Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
I think I've had it happen when it wasn't also open in ResEdit. However, I'm not certain.
I know its never happened while using the graphical syst editor; only the more normal syst editors.
A suggestion for the next version: If a resource can't be saved, find that out before closing it, not after. Less risk of losing something you just spent a few minutes on.
(This message has been edited by Lindley (edited 02-04-2004).)
Quote
Originally posted by Lindley: I think I've had it happen when it wasn't also open in ResEdit. However, I'm not certain.
If the plug-in was open in another application, then that's your problem right there. You should never have the same file open in more than one editor.
A suggestion for the next version: If a resource can't be saved, find that out before closing it, not after.
MissionComputer does try to verify whether a resource can be saved, but the problem is that when it says 'for an unknown reason', it's not kidding. What that message means is that it saved the resource, and didn't get back any error messages, but when it double-checked to make sure, the resource wasn't there.
------------------ David Arthur | (url="http://"http://davidarthur.evula.net/")davidarthur.evula.net(/url) | (url="http://"http://www.ev-nova.net/")EV-Nova.net(/url) The people united can never be ignited!
^I understand that. I know a few things about programming, since I'm a CS major.
Its just a suggestion; adding a check to see whether the save was successful (who cares why) before closing the window shouldn't be impossible, and would put my mind, at least, at ease.
Obviously, this feature might be a bit more processor-intensive than one would prefer, so it could be included only as an option for those who experience trouble.
------------------
Originally posted by Lindley: Its just a suggestion; adding a check to see whether the save was successful (who cares why) before closing the window shouldn't be impossible, and would put my mind, at least, at ease.
So, you're saying, leave the resource window open if the save doesn't complete? That might be possible - the architecture might need some small changes, but it shouldn't be too difficult. I'll put it on the list.
^Yeah, that's what I mean.
I think I've managed to isolate one of the actions that causes this problem, at least in Panther.
When I open a syst resource, its fine if I just stay on the default page, add a planet, and then close it.
However, if I mess around with the System Attributes tab, it fails to save when it closes. In particular, it just did this after I went in and changed nothing except the syst's government.
I haven't experimented enough to be certain about this, but it seems like a good place to start looking for whatever bug is causing this.....
All right, I've narrowed it down somewhat:
-If I open the Galaxy, add a syst through that, then add a planet to the syst, and then do anything with the System Attributes tab, the resource fails to save.
-The resource saves properly if I change the System Attributes tab before adding a planet or doing anything in the Galaxy editor.
Also a suggestion for the next version: When a new spob is created, the default is to make it (a) Always dominated, ( Starts game destroyed, a Wormhole, (d) Deadly, and (e) unlandable but inhabited.
I do not think this is an appropriate set of defaults for a new spob.
Try using NovaTools. It works inside Res-Edit but is easier to use if you are new to editing.
------------------ Support USA Patriot Act let real Americans take away our rights before those darn foreigners can try. Before you do what you are about to do, think about why you are about to do what you are about to do. All the problems of the world can be solved by good parents and good water.