Hello!
My Workbench application makes use of 2 "bitmap.image" objects with the BITMAP_Screen attribute initially set to the Workbench screen pointer.
What happens to them when jumping to a new public screen?
If I understand well it is not possible to change that BITMAP_Screen attribute via SetAttrs(), or? Perhaps this is handled internally by the "window.class" object?
Thanks, regards
Don't know about the internals - all I can tell you that I use both bitmap.image objects and the screen jumping feature in WordNet, and everything works just fine. Despite the bitmaps being created against a particular BITMAP_Screen pointer, upon arriving on the new screen the image colours are just fine.
AmigaOne X5000-020 / 2GB RAM / Sapphire Pulse Radeon RX 560 / AmigaOS 4.1 Final Edition Update 2
Did you try this with a CLUT screen (<= 256 colors)?
@thomas
No, I don't think I did. AFAIK the Window Class jump-to-screen feature documentation says nothing about the need to remap colours so I've never actually bothered.
AmigaOne X5000-020 / 2GB RAM / Sapphire Pulse Radeon RX 560 / AmigaOS 4.1 Final Edition Update 2
I came across the same question using serveral "getcolor.gadgets" objects which also do have an Screen attribute.
What I've done is to put them all in one layout group and after the WM_CLOSE (or WM_ICONIFY) I remove (and dispose) the whole layout and than build and add it again with the new screen pointer before the WM_OPEN.
Hey guys,
Maybe you're already past this point, but Rigo did an
article on the pop-up window menu and the jump to screen
functionality:
http://www.os4coding.net/blog/rigo/boopsi-windowclass-and-new-popup-menu-functionality-part-one
Maybe there's something in there that might help?
Thanks,
PJS