Hi Wayne, I found a Qt open bug on that:
https://bugreports.qt.io/browse/QTBUG-43506

But it's still open and hasn't been fixed.

I'll take a look at fixing it up myself. Having the mouse coordinates is not really useful so if I just remove that text from being displayed that should fix it.

Thanks, - Michael

Dear Michael,

I recognized a strange thing where I am not sure what software is causing the issue.

When exporting in V4 beta Sep-10-2020 a closed curve that was joined from 2 or more single curves in IGES format and importing it to my CAM software, the CAM is importing the curve twice. So I get two times the same object. I tried the same with MoI3D v3 and here just one object is visible after importing to the CAM. Could there be a loop counter issue (the classical n instead of n-1 counter-end issue) in v4? Or is it an IGES format issue between CAD and CAM?

This does not happen with curves that just have one element like a line or a circle, whereas a rectangle is causing the issue as well.

Best regards

Joerg

Hi Joerg, could you please post an example file that has the problem? If you could post both the .3dm file as well as the IGES file generated from it I'll take a look to see if anything is wrong with them.

What is the CAM software you are importing into?

Thanks, - Michael

Hi Michael,

Thanks for your super fast response!!!

I attached two 3dm files each with a simple square inside stored with v3 and the other with v4 beta 2020-09-10 and the two IGES files that were created with the two different MoI3d versions.

I use Condacam as CAM software.


Greetings, Joerg

Hi Joerg, so in MoI v4 I have updated the library used for IGES, STEP, and SAT formats to a new version, and the new version by default outputs the curve contained in a "subfigure", a type of component instance. That's the difference from the V3 output, the V3 output just has a composite curve entity without any other hierarchy.

It should only be in there once but it seems that Condacam is inserting it multiple times maybe as it traverses the assembly tree when it visits the parent container element as well as the "leaf" tree node.

I think that's a quirk that may be unique to Condacam, I'm not seeing it come in as duplicated in other software.

It looks like I can set an option on the export to generate output as in V3 without it being contained inside an assembly hierarchy. Can you please test the attached file which was generated using that? It seems to be the same output as V3 so I think that should work ok with Condacam.

In the next v4 beta this will be a flag you can set in moi.ini under:

[IGES]
ExportFlattenAssemblies=y

- Michael

Hi Michael,

Thanks for your feedback!

I tested the file and it can be imported as single square as it works in V3.

PERFECT!!!

BR
Joerg

Hi Michael,

it will be very usefull to have such settings, but it will be very challanging in future to remember, that such settings exist at all :-)

Would it be possible to place this setting under Options_Import/Export_IGES options?

Mik

Hi Mik, are you also using Condacam?

Usually settings like this will first go into moi.ini and then if more people ask about it, I'll then promote it up to the Options dialog.

- Michael

Hi Michael,

understand. No, I don't use Condacam, I thought only, that it is better to have any Option settings in one place, because issue with export/import files across CAD/CAM sw appeard usually in tough project time and then it's very stressfull to find the cause of issue, especially if file is quite big.

I have nice example: I'v obtained 340 MB IGES file from ArchiCAD, when I tried to import it to MoI, the import time was close to infinity, but some IGES viewer displaied the file correctly. I thougt that MoI is inssuficient sw for importing this file, but I didn't beleive it, therefore I logicaly opened Option-Import/Export - IGES options and unchecked Join surfaces on import. The file was imported in Moi in several seconds.

Other example: Some CAM programs reads DXF including splines without problem, some old sw can read DXF containig lines only, therefore it takes some time to adjust right export settings for CNC machines. Some laser cut machines reads correctly only AI format.

I know that Moi.ini offers huge amount of custom setting, but I'm not sure if dividing the Import/export options setting in "two" places is handy, but I understand that it means more programming on UI.

Anyway thank you very much for the piece of sw like MoI is.

Mik

Hi Mik, if you're not using Condacam I don't think it is very likely this setting will do anything useful for you.

It's not so much the programming for the UI that bothers me, it's more about having a gigantic amount of UI being harder to use.

Some options may only be useful to just one person. For something like that it's not good for all users to pay the price of having a more difficult UI to navigate through.

If I were to require that every single setting must have some UI for it in the Options dialog, it would probably mean that I would have to avoid putting in settings that only helped out one single person.

If I see a pattern start to develop with the setting being needed by more people, then that's when I would want to set up UI for it in Options.

This is one of the ways to help avoid the problem of "bloat" with a program getting more and more difficult to use over time simply by having more stuff jammed into the UI all over.

- Michael

Hi Michael,

yes, I absolutely agree with you, and I understand of course, that too many UI settings isn't right way for MoI, especially for one person only, and this is good for MoI.

I reported only my experineces with CAD/CAM communication.

Peace of mind.
Mik

Hi Michael.
This behavior was noticed...
https://yadi.sk/i/6WKiyOxEVmBEHw
https://yadi.sk/d/VHq70ZJcQruL_A

Hi WN, that's a display bug some info here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7590.3

- Michael

Sorry for the late report Michael but I'm noticing odd behavior with Leaders and Grid Snap.

When I pull a leader out from its initial point, it is not snapping on grid subdivisions as it should. Grid Snap is on & it doesn't seem to matter if Object Snap is on or off. For reference, my units are inches, grid size is 1 and snap size is .25. What appears to be happening is that the length of the leader segment is in multiples of the snap size, with the effect being that what acts like a grid snap is actually offset from the normal grid snap locations.

Leaders do seem to work as expected with Object Snap and Straight Snap.

Upon further tinkering, I think this is more generalized to the annotation system because I noted the same type of behavior with horizontal and vertical dimensions. The lengths of the dimension offsets are in multiples of the grid snap, but are not snapping to the grid.

I note this behavior with both Sep-10 and Sep-16 betas on macOS 10.13.6 (17G14033)

--Larry

Hi Larry, thanks for reporting this. Yes it's snapping to a grid but with the grid origin located at the first picked point. It's not intentional that it should do that, I'll see about fixing it.

Thanks, - Michael