It's a game of balance and compromise. I wanted to make sure that anything that is saved to the library passes a resource validation check first. That's why *all* new resources start life in the session repository first by current design.
I guess we could pass a "hint" to the editor of the new resource as to the suggested save location when you hit "save as" (based on where in the repository you right-clicked when you created the resource), but I'd have to grok the TreeViewAdv API to figure out if this can be done. While we're on that note, it is the TreeViewAdv control which offers selection of multiple nodes, which the Site Explorer and other tree controls use, but it also presents an API which is totally different from the stock WinForms TreeView control, so I am still learning how to do things with TreeViewAdv that would've been second nature with the WinForms TreeView. Not saying we can't do things the old way. I just haven't quite figured out how :) - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Maestro-3-0-test-build-1-tp5657585p5658349.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
