LDCad 1.5 Beta 1 (win+linux)

[Roland Melkert]

I have left the basic message only to emphasize the problem: so far I was not able to reproduce any such crash. Only I know is that it is neither the case of those well-known you mentioned in the last comment. For example, LDCad crashed once when I edited the pneumatic hose path and put both endpoints at the same point in the space. Looks as a good example but it is not: I have not been able to reproduce that since that time. And other crashes are even harder to describe.
That's why I asked how to help you with that. Is there any cmdline option or config option to turn logging to be verbose enough it helps you? Or do you want to build a non-stripped binary for me? I'm ready to test it if you tell me what&how to turn the testing/debugging mode on.

I strip the exe to keep the filesize down, but using the full debug version is also kinda useless for these kinds of 'random' errors as they often are related to speed or heap corruption. Both of which seem to occur less or none at all when running inside a debug session. Logging is currently forced to the max level (debug) as a result of some extra messages to help find the close down bug.

1. open/create some model, let's call it modeltest.mpd and save its first version containing one brick at 0,0,0 only
2. in your OS shell or file manager, make the file modeltest.mpd read-only (i.e. simulate a problem with file writing later)k
3. go back to LDCad and add another brick to the model
4. press ctrl-S - nothing visible happens (so the user expects the model is saved but that's not true)
5. press ctrl-W - a popup about non-saved modifications appears. Surprising for the user, he just "saved" the model - but "no problem" - he presses the "Yes" button and believes now the is saved for sure. No error message appears and the model window is closed!
7. load the model back - the first version without the second brick is what you can see, there is no way to see the second version, the one you believed (twice!) it is saved.

This is not supposed to go that way indeed, I'll fix / improve it for the next version.

Same problem is with the file inside zip archive, only the problem description was more confusing. I hope it is clear now.

This was the one I was talking about, it is mentioned in the log though I'll add a nag message for it.