[Resolved] Problem with AU3 Scite

[Glyph]

$Label2 = GUICtrlCreateLabel(@OSVersion&" / "&@ProcessorArch, 8, 40, 150, 17)

Returns WIN_2003

Scite does not highlight the @processorarch

and it highlights the old @OSArch, which is an undefined macro.

Here's the versions I am using:

3.2.12.1 @ AutoIt

1.7.7.0 @ Scite

[sciTE4AutoIt3]

date=2-11-2008

Maybe these are bugs?

Or is there an option I missed?

Edited November 8, 2008 by Glyph

[Jos]

The syntax colors are depending on the loaded definition files.

Run SciTEConfig (Alt+1) and that will tell you which definitions are loaded for SciTE.

Jos

Edited November 8, 2008 by Jos

[Glyph]

The syntax colors are depending on the loaded definition files.

Run SciTEConfig (Alt+1) and that will tell you which definitions are loaded for SciTE.

Jos

Ah, that fixed the highlighting issue, but still an issue with the WIN_2003 OS return.

And the config is ctrl+1 not alt+1.

Just for anyone who may look at this in the future.

[Jos]

Ah, that fixed the highlighting issue, but still an issue with the WIN_2003 OS return.

And the config is ctrl+1 not alt+1.

Just for anyone who may look at this in the future.

Rigth

Your other issue is fixed in :

3.2.13.2 (15th June, 2008) (Beta)

AutoIt:

- Changed: @ProcessorArch changed to @OSArch as it was misleading.

- Changed: Size limits removed from RegRead() and RegWrite() (previously 64KB for some registry types).

- Changed: RegRead() and RegWrite() no longer use hex strings for REG_BINARY types - native binary datatypes are enforced.

- Fixed #380: @OSVersion for Windows XP 64-bit Edition.

[dbzfanatic]

Technically the basic structure for XP 64 bit was based on Windows Server 2003 64 bit. I'm running XP64 as we speak and I have noticed this,but it never really bothered me. Jos pointed out that the "error" was fixed so I think all questions have been answered,yes?

[Glyph]

Technically the basic structure for XP 64 bit was based on Windows Server 2003 64 bit. I'm running XP64 as we speak and I have noticed this,but it never really bothered me. Jos pointed out that the "error" was fixed so I think all questions have been answered,yes?

Ah, I was wondering why they were so similiar (when you do windows updates brings you to same page in Win XP x64 as Win 2003 x64)

Thank you very much, Jos and dbzfanatic!

[dbzfanatic]

You're welcome. It's also a reason M$ decided not to port SP3 to XP64 (cheapskates).