Difference between revisions of "Talk:Z80 Routines:Graphic:Fastcopy"
From WikiTI
| Line 6: | Line 6: | ||
:I added a Safe Copy routine, since there isn't really a reliable timing to suggest.--[[User:Jim e|Jim e]] 11:00, 26 Apr 2005 (PDT) | :I added a Safe Copy routine, since there isn't really a reliable timing to suggest.--[[User:Jim e|Jim e]] 11:00, 26 Apr 2005 (PDT) | ||
::Is is still faster than the _grbufcpy BCALL ? [[User:Guillaumeh|Guillaumeh]] 12:35, 26 Apr 2005 (PDT) | ::Is is still faster than the _grbufcpy BCALL ? [[User:Guillaumeh|Guillaumeh]] 12:35, 26 Apr 2005 (PDT) | ||
| − | :::Of course, it should only take slightly longer, but will always work.--[[User:Jim e|Jim e]] 14:51, 26 Apr 2005 (PDT) | + | :::Of course, it should only take slightly longer than fastcopy, but will always work.--[[User:Jim e|Jim e]] 14:51, 26 Apr 2005 (PDT) |
Revision as of 13:52, 26 April 2005
The di is not that dispensible. The display may be messed up if an interrupt that displays to the screen occurs during the fastcopy routine. It's not the end of the world if this happens, but it's worth the extra byte to prevent it. --Dan Englender 07:11, 25 Apr 2005 (PDT)
Warnings?
Also, what would we say about the new issues with the bad LCD drivers? Can we provide a fast routine that will support the bad drivers? --JasonM 16:38, 25 Apr 2005 (PDT)
- I added a Safe Copy routine, since there isn't really a reliable timing to suggest.--Jim e 11:00, 26 Apr 2005 (PDT)
- Is is still faster than the _grbufcpy BCALL ? Guillaumeh 12:35, 26 Apr 2005 (PDT)
- Of course, it should only take slightly longer than fastcopy, but will always work.--Jim e 14:51, 26 Apr 2005 (PDT)
- Is is still faster than the _grbufcpy BCALL ? Guillaumeh 12:35, 26 Apr 2005 (PDT)
