2 results found

1. Variables declaration in Nodes

   Wouldn't it be smart to simply make all variables available locally within the node macro automatically WITHOUT need to use NENG.GETINPUT() assuming PORT ID to be the variable name? Similar approach as in macros run for manager getting VARDEF variables. And even use variable definitions more in tabular format and not as it's today.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   planned  ·  1 comment  ·  Node Network  ·  Delete…  ·  Admin →
   How important is this to you?

   Low You must login first! Medium You must login first! High You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. I like the recent files view in classic NAPA

   The recently opened files in the classic NAPA text editor is very useful for continuing work on a node, when building it initially, in case I need to close the program for some reason (instability etc.).
   Also it would be nice, if the editor would ask, if I want to open a new macro into a new text editor, in case I have already opened one macro in the text editor.
   Additionally, it would be nice if the "open" dialog would have some memory, like the last database unit I was opening the macro from. This is quite useful when working with DB2 macros.
   Perhaps it would make sense to introduce a new prefix for node macros, but not limiting the use of existing DATA* macros for nodes, since this far, for the node macro to work, it needs to be set up in quite a specific way and this would help in finding the node macros more easily.
   PS. nice work with the syntax highlighting!
   PPS. the text field in the uservoice page is quite annoyingly small showing only 4.999 rows of text when posting the idea.

   The recently opened files in the classic NAPA text editor is very useful for continuing work on a node, when building it initially, in case I need to close the program for some reason (instability etc.).
   Also it would be nice, if the editor would ask, if I want to open a new macro into a new text editor, in case I have already opened one macro in the text editor.
   Additionally, it would be nice if the "open" dialog would have some memory, like the last database unit I was opening the macro from. This is quite useful when… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   planned  ·  0 comments  ·  Text Editor  ·  Delete…  ·  Admin →
   How important is this to you?

   Low You must login first! Medium You must login first! High You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating