[SOLVED] Problems with syntax highlighting, and not working snappy

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Problems with syntax highlighting, and not working snappy

    Hello Segger Team,


    Embedded Studio does syntax highlighting in doxygen comments which is very helpful, but sadly not all variations are working:

    Could you add the syntax-highlighting also for the other variants?

    In addition, when a doxygen tag is incomplete, the end of the commend is not detected correctly for syntax highlight:




    You can drag n’drop code files out of the Embedded Studio main Window, which creates a new window. This is a very helpful feature which allows to have multiple code files open in parallel, but the new window is not snappy. If this window is moved to the edges of the desktop it is not snapped. The Embedded Studio main-window can do this (and also basically all other windows applications). In addition, in dark-mode the title bar is not black for those windows, don’t know if this is intentional.


    Regards
  • Hello Segger team,


    one more thing: Code Outline seem not to work correctly when namespaces are used in header files. Everything below and after the top namespace is ignored. Source files seem to be okay.


    Regards
  • Hello,

    Thank you for your inquiry.
    The doxygen comment stuff looks similar to what you reported here already:
    [SOLVED] Some feedback for Embedded Studio
    Correct?

    If so, it is still on our ToDo to improve this.


    Masmiseim wrote:

    You can drag n’drop code files out of the Embedded Studio main Window, which creates a new window. This is a very helpful feature which allows to have multiple code files open in parallel, but the new window is not snappy. If this window is moved to the edges of the desktop it is not snapped. The Embedded Studio main-window can do this (and also basically all other windows applications). In addition, in dark-mode the title bar is not black for those windows, don’t know if this is intentional.
    Unfortunately this is a QT limitation.


    Masmiseim wrote:

    one more thing: Code Outline seem not to work correctly when namespaces are used in header files. Everything below and after the top namespace is ignored. Source files seem to be okay.
    Could you provide an example that shows this issue?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Nino,

    the problem with the incomplete doxygen tag seems to be fixed with Embedded Studio version 7.12a. I can't reproduce it anymore.
    I had mentioned the problem with the doxygen syntax highlighting again since it was in the same area as the incomplete tags. Came up right away

    If it's a limitation of the framework you're using, I guess there's not much you can do about it. ☹

    I created a simple project for code outlining. Open the SayHello.h file and check the code outline. If you remove the namespace in line 9-12 the structure following the namespace will be displayed correctly again.



    Regards
    Files
    • Executable_1.7z

      (161.66 kB, downloaded 220 times, last: )
  • Hello,

    The doxygen issue is not fixed yet but on our ToDo. We do not have a fixed timeschedule for this yet.

    Regarding the code outline issue with namespaces. This is reproducible and should be fixed in the next Embedded Studio release.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.