+0x - Plus Symbol Used In Hexadecimal Constant

[OrionSR]

const
    m_nsize = +0x1C
end

The + is used in documentation to indicate a relative offset.
This format works when used as a constant in SB, but the highlighting is lost for the text of the constant.

[x87]

core/src/language_service/scanner.rs

Line 250 in 10101e9

if value.starts_with("0x") || value.starts_with("-0x") {

[x87]

@OrionSR test with this version
core.zip

[OrionSR]

The +0x highlighting is working but other issues have popped up.

The text for all constants in the CONST..END construct is not highlighted unless that line is selected. Eventually it all fills in.

When switching between SCR and SAv1 edit modes, the highlighting for text of constants breaks. The highlighting that was enabled by scrolling over the line is removed when that line is selected.

Update: I'm currently using SB v3.8.0. Just used the upgrade tool. Need to retest.

[OrionSR]

After retesting with a current SB build; the +0x highlighting is working and no new issues are immediately apparent.

I still have problems with larger text scripts. If I edit a line with a constant the highlighting disappears for all constants until I scroll to the const..end construct and edit a line. I suspect this might be resolved by adjusting Sanny's scanning range option but haven't tested the idea. (Never mind, scanning range 1000 fixed this issue.)

For some odd reason, these two constants from ePickupType never highlight.

    PropertyLocked = 17
    PropertyForSale = 18

IIRC, this is expected behavior.

const 
  Font_Pricedown = 0
  Font_Aharoni = 1
  Font_Gothic = 2
  Font_Beckett = 3   
  text_font = Font_Aharoni
end

text_font is not highlighted.

[x87]

Thank you for testing!

For some odd reason, these two constants from ePickupType never highlight.

can you show how you define and use them ?

IIRC, this is expected behavior.

Yes sannybuilder/dev#134

[OrionSR]

can you show how you define and use them ?

Um... Well? I defined them shortly before:

//  tPickupFlags
    UsedPickup = 0
    NoAmmo = 1
    HelpMessageDisplayed = 2
    PickupNearby = 3
    PropertyLocked = 4
    PropertyForSale = 5

Defining the constant twice should break the highlighting. So everything seems to be working properly.

[OrionSR]

Curious: In SB v3.8.5, BREAK is highlighting but CONTINUE is not. Nether is defined in keywords.ini since the update. Both are listed under compiler.ini.

[x87]

add Break & Continue to keywords.ini

[x87]

break is highlighting in SA SCR because of 084C=BREAK

[x87]

@OrionSR could you please test the recursive highlighting with this version?
core.zip

[OrionSR]

Is there anything in particular I should be looking for?
Should I keep scan range at 1000 or drop it back to 250?

[x87]

check your example with text_font = Font_Aharoni.
text_font should now be getting the same coloring as Font_Aharoni. try different types

here is a updated version

core.zip