Home » U++ TheIDE » U++ TheIDE: Layout (Forms) Designer » Toggle layout/text view in Layout Designer
Toggle layout/text view in Layout Designer [message #24247] |
Thu, 07 January 2010 11:23  |
 |
MAD!C
Messages: 7 Registered: February 2009 Location: Germany
|
Promising Member |
|
|
being a upp newbie, i initially wondered why i couldn´t call the designer on layout files (version 1820). now i got the issue:
displaying contents of a .lay file, layout designer switches to text view when i compile and run my package pressing [F5] key. just tested: also happens using the menu command "debug/run (in debugger)"
is this a bug, or how can i switch back to layout view? i found no way other than restarting ide.
in addition, having closed the running application, the debugger still hangs on the final commands, requiring me to jump out of functions [shift-F11] 2 times to really close the app.
[Updated on: Thu, 07 January 2010 11:23] Report message to a moderator
|
|
|
|
|
|
Re: Toggle layout/text view in Layout Designer [message #24252 is a reply to message #24247] |
Thu, 07 January 2010 13:26   |
mr_ped
Messages: 826 Registered: November 2005 Location: Czech Republic - Praha
|
Experienced Contributor |
|
|
generally speaking:
- during debug mode the layout editor is forced into text mode, because it makes much more sense in debugger, when you step over that part of code. (Layout is regular C++ code, so it can be debugged)
After debug mode is finished, it should turn back into original mode (either visual or text).
During edit you can switch the mode with Ctrl+T, if you are interested what C++ code is generated, or adjust something what is difficult to do visually.
MINGW + debugger is not working very well. Mirek(luzr) is mainly interested into MSC debugging in MS win environment, so unless you want to dig in (very deeply and low level) and figure out what are current problems and how to fix them (Mirek is basically blaming gdb for most of the problems, so if you are fluent with gdb, you may try to use it outside of TheIDE to figure out what works well and what not).
I'm trying to avoid debugging as much as possible (tried TDD for simple small projects which were quite mathematical, so it was pleasure to do it that way ... for GUI applications it will be tougher, there's no problem to test inner "model" with UnitTest++, but I can't help with GUI testing so far), because I like to stick with gcc. (although I do try to compile my sources with MSCC just to make it more robust, it often helps to catch some minor bugs or ambiguous things in source)
If you insist on debugging and MS Win, you should definitely consider using Win SDK + MSCC, TheIDE debugger works much better in such case.
|
|
|
|
|
Goto Forum:
Current Time: Tue Apr 29 00:22:15 CEST 2025
Total time taken to generate the page: 0.00962 seconds
|