Full Version: NodeEditor Plus [Unofficial]

Show messages:  1-14  15-34  35-54  55-74  75-94  …  115-116

Hi Brian,

for this part:
> Edit upon closing and re-opening MoI, the New shortcut key is no longer installed
> (assigned new code)...so it does not work.

This can happen if you have multiple instances of MoI running when you set up a new shortcut key.

MoI will save shortcut keys to the moi.ini file when it exits, and if you exit an instance that did not have the shortcut key set in it last it will get overwritten.

So it's good to have only one instance of MoI running when you are setting up shortcuts, and then close that one before you open up any more.

I've tuned this up a bit for the next beta so that it will write changes to the moi.ini immediately after editing any shortcuts. You should still have only one instance running but you won't need to close it to get moi.ini to be updated.

- Michael

---

Hi Michael,

I have tried numerous permutations of changing the Shortcut key. Including Alt+T, Ctrl+Alt+T, Ctrl+Alt+X, and rebooting the computer.
Setting Alt+T to my modified code, I am able to get Light, and Lavender.

For the PDF specified shortcut code, I am now "stuck" on default dark theme, but with the large canvas. A while back the canvas size was remaining small.

Setting Ctrl+Alt+T to the PDF specified shortcut code, with copy & paste, numerous times, and changing the Default theme to Light, or Lavender, etc, does NOT change from default Dark.

After a reboot, the canvas display is delayed, with a very brief flash of light color.

It is almost like there is a Cache of the default dark theme, but reboot should end this. (?)

(I was able to change the default language to FR, with no problem.)

Anyway, weird stuff. (Windows 10)

I do have the recent new alternate Themes installed, but am not using them.

Is anyone else having NodeeditorPlus Theme problems?

- Brian

---

Theme problem SOLVED!

I was copying the shortcut command from a PDF program which opened the NEPlus document PDF file.
Apparently the PDF program put in some BAD characters of some sort.

So copying the shortcut code from MO's code on the MoI discussion worked fine.

I think that the PDF reader program was from MS Edge(???)

- Brian

---

With further testing, I'll conclude that "Copying the Shortcut code from the PDF documentation via Edge, Google chrome, or Adobe does NOT work properly, even though the characters visually appear correct.

Copying from the MoI forum works.
I suppose that typing the pdf code manualy would probably work.(?)

- Brian

---

I'm glad you got it figured out Brian!

- Michael

---

Hi Mo,
Perhaps the option to toggle on and off the time elapse could be added to the node menu?
Cheers
Barry

---

Hi Barry
>> Perhaps the option to toggle on and off the time elapse could be added to the node menu?

It is possible, but I think It's not something that we need to access all the time in a menu.
I'll think about it.

---

After separately copying the 4 shortcut code lines from the Documentation PDF, to Notepad++, and removing the CR and/or LF (Carriage Return, Line Feed), at the ends each code line, by backspacing, I have reached the following conclusion:

The Documentation PDF shortcut code contains several CR and/or LF, which if copied to the shortcut key, cause the shortcut code to fail.
I would suggest changing the PDF to not create CR and/or LF, (if possible), OR add a text file of the shortcut code, to the NodeEditorPlus zip file, and tell the user NOT to copy/paste original PDF code.

- Brian

Edit: CR and/or LF can be removed in Notepad++, (find and replace), per internet searches.

I am now done with this shortcut topic :-)

---

Thanks for mentioning it. I can see it now.
The problem was at the end of the third line. I should have concatenated the 3rd and 4th lines in the pdf.

var theme = 'Default'; /* Theme options: Default,Light,SkyBlue,Autumn,Lavender */
var language = 'EN'; /* Language options: EN,RU,FR */
moi.ui.createDialog( 'moi://appdata/NodeEditorPlus/index.html?'+
'scheme='+theme+'&lang='+language+'', 'resizeable,defaultWidth:870,defaultHeight:480',
moi.ui.mainWindow );

The code in my first post works fine, I'll update the pdf soon.
Sorry for inconvenience.

---

Cool MO!
Thank you again

- Brian

---

Hi all,

I will prepare a french version of the documentation.

---

Excellent i will put a link to my French site!
https://moiscript.weebly.com/biblio-elephant.html

---

Hi MO,

It is great to see a reboot of the Node Editor for MoI!

Thank you!

Wayne

---

Hi

Just uploaded new version
v0.7.01 Updates:
Fixed pdf shortcut code issue
Added CTRL + Double click on canvas to toggle "canvas info" on and off

---

Hi Phiro
Thanks for your contribution :)

---

Hi all,

A french version of the documentation.

Have fun !

P.

Attachments:
NodeEditorPlus_Quick Start-FR.pdf

---

Bonjour Phiro

Thank you for your contributions... which make this software magical and a forum rich with great people.
Merci pour vos contributions ... qui rendent ce logiciel magique et un forum riche de belles personnes.

chri

---

Added to the Elephant Library https://moiscript.weebly.com/biblio-elephant.html

---

Note that old node programs, (assemblages of old nodes), may open and work in NodeEditorPlus, but they may look different, and inherit some differences from the new node.
Example: ConvertPts from an old node program. Mode order is different, but it still functions. Opening the new, Plus version shows different input and output.

I did an update of ConvertPts2, (it had some harmless errors as well, and was not multitype), to do interpcurve curves rather that control point curves, and called it ConvertPts3. It would go in the extension folder. (not uploaded) . Interpcurve could be added to ConvertPts, in the points.js big file.

- Brian

---

Here is a modified points.js file, as points.zip, which adds interpcurve to ConvertPts, as InterpCurve U, and InterpCurve V. (For NodeEditorPlus)
If desirable, this would replace points.js in NEPlus.

I'll leave it up to MO, whether to adopt this modification or not, and will delete this file for room, in a few days, either way.

I had to be extremely careful to spell the new words correctly. Failure for spellings to agree yields strange results, orange lights, etc.

Curve V and InterpCurve V just made a bunch of points in a pile in my test script.

I think that to re-used old node program assemblages, all nodes in them should be replaced with NEPlus version, even if they "look right".
Re-save the upgraded node program. Maybe even close and reload MoI. (not quite sure).

In my yarn knit node, the Curve U version had end tangents which were (slightly) not parallel to the xy plane, (z values differed).
The InterpCurve U version of the knit curve, the end tangents were of constant z, which enables array in the xy plane with smooth end connections.

- Brian

Edit, modified points.js file deleted. (MO says he will use it.)
I have switched to the Curves>curve node, as per MO

---

Show messages:  1-14  15-34  35-54  55-74  75-94  …  115-116