F flyingbag Member Licensed User Longtime User Sep 12, 2012 #1 Hello, For some reason - the variable "subsetret" shows up in red in my sub. If I change the variable name - it disappears - but will come back again in red the next time i start B4a. Note- B4a does NOT give me any compilation error - and my app runs fine...but I find it interesting that B4A should choose to show up this variable declaration in red font as if its an error... It disappears if I put the variable in Sub Globals (but i would prefer not to do that) Cheers flyingbag Attachments error_red.png 21.2 KB · Views: 535
Hello, For some reason - the variable "subsetret" shows up in red in my sub. If I change the variable name - it disappears - but will come back again in red the next time i start B4a. Note- B4a does NOT give me any compilation error - and my app runs fine...but I find it interesting that B4A should choose to show up this variable declaration in red font as if its an error... It disappears if I put the variable in Sub Globals (but i would prefer not to do that) Cheers flyingbag
B bvdijk Member Licensed User Longtime User Sep 13, 2012 #2 Just because I was curious I gave it a try, doesn't appear in red in my IDE (v2.02)... Upvote 0
P Penko Active Member Licensed User Longtime User Sep 13, 2012 #3 Even Erel has said that it's possible the IDE doesn't show this syntax correctly at times. This happens to me at least once at a daily basis. For me it is fixed when I compile. Does it happen to you? There is no need to worry. Sent from my Next7P12 using Tapatalk 2 Upvote 0
Even Erel has said that it's possible the IDE doesn't show this syntax correctly at times. This happens to me at least once at a daily basis. For me it is fixed when I compile. Does it happen to you? There is no need to worry. Sent from my Next7P12 using Tapatalk 2
F flyingbag Member Licensed User Longtime User Sep 14, 2012 #4 Thanks - thats good to know I am not the only one seeing this It goes away and comes back out of freewill... I believe this happens when i declare two functions with the same name private to two different modules... but i might be wrong if this is the only time it happens... Upvote 0
Thanks - thats good to know I am not the only one seeing this It goes away and comes back out of freewill... I believe this happens when i declare two functions with the same name private to two different modules... but i might be wrong if this is the only time it happens...
