Chroma coding going away...

Pep_SD

I've been dealing for a while with this problem but did not find any old thread about the chroma coding going away in some cases - I'm referring to the ability of Studio to put in different colors and fonts your variables, functions, etc...

Pretty often, which becomes quickly annoying and hard to deal with, my variables or defined functions loose their 'recognition' by Netlinx Studio. They stay in black when I type and there is no auto-completion.

Then I just have to add a <CRLF> right after the definition of the variable or the function to fix it.
But as soon as I type more lines, the problem keeps re-appearing and everywhere.

Anybody else having this behavior?

Paul-Eric

PhreaK

I get it occasionally as well. I seems to appear at random but if it's really worrying me I find that if I put a space in the variable or function name then remove it, the colour coding re-appears.

Hopefully this will be fixed in NS3 when they implement project wide colouring and auto-complete.

Spire_Jeff

There is a rescan current source file option. It is the letters AXS and an arrow that starts at the bottom of the X, wraps around to the right of the S and ends pointing at the top of the X. This will rescan the file and should fix any highlighting issues.

I find I occasionally have to do this on larger files. Also, stack_vars tend to mess with, but this seems to happen when I am copying/pasting code with the stack_vars.

Jeff

ericmedley

PhreaK wrote: »

I get it occasionally as well. I seems to appear at random but if it's really worrying me I find that if I put a space in the variable or function name then remove it, the colour coding re-appears.

Hopefully this will be fixed in NS3 when they implement project wide colouring and auto-complete.

I find that typically it's something way up the line that seems to cause it. For example I once found that when I did button stacks that the devices in some of the stacks farther down the list would loose their color. It would compile just fine. I found that if I commented the first buttone event in the stack this would occur.

something like this:

BUTTON_EVENT[dv_TP_1,01]// world domination butotns
BUTTON_EVENT[dv_TP_1,02]
BUTTON_EVENT[dv_TP_1,03]
BUTTON_EVENT[dv_TP_1,04]
BUTTON_EVENT[dv_TP_1,05]
BUTTON_EVENT[dv_TP_1,06]
BUTTON_EVENT[dv_TP_1,07]

all the dv_TP_1s below the comment would be black.

I discovered how to fix this by accident. You must remember to put at least one space between the end of the legit command and the first '/' of the comment. This fixes this bug.

BUTTON_EVENT[dv_TP_1,01]  // world domination butotns

I'm sure it's something like that.