Cableguy Expert Licensed User Longtime User Feb 4, 2015 #1 Hi EREL The following code : Code: Copy LogColor($"Connected as ${Connection}"$,Colors.Green) returns as result: Code: Copy Installing file. ~i:** Activity (main) Pause, UserClosed = false ** PackageAdded: package:b4a.example ~i:** Activity (main) Create, isFirst = true ** ** Activity (main) Resume ** ~c-16711936:Connected as BLT So, no color is being aplied, thou I figure the c-16711936 is the color code EDIT: Code: Copy LogColor($"Board initialized :${LCDBoard.IsInitialized}"$,Colors.Red) Does work as expected Last edited: Feb 4, 2015
Hi EREL The following code : Code: Copy LogColor($"Connected as ${Connection}"$,Colors.Green) returns as result: Code: Copy Installing file. ~i:** Activity (main) Pause, UserClosed = false ** PackageAdded: package:b4a.example ~i:** Activity (main) Create, isFirst = true ** ** Activity (main) Resume ** ~c-16711936:Connected as BLT So, no color is being aplied, thou I figure the c-16711936 is the color code EDIT: Code: Copy LogColor($"Board initialized :${LCDBoard.IsInitialized}"$,Colors.Red) Does work as expected
Erel B4X founder Staff member Licensed User Longtime User Feb 5, 2015 #2 Have you tested it in the IDE (the colors will only appear in the IDE logs)? I'm unable to reproduce it.
Have you tested it in the IDE (the colors will only appear in the IDE logs)? I'm unable to reproduce it.
Cableguy Expert Licensed User Longtime User Feb 5, 2015 #3 Later in the day I will take a deeper look at it. 'Connection' is passed as an argument to the sub
Cableguy Expert Licensed User Longtime User Feb 5, 2015 #4 Strangely enough I can't reproduce it either... maybe some bizarre interaction with my lib fire event is causing the color to not show... Anyway, not a big deal. [EDIT] Confirmed, it's due to some bizarre interaction within a module I created and then compiled to LIB... I will try to figure it out... but since it's a private LIB, Its no biggie Last edited: Feb 5, 2015
Strangely enough I can't reproduce it either... maybe some bizarre interaction with my lib fire event is causing the color to not show... Anyway, not a big deal. [EDIT] Confirmed, it's due to some bizarre interaction within a module I created and then compiled to LIB... I will try to figure it out... but since it's a private LIB, Its no biggie
Cableguy Expert Licensed User Longtime User Feb 7, 2015 #5 So, by a fluke, I managed to reproduce the behaviour I mentioned as bug, see attached zip. Attachments smartstringlogtest.zip smartstringlogtest.zip 94.5 KB · Views: 437
Cableguy Expert Licensed User Longtime User Feb 8, 2015 #8 Am I crazy?? I changed the position of my second logcolor statement, but found that refreshing the execution while in rapid debug does make a difference. ie, clean run into debug mode, logcolors show correctly, restarting (the red arrow next to the green stop square) without stopping the debugger can sometimes give the color integer and not apply the color to the log statement as shown in the screenshot. disabling and re-enabling log filters also reproduce the behaviour change. Last edited: Feb 8, 2015
Am I crazy?? I changed the position of my second logcolor statement, but found that refreshing the execution while in rapid debug does make a difference. ie, clean run into debug mode, logcolors show correctly, restarting (the red arrow next to the green stop square) without stopping the debugger can sometimes give the color integer and not apply the color to the log statement as shown in the screenshot. disabling and re-enabling log filters also reproduce the behaviour change.
Erel B4X founder Staff member Licensed User Longtime User Feb 8, 2015 #9 The issue you are seeing is not related to the new smart strings feature. For some reason there is an additional character in the logs which prevents the logs parser to work properly.
The issue you are seeing is not related to the new smart strings feature. For some reason there is an additional character in the logs which prevents the logs parser to work properly.
Erel B4X founder Staff member Licensed User Longtime User Feb 9, 2015 #11 I was able to reproduce it. It will be fixed for the stable version.
T Troberg Well-Known Member Licensed User Longtime User Feb 9, 2015 #12 Cableguy said: so I am NOT Crazy!!!!??? Dahm! Click to expand... Well, not in this specific case. In a more general sense, well...
Cableguy said: so I am NOT Crazy!!!!??? Dahm! Click to expand... Well, not in this specific case. In a more general sense, well...
Cableguy Expert Licensed User Longtime User Feb 9, 2015 #13 Troberg said: Well, not in this specific case. In a more general sense, well... Click to expand... That's great news!!! (No, I'm not quoting the wrong person!)
Troberg said: Well, not in this specific case. In a more general sense, well... Click to expand... That's great news!!! (No, I'm not quoting the wrong person!)
