Complex Lock mode for WP-34s

[BarryMead]

(04-29-2015 02:02 PM)emece67 Wrote:  If this complex mode lock will be a separated branch from the trunk, perhaps the CPXYES and CPXNO commands can be removed.

The last time I tried to check out the entire source tree with the command:
svn checkout svn://svn.code.sf.net/p/wp34s/code wp34s
I did not see a separate wp-34i or wp-34cpx branch. When will this new branch of the source tree be part of the official svn repository? The reason I am asking this question is because I created separate icons on my desktop for the Normal, and Complex WP-34s QT emulators and the way it works now the QT emulator under Linux uses the same $HOME/.config/WP-34s/ directory to store the wp34s.dat memory file for the complex emulator as it does for the normal emulator, and they are not compatible with each other. So after I run the Complex QT emulator I have to clear memory and reconfigure the display modes to switch back to the normal QT emulator and visa versa. It would be nice if the complex QT emulator had it's own $HOME/.config/WP-34CPX directory to store it's memory file to so that switching from the normal to complex QT emulators would not corrupt the memory file. If I run the non-QT emulator this is not an issue, because the wp34s.dat file for the non-QT emulator is stored in the same directory as the executable, so you can avoid cross-corruption by placing the normal and complex non-QT emulators in separate executable directories. For many reasons I prefer to run the QT emulator. The save directory doesn't seem to be changeable anywhere in the standard source. I think it is a function of the complicated Makefile and build system, but I am not sure. I was hoping that a new memory file save directory would
be automatic as a consequence of the new branch. It worked that way for the WP-31s. If not can anyone advise me as to how/where to make such a change?