Calling Macro After Cross Page Boundry

[MikeWinston]

You may be right longpole. But this is what it's pointing to at this time.
Sometimes i guess we wish for more problems so we have more information to troubleshoot.

Well DT_interrupts handles page crossing. I'm pretty sure. So I don't think this is good enough proof of being not the problem.

[Archangel]

Have you tried putting your vars all in bank 0 ?

[MikeWinston]

O.K. I'll try that tomorrow. (I don't have chip with me now)
thanks,
Mike

[MikeWinston]

Archangel,
No luck there. I just got a blank screen. I put all all my vars in Bank 0 like following example:
posX var byte BANK0 SYSTEM

I can get it to work if i manually do everything. But the macro would sure be nice.
Mike -

[MikeWinston]

Got it working.
Changed code in Macro. Removed the local label called OverVar. Not sure why it was there anyway. Also took the gosub LcdGotoXY out of for/next loop since it only needed to be executed once.
Also put in provision in case the variable number = 0.

here's updated macro:

'PrintVar Macro
'Example: @ PrintVar x,y, _variableName
'
asm
PrintVar macro x, y, variable
    MOVE?CB  x, _posX
    MOVE?CB  y, _posY
    MOVE?WW  variable, _varData
    L?CALL   _VariableOut
    endm
endasm
VariableOut:
    zeroFlag = 0
    gosub LcdGotoXY
    
    'cycle through all possible digts of word sized number
    for n = 4 to 0 step -1        		
        lcdData = (varData dig n) + 48
        if lcdData = 48 AND zeroFlag = 0 then SkipNum
        zeroFlag = 1
        gosub LcdSendChar
        posX = posX + 6
SkipNum:
		'if varData = 0 then print "0"
		if n = 0 AND zeroFlag = 0 then	
        	gosub LcdSendChar
        endif
    next
	return