Blockly mainWorkspace undefined about ngx-blockly HOT 7 CLOSED

In fact the problem is that "Blockly" is not instantiated when I access Blockly.mainWorkspace

from ngx-blockly.

The blockly is no longer a global, but is exported. So you can import it from ngx-blockly and use it. e.g.

from ngx-blockly.

ok! I understand. Many things have changed.
Then, how do I have access now the Lua property? It seems is not there anymore

Blockly.Lua.valueToCode(...)
Blockly.Lua.ORDER_ATOMIC

I have also realized that now a block created with the workspace does not have methods initSvg or render nor a blockInstance property. Please, do you know how is this done now?

auxBlock.blockInstance.setConcreteInstancesOnly(false);
auxBlock.initSvg();
auxBlock.render();

Many thanks again for your great help

from ngx-blockly.

I do not have an answer regarding the lua.
As for the initSvg, the return of new workspace block is a Blockly.Block, but only Blockly.BlockSvg have that methods. So you will need to tell typescript it is an BlockSvg like this:

from ngx-blockly.

Thank you veru much. It is weird that the exported Blockly does not expose a Javascript or a Lua property to generate code. In the examples provided in the Blockly documentation they use Blockly.Javascript.valueToCode(...). I am a bit lost now :-( because I cannot generate code from custom blocks.

from ngx-blockly.

Unfortunately the latest changes to Blockly made that approach incompatible with typescript. To access Generators do it like this:

Blockly[NgxBlocklyGenerator.LUA].valueToCode() or Blockly['Lua'].valueToCode()

from ngx-blockly.

Thank you very much! It works!

from ngx-blockly.