Changes between Version 10 and Version 12 of Ticket #4078
- Timestamp:
- 2016-11-14T13:51:16Z (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4078
- Property Cc added
-
Ticket #4078 – Description
v10 v12 9 9 1. Right-clicking on an empty spot in the library browser doesn't do anything. I was expecting it to open a context menu where you can choose to add things, like folders for debugging, instead of having to go the File menu. 10 10 1. ~~After some further use I realised that this is not quite true, since strings are shown unquoted in the variable browser. I think it would be better to quote strings, because currently you can't differentiate between e.g. the string "1" and the number 1 without taking the extra step to look at the variable's type.~~ 11 1. Another small issue: the variables in the variables browser are sorted alphabetically. That's fine for the local variables, but a bit annoying when record members are also sorted that way. As a developer I know many of the data structures in the compiler by heart, so I find it confusing when the order in OMEdit doesn't match the declared order I expect.11 1. ~~Another small issue: the variables in the variables browser are sorted alphabetically. That's fine for the local variables, but a bit annoying when record members are also sorted that way. As a developer I know many of the data structures in the compiler by heart, so I find it confusing when the order in OMEdit doesn't match the declared order I expect.~~ 12 12 1. OMEdit doesn't mark the line the debugger is on in any way, except for highlighting it. But if you click on another line it will highlight that line instead, and you won't know which line is active except if you double-click on the current frame in the stack browser to select the active line again. I would suggest that either the active line should be highlighted with another color than the currently selected line, or to have some symbol in the margin that indicates the active line. 13 13 1. The program, work directory and GDB path will often be the same for several debug configurations, so some way of cloning debug configurations would be nice.
