PureBasic Forum

When any expression is used for an issue (i.e. \bTODO\b ) the issue is not marked (has the issue background color changed) but does display in the following source code (for either line):


Highlighting is shown for both lines if the source code is changed to this (or has a variety of other characters added or removed):

What exactly do you mean? Here it works, maybe because I'm using the x86 version.

Try ; TODO with a space before.

@c4s: I mean when the source code is as I showed and the expression for the issue is as I showed, neither of the two comment lines are highlighted even though they show under the Issues Tab in the PB IDE.

When I change the text from the source to match the second text example (by typing a 2 in the word 'Procedure') then both comments become highlighted in addition to being listed under the Issues tab in the PB IDE.

I appreciate the comments regarding the x86 version. When I get a moment I will have to install that version to test it there also.



@Thorsten1867: Thanks for the suggestion but it doesn't change the situation.

As I stated in my explanation the lines match the 'issue expression' as it is written and are displayed in the Issues Tab. However they are either both highlighted or both not highlighted based on text that would seem to be totally separate from the comments. On the one hand, the text is before the comment and not a part of it and on the other hand, the text is not even on the same line.


I had first noticed that when loading a source with 'issues' that are supposed to be both highlighted and displayed under the Issues Tab the issues don't seem to be highlighted until the cursor is moved over the line where they are. However I stumbled on the situation where no amount of massaging would cause issues to be displayed after a certain source line. They would be displayed before but not on or after that line (for the rest of the source).

I narrowed down one instance that shows this and posted it above. There may be more than one factor causing it and I've found other examples where it happens. I just need to find one where someone can confirm the bug.

Sorry, I'm still not able to reproduce it. To do so I pasted your sample code and changed the TODO expression from \bTODO\b.* to \bTODO\b:

Both are highlighted and shown in the Issue Tool. Of course with ".*" the whole line will be highlighted and shown.

Here's my screenshots (please, no comments on the color selection ).

Non-working:


Working:



It doesn't matter what the expression is, it will match but not highligh in these situations. To show you, here is your example:

Non-working:


Working:

This is not a bump, just wanted to add a little more info.

I verified this happening with the x86 version as well as the the 64bit version.

The non-commented text can also be shortened to the following sample (incomplete code statement) to prevent issue highlights showing up for it and all the lines following it.


As was true before, if any characters are added to the text before the '.' then highlighting will start to work. If either a '(' or a ')' are added to the text after the '.' but before the 'c' then highlighting will turn on also. Other characters added after the '.' don't seem to cause any change and leave the issues unhighlighted but still displayed in the issues tab.

Sorry Demivec, I'm still not able to reproduce it...

I copy and paste your above code into a new tab and it's immediately highlighted (PB 5.30b4, Windows 8.1, x86).

Edit:
What I just found out is that when switching the encoding from Utf8 to Plain Text (I have Utf8 enabled by default) all highlighting is gone until I select the Issue code part.

I have Utf8 on by default also. After your remark about plain text demonstrating the problem I switched my settings from Utf8 to Plain Text and back again but still wasn't able to get it to show highlighting with the sample of problem text.

I appreciate your attempts to confirm this. I'll just have to sit back until more people experience it.

Because it seems to happen with the phrase 'procedure.' it should crop up more.


I'm also using windows 8.1 x64.

Have you try to delete your prefs manually, or start PB with the /PORTABLE flag ?

Sometimes there are some very fascinated issues, if you hold the preferences from one pb-version to another....
So try to start the IDE with a fresh preferences environment.

Maybe this helps...

@Bisonte: I thank you for your suggestions.

I exported my preferences and then reinstalled the 64bit version to a clean directory and set it to load with the /PORTABLE flag.

I then loaded it and pasted the sample of problem code above, it highlighted correctly.

I then opened and imported my previously exported preferences. When I then applied them the highlighting went off.

So it would seem the preferences are affecting things. I've tried comparing the text of the preference files, the default one with the one after the imported settings.

My final conclusion is that I found that if the BackgroundColor setting was RGB(255,255,223) the highlights were shown, if it was RGB(255,255,210) then it wasn't shown. Other randomly picked values for color didn't work either. It didn't matter if the value was placed in the preference value before loading (as a single integer) or if the values were selected in the preference window, both resulted in the same effect.


Here is a copy of the default colors (working):


My colors which did not work according to the scenario described in the first message):


Out of all these the BackgroundColor seemed to be at least one determining factor.

I also have the same behaviour (Windows 8.1 x64)
Tried PB530 x86 and x64 : same
BUT:
If the TODO is outside a procedure, it works

Another behaviour, in the preferences when you checked the option "Show in procedure browser", you cannot unchecked it.

@flaith: According to what you said, when I use this sample it highlights only the last TODO:




For this, I believe you need to click update, and apply.

Ouch!
Thanks