Feature you coded for me doesn't work in V5

Next
 From:  fcwilt
11688.1 
Hi,

I just tried my first multi-object export to STL that, as I recall, you coded for me sometime back.

Under V4 it looks for selected objects and if they are names it exports them as STL.

Under V4 it isn't finding the selected objects in groups.

Thanks.

Frederick
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
11688.2 In reply to 11688.1 
Hi Frederick, can you please attach the plugin files here?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  fcwilt
11688.3 In reply to 11688.2 
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

EDITED: 26 Mar by FCWILT

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
11688.4 In reply to 11688.3 
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? :

code:
	objectpicker.allowTopLevelObjects();


Or you could also change this to:

code:
	objectpicker.allowStandaloneObjects();


- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  fcwilt
11688.5 In reply to 11688.4 
Hi Michael,

Yes, I was selecting items within a group.

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

Frederick
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  fcwilt
11688.6 In reply to 11688.4 
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
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
11688.7 In reply to 11688.6 
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:
code:
if ( WaitForDialogDone() ) DoExportParts(objectpicker.objects);	

and change it to this:
code:
/*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:
code:
var d = moi.ui.commandUI['extension'].value;

and change it to this:
code:
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
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
 From:  fcwilt
11688.8 In reply to 11688.7 
Hi Michael,

I can handle that.

I even understand most of it.

Frederick
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All