I don't understand what I am doing wrong. It looks correct to me. ::)
first, if you want to terminate a byte array with a 0 - lol - put 0 - i dunno how well the assembler likes the use of "NULL" in that case
it may be ok on newer assemblers, but on older ones, it wanted to fit equates that resolved to a 16-bit integer into a 16-bit place
as for the long list of errors.....
usually, when i see a long list like that, i go right to the first one and find the problem
remove all the commas that are at the end of lines - you should be in good shape :bg
It is just the commas that were causing the problems? :lol
That is just ridiculous. ::)
Thanks dedndave! Much appreciated!
Quote from: 2-Bit Chip on December 09, 2009, 04:10:44 AM
It is just the commas that were causing the problems? :lol
That is just ridiculous. ::)
Call it a feature. A comma means "more is coming that belongs to this line":
Quote invoke CreateWindowEx, 0, ; we create a listbox here
chr$("listbox"), 0,
WS_CHILD or WS_THICKFRAME or LBS_NOTIFY or LBS_USETABSTOPS or WS_VSCROLL,
0, 0, 0, 0,
hwnd, 170, hInstance, NULL
Noticing the errors on every third line, maybe the message should have been 'line too long'.
yes - that one was a bit cryptic - lol
i think the old assemblers would have said something like "value expected"