.
Last edited:
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
bug (red variable not going away)
- Thread starter wheretheidivides
- Start date
- Similar Threads Similar Threads
Sometimes when you change things, variables stay red. You have to modify that line of code to make the red go away. It has to do with modifying a variable in 1 location that the other locations don't update. or sometimes when you change a viable (say in a dim statement), in the middle of a line, it changes red and stays red until you modify it.
I'm sure this has been mention as it's a common bug.
=============================================================
I wrote this line of code without a dim
it turned red
I added the dim
it stayed red
I had to add a space at the end (modify it) before it would not be red.
I'm sure this has been mention as it's a common bug.
=============================================================
I wrote this line of code without a dim
it turned red
I added the dim
it stayed red
I had to add a space at the end (modify it) before it would not be red.
Last edited:
+1 for me too. Not life threatening or anything, but it was odd and seems to have started doing it recently. In one case I duplicated a bunch of Activities that used similar code and copied/pasted the entire code to 5+ other Activities. Every one of them had UserClosed in the line "Sub Activity_Pause (UserClosed As Boolean)" highlighted in Red. I had done the same thing before without it turning Red.
I can't remember the exact date I started using 2.51, but I think I was using it when my variables stayed red. I just tried to get it to happen again though and can't. Could be something else leading up to it that caused it.