Sounds weird. I'm not very familiar with 64bit machines and tracking GCC errors is too hard for me so I guess there's no way I can fix that... If GCC 4.x works fine on some platforms where 3.x fails I'll have to mention it in the readme.
I must be missing something here...The GUI looks good, you are too hard on yourself.
My top 3 enhancement requests are:Anyway, I think its an encouraging project. The world really needs an IDE for debugging QT4 programs.
- Double clicking a method in the class browser should go to the code for the method, currently all the methods open the header file instead. The class name its self could do that.
- A button to toggle between .h and .cpp file for the same class. I am always going back and forth between these two.
- Some obvious way of adding a breakpoint. Am I missing something here?
QDevelop locks up on both my Gentoo machines, so you are already ahead thereThere are currently two ways to set breakpoints :
- I've thought about that but didn't find time to do it in a proper way yet. It should be added in a feature release but don't ask me when, I'm rather busy ATM.
- I was thinking about a context menu for class names to open either header or source. If that's not what you mean could you precise your button idea?
- I admit Edyuk lacks documentation and breakpoints are not that obvious...
Note : the first method currently REQUIRES breakpoints to be set BEFORE starting debugging.
- graphically by right clicking on the leftmost part of the editor (on concerned line) and toggling the breakpoint entry
- by hand through the "custom command" entry in Debug menu and typing the corresponding command
I'm thinking about improving this breakpoint issue (by adding a shortcut, among other things) but, once again, I lack time... Anyway, if I'm lucky and fast enough these three might find their way in the next upcoming release which will be issued before the contest ends.
Bookmarks