| |
TheWarCriminal
Account closed
Registered: May 2011
Posts: 30 |
keep top 2 rows of screen from vertical scrolling
I lost my code from years ago that would keep the top 2 rows of the character screen (1024+80) from vertical scrolling with no flickering. I used it for the BBS I was creating back then. With recent devs in CBASE not performing how I would like it too I have started back recoding that BBS but I need 2 very important things. First off is a no vertical scroll on the top 2 rows. I know CBASE has one but it flickers and is compiled. Would like one in ML or someone point me in a starting direction. The 2nd one is a date ML routine. I know how to check the time and convert it into a readable format but the timer does not hold a date so it keeps resetting at 24hr. Since I am coding this BBS for WinVice is there a way to get the info from the emulated RTC?
I know this sounds like I have no clue what I am doing but when you have been away from c64 coding for 3 decades you loose the knowledge. Just getting reacquainted with BASIC V2 is a hazzle when you are so used to VB.NET behind code. One oh the things that constantly get me is the string setup: BASIC V2 is string$ where as VB.NET is $string. Which ever company decided to screw around with the context should have left it alone.
Any help would be appreciated in this. (I have searched the forums here, Google and Internet Archive c64 Books) |
|
... 28 posts hidden. Click here to view all posts....
|
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting GroepazDon't forget to patch the HOME location too Or just have prints all ordinary on 40x25, but with a split that would optionally display a hires bitmap in the top two rows (no $d800 issue). Or, well, border sprites! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
Oh yeah, border sprites with RS232 NMI going on \o/ |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1378 |
Quoting KrillQuoting GroepazDon't forget to patch the HOME location too Or just have prints all ordinary on 40x25, but with a split that would optionally display a hires bitmap in the top two rows (no $d800 issue).
Yes, I think Silver Dream already mentioned raster splits.
(much as you already mentioned stealing the kernal routine - though I was thinking more, disable ROM and patch the kernal routine, so scroll is still triggered by character printing as usual)
Nice idea using hires bitmap to avoid d800 issues though!
I'm still unclear as to whether he wants to do smooth scrolling or just the usual row resolution scrolling. |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting ChristopherJamthough I was thinking more, disable ROM and patch the kernal routine, so scroll is still triggered by character printing as usual Somebody mentioned memory being tight, so i guess hooking into the CHROUT vector and doing some interception and custom scroll etc. seems more feasible than hogging 8 KB for pretty much the same functionality. =) |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting GroepazOh yeah, border sprites with RS232 NMI going on \o/ Same problem as with a raster split, no? But can be turned off for transfers.
And i guess you wouldn't really use actual NMI but poll the flag from mainline thread instead (for maximum transfer speed)? |
| |
Silver Dream !
Registered: Nov 2005
Posts: 107 |
Quoting ChristopherJam(much as you already mentioned stealing the kernal routine - though I was thinking more, disable ROM and patch the kernal routine, so scroll is still triggered by character printing as usual) That was actually the very first suggestion I came with. The question is whether RAM under KERNAL is to be used for something else than a KERNAL copy. Hooking through IBSOUT as suggested by Krill is more complex but surely uses less than 8KiB needed for KERNAL patching.
Quote:Nice idea using hires bitmap to avoid d800 issues though!
Yes, although also rather pricey both in terms of memory and cpu usage.
Quote:I'm still unclear as to whether he wants to do smooth scrolling or just the usual row resolution scrolling. Good that it's not only me who has doubts on the actual OP's goal :-) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
Quote:
Same problem as with a raster split, no? But can be turned off for transfers.
And i guess you wouldn't really use actual NMI but poll the flag from mainline thread instead (for maximum transfer speed)?
He wants to have this statusline to watch when a user is connected to the BBS. That pretty much implies you are using NMIs and cant switch them off - unless you limit yourself to support a certain kind of rs232 interface (no userport bitbanging, for example). And no, the most efficient implementation has the NMI fill a ringbuffer, and the main thread consuming that. |
| |
Silver Dream !
Registered: Nov 2005
Posts: 107 |
Quoting GroepazOh yeah, border sprites with RS232 NMI going on \o/ Is that a problem or what? :-P |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting Silver Dream !Quoting GroepazOh yeah, border sprites with RS232 NMI going on \o/ Is that a problem or what? :-P Maybe just a different kind of flicker, maybe no problem at all (opening the vertical borders has a large margin of tolerance).
Additional DMA itself (caused by the sprites) on top of badline DMA shouldn't be a problem at all, should it? :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
Oh when Krill mentions borders i was thinking of sideborder, of course. Vertical is no problem, obviously :=) |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
