Hi Pilou,

re:
> PS you don't speak about the flikering of the Max SMirnov Subdive functions! ;)

Yes, sometimes it's a bit difficult to make a simple description of a change. Sometimes I leave out a few things if they were like that especially if I've already told the person who reported it that there is a fix prepared for the next release.

- Michael

No problem! :)

Michael,
There is a minor problem with both beta releases, in that the full screen window is too big and it partially overlaps the Windows 11 task bar at the bottom of the screen.
Barney

Hi Barney, does it also happen with MoI v4 as well? Can you please e-mail me a screenshot at moi@moi3d.com ?

Thanks, - Michael

No, Version 4 is OK
I'm sending the screen shot under my real Name(!)

My perspective on this issue:

MoI 4, 5beta1, and 5beta2 were filling up the screen completely.
But, by hitting the Windows 11 upper double box at the top left, (The Maximize/Restore icon) to the right of the minimize dash, then draging the reduced MoI window left, then right,
all 3 such MoI versions then leave the Windows 11 task bar at the bottom of the screen.

- Brian

Hovering over the Window 11 Maximize/Restore icon in Windows 11, pops up 6 possible window pane varieties. (Customizable???)
For Windows 11, the Window Maximize/Restore icon in MoI 5 beta does not have this hovering behavior.
(I am speaking from much ignorance :-)

Is this some new feature of Windows 11?
YES, it is called snap layouts.
https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/apply-snap-layout-menu


(I am already getting annoyed by the Windows 11 "weather report +" button at lower left popping up on my screen " :-( )

Hi barney,

re:
> No, Version 4 is OK
> I'm sending the screen shot under my real Name(!)

So in the screenshot the main MoI window looks like it is not overlapping the task bar, the problem is that the bottom toolbar is getting a vertical scroll bar on it. This is likely a side effect from a UI mod since your UI has some modifications on it.

Please e-mail me your startup scripts folder and any other files that you have changed in the UI and I will see if I can adjust the mod for you to stop that from happening.

- Michael

I've look but cannot find the release notes.

Groups (something I asked for early on) are looking good.

Thanks much.

Frederick

Hi Frederick, release notes for this version are at the first message of this thread, here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=10706.1

Also the release notes for all v5 beta releases are collected here:
http://moi3d.com/wiki/V5Beta

- Michael

If possible I would like to see a way of exporting a group as individual STLs, for each object, with the file name composed of the group name and the object name concatenated, perhaps using some sort of user defined pattern. The pattern would allow a tag for the group name and the object name plus other literal characters.

This would really benefit my workflow.

As I develop a product I usually progress through various versions. If by placing the objects of a given version in a group, named after the version, I could export all the STLs needed for a selected version with the version information in the file name.

In V4 I have to include the version information in the name of each object. Moving to the next version of a product involves editing the name of each and every object, since I want the version info in the STL file name. As you can imagine that is tedious and error prone.

Thanks.

Frederick

Hi Frederick,

re:
> If possible I would like to see a way of exporting a group as individual STLs, for each
> object, with the file name composed of the group name and the object name
> concatenated, perhaps using some sort of user defined pattern. The pattern would
> allow a tag for the group name and the object name plus other literal characters.

The group structure is accessible to script so It should be possible to make a script that would do that.

I would need to see an example file with groups set up and the corresponding desired output to make sure I understand what it's supposed to do and you would need to specify in more detail how the user defined pattern would function.

Also if the file names were generated in this way how would you want to specify the directory for where to place the files, would that be expected to be in the group name?

- Michael

Hi Michael,

Attached is a simple file with ONE group and THREE objects.

I envision selecting the GROUP and then executing a EXPORT STL command.

Each OBJECT in the GROUP would be exported as a separate STL file.

The destination folder would be determined by a option within the 3DM file itself (as opposed to a option within MOI) . This option would be specified by the user and it would be saved with the file.

The name of each file would be determined by another "file option" which would determine how the file name would be constructed from the GROUP name and the OBJECT name.

I can see having some sort of tokens representing things like the GROUP name, the OBJECT name and anything else you think would be good.

So lets say the tokens for the two above were $G for GROUP name and $O for OBJECT name.

They would be used, along with literals, to create a template used to construct the file name.

With a template of $G_$O and using the attached 3DM file the file names would become:

Group A_Sphere 1.stl
Group A_Sphere 2.stl
Group A_Sphere 3.stl

Hope that makes it clear what I am thinking of.

Frederick

Hi Frederick,

re:
> The destination folder would be determined by a option within the 3DM file itself (as opposed to
> a option within MOI) . This option would be specified by the user and it would be saved with the file.
>
> The name of each file would be determined by another "file option" which would determine how
> the file name would be constructed from the GROUP name and the OBJECT name.

Unfortunately there is not a mechanism in place currently to have this custom "file option" type data.

So those parts are not feasible in the current version.

- Michael

Hi Michael,

OK so how about, for now, using the existing app level option file?

Or even hard-coding into the script?

Frederick

Hi Frederick,

re:
> OK so how about, for now, using the existing app level option file?
>
> Or even hard-coding into the script?

Here's a version that has the directory name hard coded in the top of the script.

It will go through selected groups and generate .stl files into the directory.

There are instructions for how to install a plug-in here:
https://moi3d.com/faq#Q:_How_do_I_install_a_plug-in_script.3F

- Michael

Hi Michael,

Thanks much.

The install instructions mention two files, a .js file and a .htm file.

Do I need a .htm file?

Frederick

Hi Frederick, in this case you don't need the .htm file. The .htm file usually contains the UI for the command but since this one doesn't display any UI it doesn't have an .htm file.

- Michael

Hi Michael,

Actually I like that very much.

The previous script asks what type of export and, for STL files, it shows a dialog with a number of options.

This is quick and easy. I am happy as a clam at high tide.

A quick related question. Is the concept of a 3DM file having user entered meta-data, such as would be required for my export idea, or things like author, project, etc within the realm of the reasonable for V5?

Frederick

Hi Frederick,

re:
> A quick related question. Is the concept of a 3DM file having user entered
> meta-data, such as would be required for my export idea, or things like
> author, project, etc within the realm of the reasonable for V5?

Yes it should not be difficult to add those for v5.

- Michael

Michael

You are the best. You deserve some kind of award. Maybe a Nobel?

Frederick