Hi all
I have added a wordlist feature to RadASM.
- Auto case convert.
- Ctrl + Space shows wordlist.
- Code properties are temporarely added to the wordlist.
Read the WordList.txt to find out more.
Give me some feedback as I am not shure that this feature is really useful (might convert case on words that it shold not convert, ie struct items).
KetilO
Important:
First time installers need to install complete package first.
Update: 4 dl's. There was a bug, dl again.
04-15-2002, 66 dl's. Deleted attachment.
Look further down for complete package.
I have added a wordlist feature to RadASM.
- Auto case convert.
- Ctrl + Space shows wordlist.
- Code properties are temporarely added to the wordlist.
Read the WordList.txt to find out more.
Give me some feedback as I am not shure that this feature is really useful (might convert case on words that it shold not convert, ie struct items).
KetilO
Important:
First time installers need to install complete package first.
Update: 4 dl's. There was a bug, dl again.
04-15-2002, 66 dl's. Deleted attachment.
Look further down for complete package.
CTRL+SPACE causes an app error on my Win2K:
The instruction at "0x00402ba6" referenced memory at "0x00000000". The memory could not be "read".
The instruction at "0x00402ba6" referenced memory at "0x00000000". The memory could not be "read".
Hi jademtech
Yes, RadASM does GPF if you dont add "Word=masmApiWord.api" to section in the masm.ini file.
The section should look like this:
Trig=invoke
Call=masmApiCall.api
Const=masmApiConst.api
Struct=masmApiStruct.api
Word=masmApiWord.api
I will fix the bug.
KetilO
Yes, RadASM does GPF if you dont add "Word=masmApiWord.api" to section in the masm.ini file.
The section should look like this:
Trig=invoke
Call=masmApiCall.api
Const=masmApiConst.api
Struct=masmApiStruct.api
Word=masmApiWord.api
I will fix the bug.
KetilO
Thanks :alright: keep up the great work :)
sorry... i just realized there was a bottom to the wordlist.txt
sorry... i just realized there was a bottom to the wordlist.txt
I don't understand how it works.
Where are the options ?
1. Wordlist Convert. Performs case convert if checked.
2. Prop. to Wordlist. Properties are added to the wordlist if checked.
Where are the options ?
1. Wordlist Convert. Performs case convert if checked.
2. Prop. to Wordlist. Properties are added to the wordlist if checked.
Hi The Svin
For now the word list contains only a few words, but your projects code properties are temporarely added to the word list. Type "null," and the word "null" becomes "NULL". The same goes for any of your proc, constant, struct and macro names.
When you press Ctrl + Space a listbox with the word list pops up.
The options are well hidden on the Options / Code Editor menu.
KetilO
For now the word list contains only a few words, but your projects code properties are temporarely added to the word list. Type "null," and the word "null" becomes "NULL". The same goes for any of your proc, constant, struct and macro names.
When you press Ctrl + Space a listbox with the word list pops up.
The options are well hidden on the Options / Code Editor menu.
KetilO
Thanks, KetilO.
I found these "well hidden" busturds with your help :)
I found these "well hidden" busturds with your help :)
Hi KetilO:
Well done
Is it possible for user to change the Ctrl-Space in order to show the wordlist.:confused: In my system Ctrl-Space will pop up the IME (Input Method Editor)
I found something in masmApiWord.api file. When there is a blank line in the file, the word after the blank line cannot auto case convert.
eg
NULL
TRUE
<- - - - - - - Blank line (nothing just CR)
FALSE
CommandLine
NULL and TRUE can auto case convert. FALSE and CommandLine cannot.
Thanks
Well done
Is it possible for user to change the Ctrl-Space in order to show the wordlist.:confused: In my system Ctrl-Space will pop up the IME (Input Method Editor)
I found something in masmApiWord.api file. When there is a blank line in the file, the word after the blank line cannot auto case convert.
eg
NULL
TRUE
<- - - - - - - Blank line (nothing just CR)
FALSE
CommandLine
NULL and TRUE can auto case convert. FALSE and CommandLine cannot.
Thanks
Hi ASM
Yes, blank line causes a break in the word list. I will fix it.
Too bad, Ctrl+Space is sorta standard for such things. I will see if I can come up with something.
KetilO
Yes, blank line causes a break in the word list. I will fix it.
Too bad, Ctrl+Space is sorta standard for such things. I will see if I can come up with something.
KetilO
Bug with RadASM auto correction:
In the second line of
invoke DialogBoxParam, hInstance,
[*GETWINNAME*],NULL,
if you push ENTER between "," and "NULL," this happens:
invoke DialogBoxParam, hInstance,
[*GETWINNAMNULL
NULL,
KetilO, do you think it would be better if with TXT files highlight mode is turned off?
I mean, if I work with a TXT file in RAD asm, like I do now, It would be better if it did
not highlight all these in's and if's :) Maybe highlighting should be enabled only where
file extension is ASM, INC, RAD(for dialog to window plugin templates) and TPL.
One more thing.. why isn't the text between two COMMENT statements in color specified for remarks?
And.. I've just noticed that when typing in a string (text after " or ' ) the last letter is always
black until you change the line or type in something after the final " or '.
These 2-3 things are not that important... however I wanted to let you know for these features in
case you didn't notice them yourself.
See you later.
In the second line of
invoke DialogBoxParam, hInstance,
[*GETWINNAME*],NULL,
if you push ENTER between "," and "NULL," this happens:
invoke DialogBoxParam, hInstance,
[*GETWINNAMNULL
NULL,
KetilO, do you think it would be better if with TXT files highlight mode is turned off?
I mean, if I work with a TXT file in RAD asm, like I do now, It would be better if it did
not highlight all these in's and if's :) Maybe highlighting should be enabled only where
file extension is ASM, INC, RAD(for dialog to window plugin templates) and TPL.
One more thing.. why isn't the text between two COMMENT statements in color specified for remarks?
And.. I've just noticed that when typing in a string (text after " or ' ) the last letter is always
black until you change the line or type in something after the final " or '.
These 2-3 things are not that important... however I wanted to let you know for these features in
case you didn't notice them yourself.
See you later.
Hi Milos
Thanks for the bug report. I will fix it.
The way hiliting works in RadASM makes the COMMENT a bit tricky, but I will look into it.
Not hiliting unknown file types is a good idea.
KetilO
Thanks for the bug report. I will fix it.
The way hiliting works in RadASM makes the COMMENT a bit tricky, but I will look into it.
Not hiliting unknown file types is a good idea.
KetilO
Hi all
I have fixed known bugs.
Note: This is a complete package.
First time install:
Unzip to C:\RadASM
Upgrade:
Unzip to temp folder and move selected files.
(All addins, masmApiWord.api and RadASM.exe)
Read WordList.txt on how to modify masm.ini
Earlier versions than 1.1.0 also needs to move RadASM.ini
and masm.ini
KetilO
Attachment deleted.
Look Here for latest.
I have fixed known bugs.
Note: This is a complete package.
First time install:
Unzip to C:\RadASM
Upgrade:
Unzip to temp folder and move selected files.
(All addins, masmApiWord.api and RadASM.exe)
Read WordList.txt on how to modify masm.ini
Earlier versions than 1.1.0 also needs to move RadASM.ini
and masm.ini
KetilO
Attachment deleted.
Look Here for latest.
Hmm... may i make a suggestion for RadASM? i don't think it should be difficult to implement...
between a comment, like,
COMMENT / Blah /
all the Blah remains one colour (perhaps the same as code commented by the ';'). it looks fine right now until one types in "if," "not," "while," or any such words... then you get, well, colourful comments :)
between a comment, like,
COMMENT / Blah /
all the Blah remains one colour (perhaps the same as code commented by the ';'). it looks fine right now until one types in "if," "not," "while," or any such words... then you get, well, colourful comments :)
Hi jademtech
I will find a way to solve the COMMENT problem, just give me a little time and I will come up with a simple solution.
KetilO
I will find a way to solve the COMMENT problem, just give me a little time and I will come up with a simple solution.
KetilO
Nice, KetilO! This is especially useful when working on larger projects.
I don't know how hard/easy this may be, but is there any way to see what type these keywords are? Perhaps with a little icon next to the entries in the imagelist (I use VB a lot :) )
I don't know how hard/easy this may be, but is there any way to see what type these keywords are? Perhaps with a little icon next to the entries in the imagelist (I use VB a lot :) )
Hi Qweerdy
As you might have guessed I too use VB a lot, so RadASM is influenced by this. I too are missing an indication of what type the word is, so I guess an ownerdrawn listbox is on its way, but not very high up on my todo list.
KetilO
As you might have guessed I too use VB a lot, so RadASM is influenced by this. I too are missing an indication of what type the word is, so I guess an ownerdrawn listbox is on its way, but not very high up on my todo list.
KetilO