Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » Debugging mouse over popup need to be improved
| Debugging mouse over popup need to be improved [message #44733] |
Wed, 10 June 2015 08:51  |
cbpporter
Messages: 1406
Registered: September 2007
|
Ultimate Contributor |
|
|
Every time I use TheIDE for debugging I'm having a bad time.
Te mouse over popups are a big part of it. They are fairly useless.
To be made any better, they should:
- not clip out of the bounds of the screen. Mouse over anything past the middle of the screen? Most of the content will be clipped and you need to scroll your window.
- support multi line display, having multiple lines represent thing in the inheritance hierarchy.
|
|
|
|
|
|
| Re: Debugging mouse over popup need to be improved [message #44737 is a reply to message #44736] |
Wed, 10 June 2015 22:23  |
cbpporter
Messages: 1406
Registered: September 2007
|
Ultimate Contributor |
|
|
Windows with the SDK, 32 bit compiler ran from 64 bit IDE.
A few additional notes:
- the little panel to the right of your watched variables list, the one that populates with detail once you click on a variable is a lot more useful than the popup, but the data is formatted the same way, so I'm guessing the data comes from the same component. Using similar output in the popup would be a lot better.
- I have my Windows task bar on the right. A lot of applications have problems with this, but not mine, since I know that I need to use a different WindowsAPI function to get the right desktop rect. Might be partially the cause of the clipping. I'll tell you tomorrow which function it is, I don't have access to code right now.
- a bit of smart displaying might make things more pleasant, like getting rid of the Moveable entry, bringing short String entities to the foreground, custom and better Vector display. BTW, highlighting variables called "name" or "Name" when they are strings, or id, ID, type and a few more is kind of heuristic, but I can guarantee that it would pay off for a lot of cases, especially for the limited in space popup.
- sometimes the popup just does not appear. Having it work more often than not is a lot worse than having it work rarely because it catches you by surprise, and it fails for no apparent reason, like variable.field.
- having the debugger starting to misbehave even with plain int variables when multiple "int i" are present in a function is a huge pain. I started selectively but retroactively making sure I use a variable name once only in a function because of this.
|
|
|
|
Goto Forum:
Current Time: Sat Oct 05 10:55:47 CEST 2024
Total time taken to generate the page: 0.02285 seconds
|
Members
Pages
Help
Register
Login
Home
