Full Version: Nodebundle for playing with nodes

Show messages:  1-8  …  1329-1348  1349-1368  1369-1388  1389-1408  1409-1428  1429-1448  1449-1468  …  1849-1859

Thread Split: Some posts in this thread have been moved here

Hello Brian,

I missuse a moi function for dialog boxes to display the html (moi.UI.createDialog). It's an easy and hopefully lightweight way to show some Information.

I'm more weired about the problem with the light display mode. Typically is something wrong with the path, when that happens. The path is evaluated in basicfunctions.js.

Looking forward
Karsten

---

Thread Split: This post has been moved here

Hi Karsten,

The html box is easy to delete, so not much of a problem.

The docupath in basicfunctions.js refers to "index.html", which matches "dark" hotkey,
whereas "light" hotkey refers to .../indexhtml?scheme=Light"...


My Shortcut key for "dark" nodeeditor, Ctrl+Alt+M:
moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );

 

My Shortcut key for "light" nodeeditor, Ctrl+Alt+N:
moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html?scheme=Light', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );

Modification to reverse the html problem, but not correct it:
In docupath, replace ..."index.html"... with ..."index.html?scheme=Light"
Now the dropdown works in Light mode, BUT not in Dark mode.

So this is not a solution. I can now use the dropdown documentation in Light mode, but not in Dark mode.

- Brian

Maybe a fix in docupath would be to do: If index.html?scheme=Light, do the dark dialog, else do the light dialog. Or something similar?

---

The little tiny doc window is the same as the window for info for a node that does not have any .html info code. (YET:-)

- Brian

---

Split off Bravlin's post above to its own separate discussion thread. - Michael

---

My bad code deleted.

- Brian

---

They call this nitpicking:-)

Modified the text of the .html a little bit. ist = is, places = place, imputs = inputs, rebuilt = rebuild, olaces = placed, orientated = are oriented

"placed TO the rails" or "placed TO the first rail" do not sound quite right to me, but may be OK.
alternatives might be "placed on the rails or "placed along the rails..."

Also the AAABBBCCC placement description was not clear to me.
A description of the ABCABCABC placement would also be helpful.
Or even just AABBCC placement?
A specific example, say 4 objects to place, and two rails...(?)

####


The Sweep node has two options available by the RMB:

• One Rail
• Two Rails

One Rail:

Takes one Rail for each Sweep. The number of profiles used for each rail is defined by the whole number of profiles divided by the number of rails. The order in which the profiles are placed to the rail is defined by the switch in the infos panel. AAABBBCCC means the first, second, third, ... profile in the objectlist is placed to the first rail.

Two Rails:

Takes pairs of curves from the rail inputs and places profiles from the profiles input to them. The order in which the profiles are placed to the rail is defined by the switch in the infos panel. AAABBBCCC means the first, second, third, ... profile in the objectlist is placed to the first rail pair.

---

Hello Brian,

I'm very grateful for your invertigations and improvements. Feel free to change things and send me the improved html, please. There are alot of other nodes to describe.

Thank You very much!
Karsten

---

Ralf,

We are looking to rationalise the extension nodes, & with a view to this I have retributed your node contributions into existing submenus. Have a look at attached r2d3.js file, & let me know what you think.

---

Also, I was having a play with your stream2array node: icosStream.nod attached.
I posted an animation to instagram (it too big to post here, I'm running out of server allowance)
https://www.instagram.com/nodeology/

Anyway, I have noticed some anomalous behaviour. Have a look at 2nd instance of stream2array node. It is not connected to an output but rather outputs through the 1st instance of the node. Curious!

Nevertheless, I am enjoying exploring your nodes

Thanks
James
NE folder can be found here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9358.1

---

Hello Brian,

could you please test this:

 if ( document.URL.indexOf("appdata") > 0 ) { docupath = document.URL.split("index.html")[0]+"nodes\/extensions\/Documentation\/"+lang.LANGUAGE + "\/"; }
					else { docupath = document.URL.split(/moi:\/\/(.*\/).*/g)[1].replace("ui","")+"nodes\/extensions\/Documentation\/"+lang.LANGUAGE + "\/"; }

Thanks in advance!
Karsten

---

Hi Karsten,
This version enables the doc dropdown in both "Light" and "default Dark" versions of nodeeditor. (It looks like you added [0] to your code.)

However it also creates a "mouse scroll/zoom wheel" "Hole" at the top center of the nodeeditor screen, Light or Default version.

- Brian

---

Hello Brian,

I've changed to split and take the first part by [0].

The scroll wheel issue doesn't happenend here with Windows 7 64bit and MoI Beta V4. I've tested also on Windows 10 - also no Problem!?

Have a nice day
Karsten

---

Hi Karsten,

So far, no one else has reported having the "Hole", so ...?...

- Brian

---

Hi Karsten,

It seems that snaggit13 was causing the "Hole", so your latest code seems to be just fine, and enables Light and Default Dark nodeeditor, along with the ne doc dropdown.

- Brian

---

This world is too complicated for an old man like me.

---

Message 7777.1404 was deleted

---

Hi All,

Screen above lofted to fully open pattern to give variable aperture relief, mapped to a surface

James
https://www.instagram.com/nodeology/

Image Attachments:
triLoftedScreenSm.jpg 

---

Amazing James!

Great job!!

---

Message 7777.1407 was deleted

---

Much nicer than a recent stucco expanded metal purchase.

---

Show messages:  1-8  …  1329-1348  1349-1368  1369-1388  1389-1408  1409-1428  1429-1448  1449-1468  …  1849-1859