(03-16-2014, 05:42 PM)micheus Wrote:(03-16-2014, 05:23 PM)MikeJ Wrote: Add to current and replace current seems to do the same as preserve selection.It's different for me
Yes, it is different for you because my use of the plug-in does not work in the same way yours does. As a result, I decided to give up on this plug-in and simply not use it because obviously there was something wrong with my Wings3D.
However, the exchange between you and oort since then has caused me to make a discovery that I was misunderstanding the operation of this patch/plug-in. I did not realize that the selections made in the file to be merged in were significant. Quite frankly I'm puzzled as to why they should be.
I was assuming that the three options would ignore what ever selections were made in the file to be merged in. Therefore, in all of the files that I was trying to merge which had none of the objects or items selected, all three of the selection options in this new patch didn't do anything. Or, I should say, all did the same thing.
So, I guess I need to understand why the workflow for the use of this plug-in needs to take whatever objects are selected or not selected in the file to be merged in into account when performing the merge. In my mind the selections in the file to be merged in should be ignored and the selection settings made in the plug-in should decide for all of the objects being merged from the file being merged in as to whether they should be selected or not.
I believe this will also take care of oort's issue of needing another option of "new" unless I misunderstand what he is saying. Because in my mind "replace current" would do what his "new" option would do: All of the selections made in the current file would be deselected and replaced by all of the objects in the merged in file being selected when they arrive in the current file.