Topic : Ride7 editor ignores almost every highlighting option

Forum : Ride IDE

Original Post
Post Information Post
May 27, 2013 - 4:51pm
Guest

Greetings,my Ride7 editor keeps ignoring highlighting options. - Nothing is colored, e.g. typedefs are black and not red.- Functions are not bold.- C keywords like

Replies
Post Information Post
+1
0
-1
May 28, 2013 - 9:37am
Raisonance Support Team

Hello,
Your message has been snip, can you post it again?
Thanks
Regards,

+1
0
-1
May 28, 2013 - 11:37am
Guest

Hi, no problem,

my Ride7 editor keeps ignoring highlighting options.

- Nothing is colored, e.g. typedefs are black and not red.
- Functions are not bold.
- C keywords like "for" and "if" have the desired color.
- The Options->Editor Preferences->All Languages->General options work just fine.
- My files have the .c ending an are recognised as c-files.

Strangely enough, if I select a function call in the editor, it shows me the tooltip with the correct prototype. So I must assume it knows this is a function, but ignores the highlighting. This seems to happen in my big project as well in the example projects. The projects compile an link without error.

Is there some kind of option I'm missing?

I'm working with the Ride7 version I downloaded yesterday with an enterprise license.

+1
0
-1
May 28, 2013 - 1:45pm
Raisonance Support Team

Hello,
- Did you select "True" in Edit->preferences -> General -> Highlight the current line.
- Did you select the red colour in Edit->preferences -> C language -> Typedef.
- Did you select "Yes" in Edit->preferences -> C language -> functions.

Maybe try to reset to default the General and C language options. highlight the group options and click to the reset button.

best regards,

+1
0
-1
May 29, 2013 - 9:58am
Guest

Hi,

- Yes, it was activated by default.
- Yes, the "Foreground Color" was 128;0;0 by default.
- Yes, "Bold" was set to "Yes" by default.

I did as you told me. Now all my C keywords are gone, so "for" or "case" keywords are all black. All keywords in the "Keywords" section in my C language Properties are gone.

The typedef and function highlighting seems to work at a few files but in most cases it does not work. Be aware, that it seemed to work partially in a few files before I reset the settings to default, so no big change here.

Is it possible, that my project file is somehow corrupted? Before I installed the new Ride7 version I deinstalled a fairly old one. Maybe some old file corrupted my new installation? The old Ride7 version had the same issues as the new one, but I assumed it would be fixed with the new version.

I will try to do a clean deinstallation and reinstall Ride7 and the RKit. Will be reporting back.

+1
0
-1
May 29, 2013 - 11:34am
Guest

Hello,

I performed multiple deinstallations and installations using the guides you gave me. Unfortunatelly nothing seems to have worked. I also installed Ride7 and the RKit on the PC (Win7 x64 Prof. same as mine) of a coworker that never had any raisonance product installed. The same problems apply to this installation as well.

Below is a picture of my editor with some comments. This is taken from a fresh installation of Ride7 opening an example project after the project was "made" and "build". I ensured the highlighting options were on.

Best Regards,

+1
0
-1
May 29, 2013 - 4:26pm
Raisonance Support Team

Hi,
Can you control again if yes is selected for: Edit->preferences -> C language -> functions (It's working for us)
Concerning the typedef in red, It's true! is not red but if you right click on it and "go to definition" you should see "ADC_InitTypeDef" in red in STM32f10x_adc.c file.
This is a bug with the "go to definition" functionality, we are working to solve the problem.

best regards,

+1
0
-1
May 29, 2013 - 5:28pm
Guest

Hello,

here is a list of things I have done and the results (uncolored function means not bold).
--------------------------------------------------------------
1) Reinstalled Ride7/RKit, as I have told you.

2) Opend "Quickstart_STM32F107..." project -> Nothing colored, as I have told you. Both on my PC and the PC of my coworker.

3) Opend my work projekt -> Parts colored, as I have told you.

4) Worked on my project while waiting for your response -> I did not notice something changing.

5) Read your latest post and checked "Quickstart_STM32...." on my PC again -> Everything is colored and working!?

6) Went to the computer of my coworker and checked "Quickstart_STM32..." -> Still nothing colored. Checked the options, of course. "go to definition" not working with anything I have tried.

7) Opened my work project on my PC -> Significant more parts of the code are colored, yet still parts are uncolored. "go to definition" works with anything I have tried, uncolored functions/typedefs too. BUT: If I use the "go to definition" order on colored functions, it jumps directly to the definition of the function in the .c-file. If I use the "go to definition" order on a uncolored function, it jumps only to the declaration in the .h-file. Be aware, that uncolored functions have a definition in a .c-file and a declaration in a .h-file too. I assume the "go to definition" order does not work with the uncolored typedefs, but it seems they are all colored now. :)
--------------------------------------------------------------

It seems my problem is related to the "go to definition" bug. Can you tell me, when an update to fix this issue will be available? I'm on vacation till monday next week, so I can't respond till monday morning.

Kind regards,

+1
0
-1
June 4, 2013 - 4:01pm
Guest

Hi,

some additional information. Opening a project with a doubleclick from the explorer results in nothing colored. Opening a project within Ride7 results in mostly correct highlighting.

Kind regards,

+1
0
-1
June 10, 2013 - 3:13pm
Guest

Parsing the project source files is done in a background thread and could take some time depending on the size of the project. But at one point you should have all your source files properly highlighted.

You could check that Ride7 has parsed properly your files from the "View|Global Symbols" view. It should contain all the global symbols, types and functions...

+1
0
-1
June 26, 2013 - 3:15pm
Guest

One last addition, this is how I manage things now:

1) Write code.
2) Clear project.
3) Wait till the parsing is done (shown in the bottem text line).
4) Open project again within the Ride IDE.