This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Some issues about IDE V4.53.00

Hi,

It cost me 2.000 Euro's to get the new uVision IDE with a 256Kb limit. I use the Keil uVision IDE for a few years with much pleasure. I found some issues with the new version V4.53.0.0 which I will share with you and I also send a ticket to Keil support.

Hi,

I'm using uVision V4.53.0.0.
I would like to share some things that I think should be corrected:
- clicking inside a source code, then scroll down, then use ALT+F+S to save the file not always highlights the menu bar 'File'. You can check it out by continuously left mouse click in the code and then press the left ALT key. You will see. (leaving me with a lot of 'fs' strings in the code)
- pressing CTL+F to find some string then after ENTER I would like this search window to disappear not blocking found text.
- almost ALL texteditors have the same problem: if I want to search for some text, when found, please show this text line in the MIDDLE of the screen in stead of at the top or at the bottom so I can see the surrounding code
- please make the files relocatable in the editor by dragging the file tab to the wanted position as I like to place the header files at the right of the souce (.c ) file. (this worked in some older versions)
- How can I disable Outlining for all sources once and for all?

I think it's a great IDE and I like it very much: just my two cents.

Best Regards,

Henk

Parents
  • Yes, you are right - Visual C has this "change and continue debugging" feature, which of course is very nice for debugging, and this of course requires a full on-the-fly parsing of the code.

    Eclipse also needs it, as debugging in Java / Android is so poor - so on-the-fly is really ultimately required.

    For Microcontroller "On-the-fly" Intellisense of course also would be very nice. I know some Microcontroller development systems will, which provide Itellisense "static" (not on the fly - only after successful built). But at least for my working style this does not make much sense, as when I finished a new software modification that much, that the built is complete, then it is nearly all done. So I really would need it more "on-the-fly", while entering new code / new classes.

    But I understand that this is really a difficult job for the editor programmers - it somehow goes into the direction to support a second "on-the-fly" compiler only for intellisense.

Reply
  • Yes, you are right - Visual C has this "change and continue debugging" feature, which of course is very nice for debugging, and this of course requires a full on-the-fly parsing of the code.

    Eclipse also needs it, as debugging in Java / Android is so poor - so on-the-fly is really ultimately required.

    For Microcontroller "On-the-fly" Intellisense of course also would be very nice. I know some Microcontroller development systems will, which provide Itellisense "static" (not on the fly - only after successful built). But at least for my working style this does not make much sense, as when I finished a new software modification that much, that the built is complete, then it is nearly all done. So I really would need it more "on-the-fly", while entering new code / new classes.

    But I understand that this is really a difficult job for the editor programmers - it somehow goes into the direction to support a second "on-the-fly" compiler only for intellisense.

Children
  • PS: But perhaps it is easier, if we would require working intellisense after failed build - this would be very helpful. Then I could program the classes / structs, then do a failed build, and then start with coding the functions - in this situation of course it would be great to get intellisense access to the class variables. No problem for me to do some built command to "enable" intellisense for some new classes - this would be great.

  • PPS: If we are discussing these issues, please also do not forget, that currently precompiled headers do not work, if the c/cpp modules are organized in different folders. It would be VERY nice if precompiled headers would work also with folder-tree-organized source code. (best with some easy method to define the precompile stop point: either the possibility, to define a specific h file to be used for precompiled headers (and only working if this h file is the first h file to be included of course), or some simple method to define the "#pragma hdrstop" - e. g. at the end of this "important and very big central" h file).

  • What is this project of yours? Hope it does a little more than just flash an LED.

  • It is a motor control system with several motors, USB connection and some further high speed AD sampling - is this ok :)? (Additionally it works with many control cards linked by some bus system, so it is really a bit complex).