M. Tavasti <firstname.lastname@example.org> wrote:
Wojtek Lerch <> email@example.com> > writes:
And I can repeat this, with plain PhAB actions. Without rebooting,
just do changes, save, exit PhAB, and try to re-open. Fine.
Could you perhaps teach me how to repeat it?
It sure sounds like a bug in PhAB, and it would be good to fix it…
Yes, I’ve done a bug report, and I’m happy to provide more info.
Can I send you the files? I have corrupted file, and working one.
What would be perfect is if you could do the following:
If your application has many modules, identify the one that’s
broken. You can do it by opening a new project in PhAB and
importing modules from the broken project until you hit the one that
has the problem.
Take the working version of your project, and import the module that
gets corrupted into another new PhAB project. Save one copy of this
project, and experiment with another one.
Hopefully, you will now be able to find a way to make PhAB corrupt
the file. When you do, send me the working version of the project
and a description of how to break it. Just email it to
Set of operations done is quite much (2 hours work) , and don’t know
which of them is bad one. Or is it related to file size or something.
While working on the app, save the app every five minutes or so. Use
the “Save As” option to alternate between two different names, and try
to re-open the app each time after saving. This way when the re-open
fails, you will have the previous unbroken version intact.
Wojtek Lerch (firstname.lastname@example.org) QNX Software Systems Ltd.