![]() Either way, when that happens, it takes me a long time to get the PJX file working again.ġ) Is there any way, short of trying to remember to close the PJX window after every build, to automatically circumvent this problem? Closing the PJX window dozens of times per day and reopening it every time to modify the app is a royal pain, and is easily forgotten at the worst possible times.Ģ) If not, is there any simple way of recovering from corruptions that will sooner or later occur?Ĭurrently, I periodically save the whole project, including the PJX file to another disk. And when there is an error in the app, the PJX file either doesn't get saved with the modifications, or it is getting saved with corrupted modifications. ![]() Obviously, the PJX file is being corrupted because the modified PJX file is not being saved until the PJX window is closed. And never when the PJX window is already closed. ![]() This happens only if there is some sort of an error in the application, never when the app runs correctly. PJX window after building the application and before testing the application the. ![]() And I just today got hit again, fortunately for the first time in months.ĭuring developement using FP2.6, if I fail to immediately close the. This has been an ongoing problem for me for years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |