Unsupported syntax hiliting version of QE.

[hutch--]

I spent some time about 18 months ago playing with the option of syntax hiliting in QE and while it was no melodrama to get a version of it working there were fundamental problems with some of the later clear type fonts that made it difficult to make reliable. With fixed bitmap fonts it did not appear to have any real problems. I am in debt to zooba for helping test this prototype.

It comes with a 1 meg keywords file that contains the list of words that are hilited which include the intel mnemonics, windows api functions registers etc ....

The size of the keyword file slows its load speed up enough to notice and as QE is a multiple instance editor every instance must load the keyword file but it seems to run OK on a late model box.

Please note that this syntax hiliting version was a prototype and it is not supported or updated, it was based of the first QE 3.5 version so its reasonably similar to the current version.

www.masm32.com/download/qe35synt.zip

[Vortex]

Very nice work Hutch :U I wish you would support syntax highlighting in the future versions of QE.

[GregL]

Well, I hate to be the bearer of bad news but when I open a file it looks terrible for a couple of seconds and then crashes. I'm using the Consolas font (monospaced, TrueType).

[grofaz]

I like it! And I'd really like it if I could set the background to black, text to green, and customize the highlighting scheme to suit.
But it's a big improvement as is too. Thanks hutch for uploading it. Please incorporate it into your latest QE.

regards

[MichaelW]

It works for me, under Windows 2000, but IMO much of the small benefit of syntax highlighting is lost against the background, because the colors provide too little contrast.

[hutch--]

I was lucky at the time that zooba helped test this version but there were fundamental problems when using vector fonts and an added problem with the cleartype technology that made the fonts darken after each screen refresh and I could not get it reliable so I just put it aside.

The technique was based off Iczelion's original but with a number of things fixed and a fast hash table for the word recognition so it would handle the large word count of APIs but the association between the internals of a rich edit control and the API DrawText() appears to have been lost.

I would have happily set QE up with the option to use syntax hiliting if I could have got it to be reliable but after working on it for a while I well understand why the guys who write IDEs gave up on rich edit controls for this capacity and wrote their own custom editors.

[Cobra]

Couldn't you use the fasm/radasm edit control for this purpose?