Excellent!... I look forward to making use of this myself,
Glad to know this sort of functionality has become integrated in the new OS release
I remember using KCommodity on Amiga OS 3.x in a limited fashion for this and some other screen promoting
Submitted by JosDuchIt on
Very interesting &readable
If you want to give users the option to open on a separate screen, let them define the screen parameters themselves using AmigaOS's Screens editor.
Maybe providing the launch of the Screens editor from your app?
In your program’s Settings, provide a string gadget for the public screen name.
I guess instead, once created , you might as well give the user the opportunity to select it directly from a list of defined public screens? (so as not having to copy the name)
Is this easy to implement ?
Submitted by trixie on
Maybe providing the launch of the Screens editor from your app?
Yes, the OS development will most likely go in this direction. As the Screens editor doc specifically says, "For the near future, it is envisioned that any application will be able to register its screen's name with the system, and also to invoke the Screens editor (through an API call) and present it to the user as the standard means to configure all aspects of its screen's user interface." (See SYS:Documentation/Prefs/Screens.doc). Before that happens I would stay away from custom kludges trying to invoke the editor.
you might as well give the user the opportunity to select it directly from a list of defined public screens?
I can imagine a string gadget followed by a chooser listing the available public screens (not the ones currently opened but those defined in the Screens editor). Once the OS provides a way to obtain such a list.
As you can see, certain aspects of screen handling are still somewhat uncooked. I'll happily update the article when things become set in stone.
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition
Author of WordNet for OS4
Submitted by cha05e90 on
Very nice read - thank you very much for this guide!
X1000|II/G4|440ep|2000/060|2000/040|1000
Submitted by BillEaves on
An interesting read.
I found the following intruiging.
3.2 Greater window mobility
Using a new feature in Window Class (introduced in AmigaOS 4.1 Update 3), ReAction-based programs can now “jump” between screens freely during their runtime.
How do you achieve this ?
In MUI you have icons in the window bar that can jump your application to a public screen, but I see no such icons in any apps using Reaction windows.
Or does the ability have to be hard coded by the developer of the application ?
I am interested in this because the new shell can do everything that KingCon could apart from being able to jump onto another screen.
Submitted by trixie on
@BillEaves
The developer decides whether his/her program will support screen jumping, by passing two specific tags at window creation time. Read Rigo's tutorial that relates to this new feature:
http://www.os4coding.net/blog/rigo/boopsi-windowclass-and-new-popup-menu-functionality-part-one
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition
Author of WordNet for OS4
Submitted by trixie on
A small update - added section 4.4 (Screen jumping caveats)
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition
Author of WordNet for OS4
Submitted by Massi on
Very clear reading, precious work as usual! Thanks
Comments
Submitted by Belxjander on
Submitted by JosDuchIt on
Submitted by trixie on
Submitted by cha05e90 on
Submitted by BillEaves on
Submitted by trixie on
Submitted by trixie on
Submitted by Massi on