Hi Michael,

Nodeeditor located here: "C:\...\AppData\Roaming\Moi" that's why I expected it to work with V5 as well.

The short key I use for it in V4 is: Alt+N

-Psygorn

Hi Psygorn,


> Nodeeditor located here: "C:\...\AppData\Roaming\Moi" that's why I expected it to work with V5 as well.

Yes, if it's being used from there it should work in both v4 and v5 as well.


re:
> The short key I use for it in V4 is: Alt+N

Can you also post the text you have for the "command" part of the shortcut key?

- Michael

Hi Michael,

A new issue appeared! (It has nothing to do with Nodeeditor)

Open the attached file in V5, select all red curves press Ctrl and while have it pressed try to move them (basic copying procedure)! V5 copies only few lines not all of the selected lines! (V4 is able to open this file and there everything works fine)

> Can you also post the text you have for the "command" part of the shortcut key?

Here is the script:
script: if ( moi.majorVersionNumber == 3 ) { moi.ui.createDialog( 'nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow ); } else if ( moi.majorVersionNumber == 4 ) { moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow ); }

I changed it to : script: if ( moi.majorVersionNumber == 4 ) { moi.ui.createDialog( 'nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow ); } else if ( moi.majorVersionNumber == 5 ) { moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow ); }

and Now it works :) thank you for the hint.
Edit: or maybe I shouldn't change it that way?

Please help me with other issue.

-Psygorn

Hi Psygorn, for the node editor since you probably don't use version 3 anymore you can remove the version specific stuff in there and just put this:

script: moi.ui.createDialog( 'moi://appdata/nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow );

That will then work in v4, v5, and v6+

Your new one above will break again when major version number becomes 6 in the future.


For your red curves, that's definitely a bug in v5 where Ctrl + drag is not copying edge curves like it should be. Some of the selection changes relating to groups must have broken that.

For the time being use Transform > Copy to copy edge curves instead of Ctrl+drag . I'll work on fixing the bug for the next beta release, thank you for reporting it!

Thanks, - Michael

Hi Michael,

Thank you for your help & time. :-)

-Psygorn

This folder structure you mention would be really useful — I actually need it far more than I need the existing group, which is more like a compound part object than a group of independent objects.

With the new groups, it would be nice to be able to make the side panel a bit wider. It could be done in terms of how many columns of buttons you have — I'd be happy to go to five or even six columns.

Also, in the dark theme, the selection rectangle and construction lines are pretty hard to see if you also have a darkish background color. It would be nice to have them tweakable without a full theme swap.

Hi Cuboctahedron,

re:
> With the new groups, it would be nice to be able to make the side panel
> a bit wider. It could be done in terms of how many columns of buttons you have — I'd
> be happy to go to five or even six columns.

If you have Options > General > Scene browser position = "Adjacent" mode set so the scene browser is in its own pane you can make it as wide as you need by dragging its edge.

- Michael

Hi Cuboctahedron,

re:
> Also, in the dark theme, the selection rectangle and construction lines are pretty hard
> to see if you also have a darkish background color. It would be nice to have them
> tweakable without a full theme swap.

Can you please post a screenshot of what you're seeing?

When you have a dark background, the construction lines should display as alternating dark and white to make them easier to see. That should change from the regular light mode display where they are drawn in a dash pattern of color / transparent / color / transparent etc...

It's generally best not to have a really pitch black viewport background because then files that you open with black lines in them will be very difficult to see.

- Michael

Yes. This is great, but it still wastes a lot of screen. I guess as an alternative, being able to pin both the construct and transform groups open at the same time would be nice, but that's probably just a re-skinning at that point :-)

With this color scheme, sometimes I get a nice bold black selection rectangle, and sometimes I get this.

Hi Cuboctahedron,

re:
> Yes. This is great, but it still wastes a lot of screen.

When you're not actively using the browser pane you can hide it using the "Browser" button at the bottom.


> I guess as an alternative, being able to pin both the construct and transform groups open at the same
> time would be nice, but that's probably just a re-skinning at that point :-)

There is a startup script you can put in which will ungroup the palettes:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9439.3

And a couple of variations:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9953.2
http://moi3d.com/forum/index.php?webtag=MOI&msg=6507.487

- Michael

Hi Cuboctahedron,

re :
> With this color scheme, sometimes I get a nice bold black selection rectangle, and
> sometimes I get this.

Is it that you're getting the bold one when you start on the left and drag towards the
right and the anemic one when starting on the right and dragging towards the left?

The left to right one displays with solid lines and will capture only things completely
contained inside the window.

The right to left one ("crossing window") displays with dashed lines and will target
anything that touches the rectangle, not just completely contained within.

The dashed line one is doing a color / transparent / color / transparent type dash
pattern. I'll see about switching it to a dark / white / dark / white pattern instead
like construction lines have now in the dark theme.

Thanks for showing the problem.

- Michael

Hi Michael,

I hope you are doing well, I have got a couple of quick questions for you.

Could we have an ability to extract edges as individual curves when we press Join on them? ( I know Join does that for polyline edges but it seems it doesn't do it with single edges or for example bases of a Cylinder) ( see the green line in the attached file)
Also Could we have an ability to quickly extract intersection line of two colliding surfaces? (see the red line in the attached file)

Hi Psygorn,

re:
> Could we have an ability to extract edges as individual curves when we press
> Join on them? ( I know Join does that for polyline edges but it seems it doesn't
> do it with single edges or for example bases of a Cylinder) ( see the green line
> in the attached file)

Join is focused on combining multiple objects together and so it ignores a single
object input.

You can extract edges as individual curves by selecting them and using
Ctrl+C/Ctrl+V copy/paste on them. That will work with any kind of edge selection.


> Also Could we have an ability to quickly extract intersection line of two colliding
> surfaces? (see the red line in the attached file)

You can do that now by selecting your 2 surfaces and then run the Construct > Curve >
isect command. That command generates curves or points at the intersections
between objects.

- Michael

Hi Michael,

Thank you for your reply :-)

>You can do that now by selecting your 2 surfaces and then run the Construct > Curve >
>isect command. That command generates curves or points at the intersections
>between objects.

And How can I assign a short key to it?

_Psygorn

Hi Psygorn,

re:
> And How can I assign a short key to it?

For the command part of the shortuct key, put in:
Intersect

- Michael

Hi Michael,

Thank you :-)

Dear Michael, if you think I shouldn't ask the previous questions here (in the V5 Beta test thread) feel free to delete them.

Best,
Psygorn

Hi Psygorn,

re:
> Dear Michael, if you think I shouldn't ask the previous questions here (in the V5 Beta
> test thread) feel free to delete them.

It's ok they don't need to be deleted but it would be better if you could create a new topic for things like this.

It's just a little more difficult to keep track of multiple conversations all lumped together in the same thread.

- Michael