Re: VTUI Library
Posted: Wed Dec 20, 2023 7:06 am
I had not noticed that it actually saves to different addresses.
When looking at the VTUI library documentation https://github.com/jimmydansbo/vtuilib? ... -save_rect , my guess is that the vtui.save_rect prototype would be something like this:
vtui.save_rect(memtype, bank, address, width, height) where
memtype: $80 for video memory, $00 for system memory
bank: VERA bank if memtype=$80
address: Address in memory to write screen content to
width, height: size of area to save.
So it seems like store_logo first save the logo to address $10000 in VRAM, then it saves the logo to address $10100 in VRAM
store_where_logo_was saves the logo to $10010 and then to $10100 in VRAM.
As the area saved is 7x7 characters x2 for color information it uses 92 or $62 bytes of memory.
store_logo saves logo to address $10000 and store_where_logo_was saves logo to $10010 which would overwrite the logo saved by store_logo.
When looking at the VTUI library documentation https://github.com/jimmydansbo/vtuilib? ... -save_rect , my guess is that the vtui.save_rect prototype would be something like this:
vtui.save_rect(memtype, bank, address, width, height) where
memtype: $80 for video memory, $00 for system memory
bank: VERA bank if memtype=$80
address: Address in memory to write screen content to
width, height: size of area to save.
So it seems like store_logo first save the logo to address $10000 in VRAM, then it saves the logo to address $10100 in VRAM
store_where_logo_was saves the logo to $10010 and then to $10100 in VRAM.
As the area saved is 7x7 characters x2 for color information it uses 92 or $62 bytes of memory.
store_logo saves logo to address $10000 and store_where_logo_was saves logo to $10010 which would overwrite the logo saved by store_logo.