More NodeCanvas suggestions / questions

NodeCanvas Forums › General Discussion › More NodeCanvas suggestions / questions

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • August 31, 2016 at 11:08 am #11301
    feelx
    Participant

    Hi,

    after diving more into NodeCanvas I noticed some things:

    1. It would be nice to have some kind of separators / header texts for the Blackboard to arrange parameters more clearly.

    2. Pausing the editor when reaching a break point in the graph. (I could probably just implement that myself)

    3. When I use the repeat node I can’t see what the nodes below are doing – the coloring for them is gone. Bug or feature?

    4. I noticed that foreach gets used quite often in the code – shouldn’t that be avoided?

    All in all still very pleased with this asset.

    Cheers,
    Felix

    September 1, 2016 at 11:28 pm #11315
    Gavalakis
    Keymaster

    Hello,

    Thanks. I am glad you like NodeCanvas.

    1. There is a variables separator you can add in blackboard, but there is no text involved there. I could probably add the ability to customize the text there.

    2. Some time ago, it was working like that (Editor paused) but some people suggested that only the graph being paused :). Both are valid of course.

    3. This is indeed kind of a bug. Basically the Status of the node under the Repeater is resetting in the same frame and that is why the UI does not get time to show it. I do qualify this as a bug though and something to look into.

    4. I mostly use foreach in parts of the code that don’t get executed frequently, otherwise a for loop. If you want to point me to some method that I’ve missed and should be a for loop, please let me know.

    Thanks again!

    Join us on Discord: https://discord.gg/97q2Rjh

    September 5, 2016 at 4:54 pm #11321
    feelx
    Participant

    Hi,

    1. ok now I found them – yes it would be nice if it would be possible to name them

    2. Ok will probably implement that myself then 😛

    3. Can you pleeeeeease fix that? At least in the beginning when getting to know the tool/features quite essential. Makes it really hard to debug and kind of defeats the whole purpose of a graphical BT/FSM tool.

    4. Ok, if I come across crucial code I’ll let you know.

    Thanks!

    September 6, 2016 at 6:38 pm #11328
    Gavalakis
    Keymaster

    Hey,

    Yes, issue n#3 is already in the TODO list to fix.
    Thanks!

    Join us on Discord: https://discord.gg/97q2Rjh

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.