MoI discussion forum
MoI discussion forum

Full Version: Elephant Repository

Show messages:  1-19  20-39  40-59  60-79  80-99  100-119  …  500-503

From: Frenchy Pilou (PILOU)
27 Aug 2019   [#40]
Added




From: bemfarmer
27 Aug 2019   [#41] In reply to [#33]
Hi Pilou,

Star node DOES have "out", on my computer.
This suggests that something is wrong with your nodeeditor files(?)
Maybe in your language files? sortie?
Maybe copy in a fresh copy of the curves nodes?


- Brian
From: Frenchy Pilou (PILOU)
27 Aug 2019   [#42] In reply to [#41]
It's inside the English & French original for me!

Maybe I erased something many time ago during translation?

So I will investigate this curious thing! Not vital for the moment! :)


From: bemfarmer
27 Aug 2019   [#43] In reply to [#42]
Hi Pilou,

I just looked at the Word documentation pictures that I did a few months ago, and
Star DOES NOT have "Out", in those pictures.

So we both had a bad copy of Curves.js nodes back then. I have recently reinstalled, so have "Out" with Star now.

(I used Jame's files.)

- Brian
From: Frenchy Pilou (PILOU)
27 Aug 2019   [#44]
@Bem (I used Jame's files.) Curious also me with its last opus...

Section "Solids" done! (English / French) rest 19 sections to make! :)

http://moiscript.weebly.com/solids.html


From: James (JFH)
27 Aug 2019   [#45] In reply to [#43]
Pilou & Brian,

I think I can shed some light on the the case of the disappearing OUT label on "star" node.

You may recall that node labels and associated dots were formally greyed out until a wire was attached. I proposed to Max that it would be better I/O labels to be permanently coloured so as to indicate the intended wiring. I further proposed that in doing so, that labelling the output OUT seems redundant.

http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.830

To drive home this point I did a minor alteration to the code of a couple of nodes. (simply removing the OUT label). I was not my intention to infect others with these mutations; I had just forgotten that I'd done it. I do think though, that it is a testament to the lack of labelling necessity that it has taken till now for this issue to arise.

An advantage of removing unnecessary labelling is that it reduces the width of the node. This may sound like a trivial consideration, but when you have a node circuit with dozens of nodes, it can spread to multiple screen widths necessitating a lot of horizontal panning. Nonessential node width exacerbates this problem.

Not only can the node be reduced in width, but also input labels may be increased without increasing width, to better communicate the required input. The letter "C" for count, for example on "interp" & "random" nodes (& maybe others) could be fully labelled. See attached image below.





I have reinstated the labels to "point" & "star" nodes (see image below), posted revised NodeEditor folder to:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9358.1

I would be interested to know what others thought about the need of output labelling.
I think the "knob" node for example demonstrates that labelling in at least some cases (maybe most) is not required.




Max said "I need to think about it." and maybe he needs to be the one to make the final determination. Nevertheless your thoughts would be appreciated.

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

Image Attachments:
Screen Shot 2019-08-28 at 8.05.gif  Screen Shot 2019-08-28 at 8.28.gif 


From: bemfarmer
27 Aug 2019   [#46] In reply to [#45]
James, thank you for the clarification.

I'll need to ponder more on these redundant "outs."
-- how to remove "out" from Macros?
-- how to write an auto format routine to organize/arrange nodes?
-- left click info button is good to know.
- Brian
From: James (JFH)
27 Aug 2019   [#47] In reply to [#46]
Brian,

>> -- how to remove "out" from Macros? <<

Labelling outputs with a letter SPACE gives this result.



However the authors of Macros may prefer to label otherwise.
Ultimately, it is up to them!

<< -- how to write an auto format routine to organize/arrange nodes?>>

Can you explain further what you mean by this?

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

Image Attachments:
Screen Shot 2019-08-28 at 10.11.gif 


From: Frenchy Pilou (PILOU)
27 Aug 2019   [#48]
@James so a mystery clarified :) (even C for Count is disturbing because some nodes has list of variables C,D,E,F (six as maximum as I seen)

Sorry for come back to this little thing : does exist or not a shortcut for extend / reduce all nodes in the same time ?
Because click one by one is some painful! :)


From: James (JFH)
27 Aug 2019   [#49] In reply to [#48]
Pilou,

Yes the ability to collapse nodes is a great feature,
however I find that I rarely use it.

If I'm working on a complex node circuit, I find that there
is a lot of iterative adjustments to nodes inputs and at times
wholesale replacements of sequences of nodes , to get the desired result.

In this case, it is necessary to see all connectors and have access to node inputs...
collapsing & expanding nodes are a hinderance to this debugging process.

Also if you are then taking a screen grab of the node wiring setup, to show process
it is important that connection is revealed.

This may come down to personal preference, and perhaps I cannot regain the eye of the
novice user, but it seems self-evident to me the the coloured dot on the right of the node
are the outputs.

Max, if you are reading this, I be interested to know your thoughts

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


PS I only routinely use node collapsing facility on "clone" nodes because their function is clear
and they quickly make a mess of the circuit with cascading "clone" nodes bifurcating to further "clone" nodes ad infinitum.

The sooner the "clone" node is deprecated, the better.
From: Frenchy Pilou (PILOU)
27 Aug 2019   [#50] In reply to [#49]
Yes but "reduce" just a part of numerous Nodes can be helpful in case of a big circuit ! :)
(when this part is good working)

Maybe this function is yet existing!
I must explore the doc : https://github.com/jagenjo/litegraph.js

In fact i have never used intensively such prog
but i see that is increasing very speedy as soon as you want make something biggest that a simple 3 nodes! :)
From: bemfarmer
27 Aug 2019   [#51] In reply to [#47]
Hi James,
A magic button which automatically moves nodes around on the screen into almost columns and almost rows, with no crossed wires, nor overlapping of wires and nodes.
Probably pretty hard to do :-)
- Brian

So, for no Macro "out" word: in Macro expanded screen, select output rectangle, and in the info window replace "out" with "type the keyboard space bar" = " "
From: Frenchy Pilou (PILOU)
28 Aug 2019   [#52] In reply to [#51]
<< So, for no Macro "out" word: in Macro expanded screen, select output rectangle, and in the info window replace "out" with "type the keyboard space bar" = " "

Where is this ?


From: Frenchy Pilou (PILOU)
28 Aug 2019   [#53]
Added




From: Frenchy Pilou (PILOU)
28 Aug 2019   [#54]
Section Logic done (2 /20)
http://moiscript.weebly.com/logic.html

If you have some very small examples use of SPLIT "Mask" and "Long / Short / Repeat" ?





From: bemfarmer
28 Aug 2019   [#55] In reply to [#52]
Substituting " " for "some output" in a Macro, only applies for a Macro, not a regular node.
Double click on a Macro to expand it, or Right click select Open, in order to see the output "slots" of the macro.
- Brian

I think "out" for a regular node is hard-coded in the node.js file?
From: Frenchy Pilou (PILOU)
2 Sep 2019   [#56]
Added in English! ;) http://moiscript.weebly.com/widget-e.html
Done English + French !

if someone can show me difference between mode Switch (Switch) and mode Switch (Button) ?


















From: bemfarmer
2 Sep 2019   [#57] In reply to [#56]
Hi Pilou,

The Switch in switch mode maintains the connection between the input the internal wire is currently touching, and the output.
Left mouse clicking the Switch body changes the connection to the other input. After finishing the click, the connection with the other input is maintained,
until another left mouse click is performed.

When the Switch is in button mode, without being manipulated with the mouse, the connection is with the upper (top) input.
Then, in button mode, holding down the left mouse "key button" on the switch icon body, causes the connection to change to the lower (bottom) input.
When the user ceases to hold down the left mouse "key button" on the switch icon body, the connection reverts to the upper (top) input.

Your dynamic picture should be redone, because you are failing to select the switch mode, and you are only showing the button mode function.

- Brian
From: bemfarmer
2 Sep 2019   [#58]
There is a lack of symmetry in the switch action.
If in switch mode, with the switch set to connecting the lower input, changing to button mode immediately
changes the connection to the upper input.

Maybe the .js code should be changed to restore the symmetry?

- Brian
From: bemfarmer
2 Sep 2019   [#59] In reply to [#58]
It is hard to come up with an electrical analogy.

Switch mode is like a single pole, "3 way switch", which normally has 3 terminals. Two terminals are the "travelers", the third terminal is the output.
Two 3 way switches are used to light a hallway, alternately from either end of the hallway.

Button mode is like the crush ice button on an appliance, which only runs the blade when held pressed in. But this
analogy lacks a function for the upper input, which is null. Some kind of logic gate might be better.

The clutch on a car is an example of button mode? Un-pushed for normal travel, pushed in for changing gears...

- Brian

Show messages:  1-19  20-39  40-59  60-79  80-99  100-119  …  500-503