Ok, first message in this thread has been updated with complete release notes, sorry for the delay.

- Michael

Popped in the forum for a look and this was at the top, nice!

Thanks Michael.

Hi Michael,

Congratulations on getting the V5 beta out so soon. A positive thing to have for 2022.

I've downloaded the beta and have attempted to create a custom theme, however there's two things I can't seem to change. I've attached a screenshot of the areas I mean.

Any assistance would be appreciated. It's late here and I'm sure it's staring me in the face but at the moment I can't seem to find them.



Kind Regards
charles

French complete release done! ;)
https://moiscript.weebly.com/nouveauteacutes-v5.html

Hi charles,

re:
> I've downloaded the beta and have attempted to create a custom theme, however there's
> two things I can't seem to change. I've attached a screenshot of the areas I mean.

The first one is in the theme editor under Side pane > "Command set background color".

For the second one, there isn't anything set up for scroll bars in the dynamic theme editor but you can set it in the theme's moi.css file using this (last scrollbar property set in the regular dark theme moi.css):

::-webkit-scrollbar-track-piece {
background-color:#777;
}

- Michael

Hi Michael,

Thank you for replying so quickly.

That's awesome, thank you so much.

Have a wonderful Easter.

cheers
charles

Hi Michael,

Maybe I've not had enough coffee, but I'm puzzled as to why the beta is not liking my Extras startup script (based upon Max's Scripts menu)
https://moi3d.com/forum/messages.php?webtag=MOI&msg=10353.1

First thought was some of the Mac filesystem changes (I'm on an M1 MBP) but it doesn't even get that far. Seems like the .js portion loads and creates the Extras icon in the menu bar, but the .htm portion never gets to starting the embedded <script>.

Something changed in CommandBarCustomUI maybe?

moi.ui.commandBar.CommandBarCustomUI.insertAdjacentHTML( "beforeEnd", 
'<moi:Spacer/><moi:Spacer/><moi:CommandMenuButton icon="'+icon+'" menu="'+menu+'">'+title+'</moi:CommandMenuButton>');

--Larry

Hi Michael,

I seek to use MoI with minimal changes, so my customizations are only done in the startup folder. In this case I have disabled the other startup scripts to see if they are part of the puzzle but the behavior is the same.

Reading the V5 Beta test thread I found your conversation with Psygorn in which you fixed his startup scripts. Those changes appeared to be applicable to my problem so I applied the same changes to my Extras.js and the result is strange in that the Extras icon no longer shows in the command bar area to the right of the snaps, but is instead showing up in the browser area beneath the objects, types, styles panels. This is behavior consistent with both MoI V4 and MoI v5 beta Apr-10-2022. My original Extras-001.zip is referenced in the prior message.

Additionally, although the icon has moved, under V5 beta the behavior remains the same: instead of creating a flyout menu with the list of commands as is normal with V4, V5 beta just creates a small empty box above the icon where the much larger flyout would normally appear. It seems that the embedded script is simply not run and there are no error messages with either my original Extras or the one which incorporates the changes shared with Psygorn. Puzzling...



--Larry

Hi Larry, your Extras.htm and Extras.js are working ok on Windows but not on Mac.
I'll dig into it to see what's going wrong over there.

re:
> Those changes appeared to be applicable to my problem so I applied the same
> changes to my Extras.js and the result is strange in that the Extras icon no longer
> shows in the command bar area to the right of the snaps, but is instead showing
> up in the browser area beneath the objects, types, styles panels.

The strange result is how Psygorn wants the UI to be set up, that's what his modified
version does.

- Michael

Hi Larry, I think it's some kind of bug in handling the file encoding of your Extras.htm file.

Something like a unicode character for the apostrophe in the comment.

If you use the version attached here does it work ok for you then?

I'll investigate a fix for it.

Thanks,
- Michael

Hi Michael,

Oh good grief, I would never have guessed that (single quote vs apostrophe) to have been the problem. Yep, works perfectly once again, many thanks!

--Larry

You're welcome Larry I'm glad it's running ok for you now.

So yes it was because of that one apostrophe was a unicode character. With the new theme support there were some changes to how .htm files were read and the Qt text stream loader doesn't behave exactly the same as the WebKit text encoding detector.

I'll see about using the WebKit text file loader again to get the same behavior as v4.

- Michael

Hi Michael Gibson

My license key is not working when trying do download V5 beta Apr-10-2022. Can you help me figure out the problem. I purchased v3 and upgraded to v4, so I don't understand why my license key is not working?

Thanks
Ogar

My 3 licenses are in my MoI AppData folder, v2, v3, and v4.
- Brian

Hi Ogar, please e-mail the license key to me at moi@moi3d.com so I can investigate what might be going wrong.

Thanks, - Michael

Hi Ogar,

re:
> My license key is not working when trying do download V5 beta Apr-10-2022. Can you help
> me figure out the problem. I purchased v3 and upgraded to v4, so I don't understand why
> my license key is not working?

Looking at the server web logs, it looks like the problem is you're putting the v3 key instead of your v4 key.

The v3 key starts with VER3- , the v4 one starts with VER4- that's the one you need.

You can find your v4 key in MoI v4 under Help > About MoI > "License keys" or also you can put in your e-mail address at https://moi3d.com/reinstall.htm and it will look up your license key and e-mail it to you.

- Michael

Hi Michael.

If I buy the v4 now(as 2022-4-27), do I pay for the v5 upgrade or it will be a free upgrade?
Sorry if this has been asked.
Thanks!

Hi r0ss0,

> If I buy the v4 now(as 2022-4-27), do I pay for the v5 upgrade or it will be a free upgrade?

It would be a paid upgrade. There will be a "grace period" where if you purchase v4 within a couple of months of the v5 release you will get a free upgrade to v5. But the v5 beta period has only just recently started, the full release is quite a ways off yet definitely more than a couple of months.

So a v4 purchase right now would not be in the grace period time for getting a free v5 upgrade.

- Michael

Hi Michael,

> Update Mac trackpad/Magic Mouse handling.

Two thumbs up on these changes! I use MOI on a MacBook Pro (without a mouse) & the V4 trackpad handling was inconsistent as you know. I haven't spent a lot of time with the beta but am noting with pleasure that I can use 2-finger drags to get panning reliably...used to be that sometimes it would get stuck and zoom instead. Now I have to "teach" myself to use it as intended! ;-}

--Larry

Hi Michael,

I'm currently testing Plasticity and some of the features are very interesting. More specifically the ability to do live Chamfering and Filleting and even more importantly the ability to rotate faces (there are still issues with rotating faces, but it looks promising).

Are these features something that you are considering at the moment for the next version of MoI? These features are extremely powerful and save an enormous amount of time when modeling.

Thank you.