MoI discussion forum
MoI discussion forum

Full Version: Nodebundle for playing with nodes

Show messages:  1-11  …  1332-1351  1352-1371  1372-1391  1392-1411  1412-1431  1432-1451  1452-1471  …  1852-1859

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

From: bemfarmer
11 Mar 2019   [#1392] In reply to [#1391]
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
From: Michael Gibson
11 Mar 2019   [#1393]
Split off Bravlin's post above to its own separate discussion thread. - Michael
From: bemfarmer
11 Mar 2019   [#1394] In reply to [#1391]
My bad code deleted.

- Brian
From: bemfarmer
11 Mar 2019   [#1395]
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:



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.





Info Panel



Options under the Info panel:


  • P Seq - which profiles are placed to which rail/rails
  • Twist - Defines how the profiles are oriented to the rail
  • Pointy ends - defines the form of the start and end of the sweep
  • cap ends - closes the start and end profile of the sweep
  • Profiles -defines the precision how the profiles are processed
  • Num Points - has only an effect if NumPoints is chosen under Profiles. It defines the number of points used to rebuilt the profile curves
  • #### - Brian

From: Karsten (KMRQUS)
12 Mar 2019   [#1396] In reply to [#1395]
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
From: James (JFH)
13 Mar 2019   [#1397] In reply to [#769]
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
From: Karsten (KMRQUS)
13 Mar 2019   [#1398] In reply to [#1394]
Hello Brian,

could you please test this:

code:
 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
From: bemfarmer
13 Mar 2019   [#1399] In reply to [#1398]
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
From: Karsten (KMRQUS)
14 Mar 2019   [#1400] In reply to [#1399]
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
From: bemfarmer
14 Mar 2019   [#1401] In reply to [#1400]
Hi Karsten,

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

- Brian
From: bemfarmer
14 Mar 2019   [#1402] In reply to [#1401]
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
From: Karsten (KMRQUS)
14 Mar 2019   [#1403] In reply to [#1402]
This world is too complicated for an old man like me.

Message 7777.1404 was deleted


From: James (JFH)
18 Mar 2019   [#1405] In reply to [#1404]
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 


From: mkdm
18 Mar 2019   [#1406] In reply to [#1405]
Amazing James!

Great job!!

Message 7777.1407 was deleted


From: bemfarmer
18 Mar 2019   [#1408] In reply to [#1405]
Much nicer than a recent stucco expanded metal purchase.
From: speedy (AL2000)
19 Mar 2019   [#1409]
Hi James
for what little it is worth ..
amazing result
alberto
From: James (JFH)
19 Mar 2019   [#1410] In reply to [#1409]
Thanks Al

It is worth a lot,

James
From: bemfarmer
22 Mar 2019   [#1411]
After 2 weeks of intermittent coding, study of many nodes, mostly by Karsten, and hundreds of corrections, a node for LineWeb was created.
There are many comments in the code, which could be removed.

In addition to the LineWeb node, a simple demo node program is attached.
Copy the LineWebNode.js file in the nodeeditor Extensions folder.
This will place the LineWeb node in the Construct2 menu.
(Construct2 could also be edited to include the LineWeb node code.) Maybe Karsten or James will do this, after the node is tested?

Testing has been minimal.
Input of other objectlist types has not be tested, nor is there any code to check for other types of objectlists.

- Brian

Attachments:
LineWebNode.zip
LineWebNodeDemo04.zip


Show messages:  1-11  …  1332-1351  1352-1371  1372-1391  1392-1411  1412-1431  1432-1451  1452-1471  …  1852-1859