I experience these two problems. I would like to know how to avoid them. There is maybe a problem between my chair and the keyboard, but I would like to ask others about this.
1) (SDK Symbian 9.2) I have installed the development environment in default places. I'm maintaining few non trivial projects and sub-projects. It happens from time to time. I must delete/clean all project files in the epoc32 build directories because the sources in Carbide C++ are simply ignored, even thought I rebuilt the project, cleaned it. The console output looks like everything is all right, sis/sisx packages looks like fresh but the problem is that they contains an old binary file - event thought the sources were compiled. The problem is that it is often not obvious that an old binaries are packed within the sis/sisx files. For example in case when the program panics/crashes. I'm curious about it because if I do (random)9 compilations correctly, without problem, then why the 10th compilation is pretended, using a sort of cache or so?
2) If I create a container using Carbide UI Design Editor, then again from time to time the editor just says something like: I can not save the new design because I do not understand the code, it is maybe crippled. It happens usually ifI add a method handling an event. If I look in the code, it's terrible view, because the *** editor ruined my code (reader might say that I should avoid generated areas, yes I do). Repeatedly using SVN to fix this is annoying procedure because even thought I manage to fix that, I loose time, and every time there is no backup version in svn unless I do an atomic commits, which does not solve the problem either.
Thank you for your comments.