Hi Michael,

I replaced those scripts with updated ones at C:\...\AppData\Roaming\Moi\startup

I still see error messages with V5. ( not with V4)

A question: Shouldn't I replace BrowserPane.htm of V5 with BrowserPane.htm of V4?

-Psygorn

Hi Psygorn,

re:
> I still see error messages with V5. ( not with V4)

Are there any additional scripts in your startup folder aside from the 2 you posted?


> A question: Shouldn't I replace BrowserPane.htm of V5 with BrowserPane.htm of V4?

It could work but it can also be problematic to get a kind of frankenstein collection of old and new versions all combined together. You can run into things like missing new stuff that has been added in to V5.

If I can update the scripts you are using then you won't need to do that.

- Michael

Hi Michael,

Yes, there are at least 13 other .js files there! I thought you only need ones with "script" on their names! sorry, my bad!

The whole old startup folder is attached. (it's a zip file)

-Psygorn

Hi Psygorn, here you go, use all these updated versions instead and does that work the same in v4 and v5 for you after that?

- Michael

Hi Michael,

Yes, It works fine :-)

Thanks for your time and help!

:-)

You're welcome Psygorn, I'm glad it is working now!

- Michael

Hi, Michael, on mac, after intalling v5, the mouse wheel don't zoom but go up or down in 3d view, and all other views. What is the situation ? Normal behavior on v4.

Hi moujiik,

re:
> Hi, Michael, on mac, after intalling v5, the mouse wheel don't zoom but go up or down in 3d view, and
> all other views. What is the situation ? Normal behavior on v4.

What kind of mouse do you have, is it Apple's "Magic Mouse" or a different one?

In v5 the default behavior of Magic Mouse "scrolling" (1 finger swipe) in MoI is to pan instead of zoom.
That's to fix a bug in trackpad handling.

You should be able to revert to V4 behavior by setting this value in moi.ini :

[MultiTouch]
UseTrackpadScrollAsMouseWheel=y

Or also in v5 if you hold down the Alt key when doing the wheel motion it should work as a zoom instead of a pan.

So the reason for this is kind of a convoluted story. The way a trackpad works is the 2 finger swipe gesture normally does a panning type action and pinching is used for zooming. The Magic Mouse happens to send the exact same event for it's "scroll" as the trackpad 2 finger swipe.

In MoI v4 I tried to detect if the scroll event was coming from a trackpad or a magic mouse to do panning for the trackpad and zooming for the magic mouse.

Unfortunately the detection didn't work in certain situations, causing a bug where 2 finger swipe on the trackpad started to do zoom (like it was a magic mouse) instead of pan, as described here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=10277.1

As best as I can tell there is not any totally reliable method for distinguishing a scroll event as coming from a magic mouse (with one finger swipe) or a trackpad with 2 finger swipe.

So it seems that Apple really wants the Magic Mouse to work like a trackpad so that's what MoI is doing now with v5. I've given up on trying to automatically detect which type of device was used to generate the event.

- Michael

Hi Michael,

When I select the object and then change the color (style) to default, the object deletes itself...

Bug?

Hi Death,

re:
> When I select the object and then change the color (style) to default, the object deletes itself...
>
> Bug?

It's actually not deleting itself, it's hiding it because all the other objects assigned to Style = Default were hidden.

I noticed recently that that behavior got accidentally broken at some point quite a while ago and I restored it in v5.

The concept is if all the objects currently assigned to the style are hidden or locked it makes the object you are assigning there to assume the same state.

If you hold down shift+ctrl when clicking the style swatch it won't change the object state.

Maybe since it was broken for a long time and nobody noticed it would be better to not do that. It's meant to make styles behave a little more similar to layers.

- Michael

IDK, but I would prefer it NOT to happen, it is a bug.
If you could fix it, that would be great.
Until you explained the bug, I was at a loss...
I did a few other objects and they all "disappeared", so I naturally assumed it to be a bug in the beta release..
Almost reinstalled version 4 to get past it, but thought to ask you first.

Thanx.

Hi Michael, yes it's a magic mouse, i'll check your solution at work this morning.
Thank you.
Moujiik

OK it's working now.

Hi Michael,

Thank you for your time and help :-)

Here is a new question:

I noticed that Nodeeditor doesn't work in V5. I have it installed in V4 is there away to have it active in V5 as well?

Best,
Psygorn

Hi Psygorn,

re:
> I noticed that Nodeeditor doesn't work in V5. I have it installed in V4 is there away to have it active in V5 as well?

The Nodeeditor works the same in V5 as it does in V4.

How do you have it installed in V4, do you maybe have it copied into the V4 program files install directory instead of in app data?

How are you launching it in V4, can you show me the shortcut key that you have set up for it?

- Michael

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