MoI discussion forum
MoI discussion forum

Full Version: Node Wish List

Show messages:  1-11  …  332-351  352-371  372-391  392-411  412-425

From: Barry-H
27 Jan   [#392] In reply to [#391]
Hi Mo,
works fine many thanks.
Barry
From: Frenchy Pilou (PILOU)
27 Jan   [#393] In reply to [#387]
In fact we must make our own schema from your example ?
(killing some nodes and save it ) that works fine...
Or there is an original somewhere ?
Or I miss something ?
(here in French for some nodes because i have French enable! :)

From: MO (MO_TE)
27 Jan   [#394] In reply to [#393]
Hi PILOU
>> In fact we must make our own schema from your example ?

I modified my main.js to have more colors. But, there should be no difference in terms of working.

>> Or there is an original somewhere ?

Actually, I was working on implementing some new features of this "litegragh" fork into the old nodeeditor. But, I haven't released it yet.
https://github.com/atlasan/litegraph.js

It works nice, But, I have some problems with html and css parts.
I was hoping to find someone interested/skilled to help me finish it! :)
From: Frenchy Pilou (PILOU)
27 Jan   [#395] In reply to [#394]
THx for the infos! And alas i can't help you on these difficult domains! :( (for me)
From: James (JFH)
27 Jan   [#396] In reply to [#387]
MO,
RE: "FilletCurve" and "ChamferCurve" nodes

This is some impressive work. Indeed the facility for selecting vertices is such a profound contribution, that I really feel it is deserving of its own node.



As well as isolating vertices for fillet/chamfer operations, it could, for example add a trim point on a curve; and in the instance where there were coincidental end point, perform selective joining of curves; etc etc.

Also vertices could be output as points for the locating of other objects/geometry/vectors; or be the targets for operations (eg extrude to point).

Generally I am resistant to the tendency towards node library bloat, but in this case I believe that it would beneficial to take this facility for vertex selection out of your new nodes and universalise it into a dedicated node.

Either way; Brilliant work.
Keep it up.

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


PS Another thought: Could node have an "index" number array output as an alternative option?

Image Attachments:
verticeSel.jpg 


From: MO (MO_TE)
28 Jan   [#397] In reply to [#396]
Hi James
Thanks for your ideas. I hadn't thought about using the corner points like this.
Although, I should think more about adding a break to curve or merging curve segments.

I was thinking about adding a new node for selecting sub-objects like edges and faces to use them in filletEdges, blend, offset, inset, extrude, n-sided, network and shell nodes.
Maybe I can add an extra "point" option to it.

One thing I'm not sure about is if is it better to write a "select sub-objects" node and rewrite other nodes above to work with it,
Or, add selection function like "filletCurves" to all of them. (I guess the first one is faster and easier!)
From: James (JFH)
28 Jan   [#398] In reply to [#397]
Thanks for your reply, MO
quote:
not sure about is if is it better to write a "select sub-objects" node and rewrite other nodes above to work with it....

I like the way you're thinking!

If there was an "index" output from "select sub-objects" node, then the nodes: Construct/FilletEdges & Construct/ChamferEdges would not need to be re-written. As for Construct/Extrude etc, would they not perform analogous to Moi menu tool equivalents and accept faces as inputs?



Certainly, the ability to manipulate sub-objects rather than separate breps to discreet surfaces, curves and points and, where necessary, then rejoining; will afford greater control of resultant geometry.

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

Image Attachments:
SubObjSel.jpg 


From: MO (MO_TE)
29 Jan   [#399] In reply to [#398]
I think adding an index output for selected sub objects is a good idea, but, using this index output in other nodes brings a new challenge:
Some commands like fillet, chamfer, offset, blend and extrude behave differently with curves, edges and faces.
For example, I'm not sure how to distinguish an index for a node like "offset". should it behave like an edge/curve index or a face index or an objectlist index ?

I made a "Select_SubObjects" node. It has two outputs (for now). One output for edge/face sub objects, another one for extracting selected sub objects as separate objects.
It works nice with extrude and shell nodes without needing to change anything.
Also, adding a corner point output for fillet/chamfer is another good idea. Thanks :)
From: James (JFH)
29 Jan   [#400] In reply to [#399]
MO,

I am looking forward to getting my hands on "Select_SubObjects" node.
quote:
Some commands like fillet, chamfer, offset, blend and extrude behave differently with curves, edges and faces.
For example, I'm not sure how to distinguish an index for a node like "offset". should it behave like an edge/curve index or a face index or an objectlist index ?


The variance of operation on sub-0bject types has already been dealt with for filleting and chamfering.
Maybe a similar approach is required for offsetting.



As you alluded to extruding behaves consistently regardless of input types,
Blending only works with edges and curves, so it may also require separate nodes or ideally separate modes within "Blend" node.

Does existing Construct2/Blend node work with your "Select_SubObjects" node?

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

Image Attachments:
indexInput.jpg 


From: MO (MO_TE)
30 Jan   [#401] In reply to [#400]
Hi James

>> Does existing Construct2/Blend node work with your "Select_SubObjects" node?

No, It needs two named edges to work and it is not easy to use either. Also, it doesn't have an option to flip curves or edges.

>> Maybe a similar approach is required for offsetting and blending.

I've made a new blend node that works with "Select_SubObject" node on edges and curves.
Also, offset node works really nice with edges, faces and curves. :)
So, there is no need to add new nodes except "blend" node.

Some new options I'll try to add:
An index input and output for "Select_SubObjects" node instead of adding it to the other nodes.
A "sharp points" mode for curves.
From: Barry-H
31 Jan   [#402]
Hi all,
Is it possible to have a text array Concat node that can be index selected and displayed in the note node.
thus giving a text display of process selected within the nod file.
Cheers
Barry
From: MO (MO_TE)
2 Feb   [#403] In reply to [#402]
Hi Barry
Nodeeditor doesn't support the "string" type inputs/outputs.
I think it is possible to do that, but in the simplest scenario, requires adding "string" type support to nodeeditor,
Making a node to keep strings and changing other existing nodes like "idxSelect", "Concat" and "Note" to work with new string type.

I'm not sure if adding a completely new string menu and changing nodes is worthy for just one task.
From: Barry-H
2 Feb   [#404] In reply to [#403]
Thanks Mo I have used a number system now and it works ok.
Barry
From: MO (MO_TE)
2 Feb   [#405] In reply to [#404]
>> I have used a number system now and it works ok.
Cool, I'll be happy to see the way you do it in an example nod.

>> is there a limit to the number of Note nodes you can have ?
I don't have this issue here, do you get an error when this happen?
From: Barry-H
2 Feb   [#406] In reply to [#405]
Hi Mo,
no error message and have just tried again no problem at all.
Must have been my error.
Will update my Sections nod file as an example.https://moi3d.com/forum/index.php?webtag=MOI&msg=11314.71
Cheers
Barry
From: MO (MO_TE)
2 Feb   [#407] In reply to [#406]
Thanks. :)
From: MO (MO_TE)
2 Feb   [#408] In reply to [#406]
After seeing your nod file, I came up with an idea to switch the text with an index number.

For "switch text by index" to work, you need to change the newly added "mode" property to "Index" and separate your text by three stars (***).

See the attached nod file.

Attachments:
Note.js
Note_Index_Mode.nod


From: Barry-H
2 Feb   [#409] In reply to [#408]
Hi Mo,
excellent node.
Is it possible to have a index position that shows the choices because they are not visible one run is pressed.
Many thanks
Barry
From: MO (MO_TE)
2 Feb   [#410] In reply to [#409]
Hi Barry
Sorry, It needs nodeeditor to be running to work properly.
Although, I added the page system to display the number of choices.
Updated my earlier post.
From: Psygorn (DRILLBIT)
9 Mar   [#411] In reply to [#387]
Hi all,

I am using Google Chrome and when I want to download "ChamferCurve.js" it says "Virus Detected" and stops downloading process.

Do you know how I can fix this? or could you send it to me (like changing it's format from .js to .txt)

Edit: it also happens for "ArrayGem.js" so, if you could send that to me; I would appreciate it :-)

- Psygorn

Show messages:  1-11  …  332-351  352-371  372-391  392-411  412-425