Full Version: Feature you coded for me doesn't work in V5

Show messages: All  1  2-8

Hi Frederick, can you please attach the plugin files here?

- Michael

---

Hi Michael,

Well that was stupid on my part.

I should learn not to rush.

There were three versions over the years.

#3 is the most recent and what I had been using successfully in V4.

Frederick

---

Hi Frederick, is it that you want to have some child objects of a group selected and found by the script to export?

Does it work ok if you remove line #12 which has this? :

	objectpicker.allowTopLevelObjects();

Or you could also change this to:

	objectpicker.allowStandaloneObjects();

- Michael

---

Hi Michael,

Yes, I was selecting items within a group.

I will try your suggestions when I have a free moment.

Frederick

---

Hi Michael,

Your first idea seems to have solved the problem.

While we are looking at this code one question:

When invoking the command the first thing it does is put up a dialog requiring me to pick STL or 3DM.

I always pick STL.

Is there any way to bypass the asking and simply default to STL?

Thanks.

Frederick

---

Hi Frederick,

re:
> Is there any way to bypass the asking and simply default to STL?

Yup, in ExportParts.js find line 22 that has this:

if ( WaitForDialogDone() ) DoExportParts(objectpicker.objects);	

and change it to this:

/*if ( WaitForDialogDone() )*/ DoExportParts(objectpicker.objects);	

That will bypass the asking stage and go immediately to the exporting.

Then to make it use .stl format find line 29 which has this:

var d = moi.ui.commandUI['extension'].value;

and change it to this:

var d = '.stl'; /*moi.ui.commandUI['extension'].value;*/

That will make it always use STL format instead of getting it from the UI control.

- Michael

---

Hi Michael,

I can handle that.

I even understand most of it.

Frederick

---

Show messages: All  1  2-8