A bit of a dilemma here. SASM is a bit schizophrenic regarding the RADIX directive. It's not crystal clear from the documentation whether the RADIX directive only affects parsing of numbers, or the output in the list file as well. After working through the source code, it seems that during pass one, RADIX affects parsing and output. During pass two, RADIX is basically ignored. Hence, a pass one warning will be utilizing the current radix during formatting, while pass two just uses the last radix set in the code. The fact that your macro worked during pass one was more of a fluke than anything else.
The dilemma is that to modify SASM to parse and set the radix during pass two may have side effects I can't predict. I will experiment and see what I find.
Another curious thing is that if I comment out the places in the macros where I put the RADIX back to decimal, the display is fine, although then other things I want in decimal get displayed as HEX.
By the way the TOP file feature is very nice when the scroll wheel works for all files, which is 100% on Win98. I did try running the program under XP in Win98 compatibility mode and with display themes disabled, but the scroll wheel will still only work in the last file opened.
I didn't think to check if the programming progress window was still stuck on top with compatibility on. It seems to be that whatever difference there is in how XP handles the current window focus versus 98, it isn't influenced by the compatibility mode.
Is anyone else noticing this problem with XP, or is it something funny about my specific machine?
For the moment I'm avoiding doing any heavy editing on the XP machine. [noparse]:)[/noparse]
Comments
A bit of a dilemma here. SASM is a bit schizophrenic regarding the RADIX directive. It's not crystal clear from the documentation whether the RADIX directive only affects parsing of numbers, or the output in the list file as well. After working through the source code, it seems that during pass one, RADIX affects parsing and output. During pass two, RADIX is basically ignored. Hence, a pass one warning will be utilizing the current radix during formatting, while pass two just uses the last radix set in the code. The fact that your macro worked during pass one was more of a fluke than anything else.
The dilemma is that to modify SASM to parse and set the radix during pass two may have side effects I can't predict. I will experiment and see what I find.
Thanks, PeterM
Another curious thing is that if I comment out the places in the macros where I put the RADIX back to decimal, the display is fine, although then other things I want in decimal get displayed as HEX.
By the way the TOP file feature is very nice when the scroll wheel works for all files, which is 100% on Win98. I did try running the program under XP in Win98 compatibility mode and with display themes disabled, but the scroll wheel will still only work in the last file opened.
I didn't think to check if the programming progress window was still stuck on top with compatibility on. It seems to be that whatever difference there is in how XP handles the current window focus versus 98, it isn't influenced by the compatibility mode.
Is anyone else noticing this problem with XP, or is it something funny about my specific machine?
For the moment I'm avoiding doing any heavy editing on the XP machine. [noparse]:)[/noparse]
Thanks,
Mike C.