My statement about blocks was a result of posting too late in the evening... 
I think I mixed two thoughts into one sentence.
"Having a standard library of blocks (objects)" was about an earlier post about custom shapes. Not sure exactly what I was planning to say??? I think I was saying that any custom shapes should simply be .wings files and not have them added to Wings3d in the menus. Geta-Ve's suggestion to have "Custom Forms" in a user defined directory isn't a bad one. It may or may not be a redundant menu item??? Adding Merge file (suggested by Optigon) to the primitives might not be a bad one either. That may or may not be redundant as well???
Being able to preview a .wings file being merged in would be great. Being able to preview .wings files before opening and .obj files before importing would be great too.
"is probably better for keeping the preferences file cleaner" was about not having all the user defined settings in the preferences.txt file.
Sorry for the confusion... hope this doesn't confuse things more...
oort
I think I mixed two thoughts into one sentence. "Having a standard library of blocks (objects)" was about an earlier post about custom shapes. Not sure exactly what I was planning to say??? I think I was saying that any custom shapes should simply be .wings files and not have them added to Wings3d in the menus. Geta-Ve's suggestion to have "Custom Forms" in a user defined directory isn't a bad one. It may or may not be a redundant menu item??? Adding Merge file (suggested by Optigon) to the primitives might not be a bad one either. That may or may not be redundant as well???
Being able to preview a .wings file being merged in would be great. Being able to preview .wings files before opening and .obj files before importing would be great too.
"is probably better for keeping the preferences file cleaner" was about not having all the user defined settings in the preferences.txt file.
Sorry for the confusion... hope this doesn't confuse things more...
oort