Cannot open OWB on its own screen?

[clusteruk]

So while doing this new AROS video I am going through the ICaros 2.3 setup and I am having trouble setting up a new screen for IBrowse.

I set up a new screen in MUI / Zune settings and select and save but it stays on the default Dopu5 public screen.

I am sure this used to work fine and other apps can open a new screen but not via Zune.

Any ideas where I am going wrong please.
 

[ntromans]

You can do this by creating a new screen in PSI (I've called it OWBScreen) and then use the following IconX scrip:

stack 8000000
sys:prefs/PSI OWBScreen OPEN >NIL:
cd sys:utilities/owb
owb
SYS:prefs/PSI OWBScreen CLOSE >NIL:

The only problem with this is PSI still does not support setting the font, you so have to live with a slightly ugly one (Topaz I'm guessing) for window title and menus.

Cheers,
Nigel.

[AMIGASYSTEM]

clusteruk have you tried setting on Zune prefs "Remember On Exit"? (see screenshot) you can also use (force) single saves per single application where you need to keep a certain resolution, for example very ultile for "AmiTube"

[Amiwell]

hi steve

On Icaros 2.3 HTML5 Player is disabled downloaded these archives

http://archives.aros-exec.org/share/network/browser/owb-1.25.i386-aros.zip

http://archives.aros-exec.org/share/network/browser/odyssey-1.25-11.i386-aros.zip

new certificates

https://www.adrive.com/public/SxZEhQ/certificates.tar

[clusteruk]

No, it is screens I am having trouble with not remembering window position :-)

clusteruk have you tried setting on Zune prefs "Remember On Exit"? (see screenshot) you can also use (force) single saves per single application where you need to keep a certain resolution, for example very ultile for "AmiTube"

[clusteruk]

I am sure this used to work by changing the MUI settings, create a new screen and select it in OWB and save, or was that MorphOS?

Steve

You can do this by creating a new screen in PSI (I've called it OWBScreen) and then use the following IconX scrip:

stack 8000000
sys:prefs/PSI OWBScreen OPEN >NIL:
cd sys:utilities/owb
owb
SYS:prefs/PSI OWBScreen CLOSE >NIL:

The only problem with this is PSI still does not support setting the font, you so have to live with a slightly ugly one (Topaz I'm guessing) for window title and menus.

Cheers,
Nigel.

[magorium]

I am sure this used to work by changing the MUI settings, create a new screen and select it in OWB and save, or was that MorphOS?

To my knowledge that was never supported by AROS. So I do believe that you are mixing things there a little.

ntromans solution is what I (still) use to this day.

Nice to see you around again BTW.

[AMIGASYSTEM]

I am sure this used to work by changing the MUI settings, create a new screen and select it in OWB and save, or was that MorphOS?

This also happens with MUI on OS3, however if I'm honest I didn't really understand what you would like to achieve, maybe if you make a video it would give a better understanding of your problem.

[magorium]

... however if I'm honest I didn't really understand what you would like to achieve, maybe if you make a video it would give a better understanding of your problem.

There really is not much to see in a video. Another problem is that clusteruk is trying to accomplish something that does not work for him (so he is unable to make a video out of it).

His aim is pretty simple: have OWB configured in such a way that all windows that OWB opens are displayed/opened on another (second) screen (thus not on wanderer/magellan/scalos).

Amiga/AROS has a proficiency for that named PUBSCREEN. If an application supports opening its windows on a pubscreen (either by using a tooltype or by providing a commandline argument) then this wil happen automatically, provided that you have a public screen setup correctly.

Windows and Linux call it "desktops" which you can switch on the fly (Amiga uses the screen cycle gadget for that or a special crafted alt-tab utility).

You can setup public screens with the PSI preferences utility.

Running an application that way has two advantages:
1 - to prevent cluttering the WB (replacement) screen
2 - to be able to use a full set of custom palette pens that do not match the WB (replacement) ones


An I forgot to mention a third advantage: being able to run an application in another screen resolution.

[AMIGASYSTEM]

 magorium I understand, a kind of "ModePro" that I use on my AfA One, "see attached video"

https://youtu.be/mqi_blFM-rc

What I don't understand is that Wanderer would not need this, since OWB can be opened in a window at any size

[magorium]

magorium I understand, a kind of "ModePro" that I use on my AfA One, "see attached video"

Yes.


But do note that modepro offers some additional features.

What I don't understand is that Wanderer would not need this, since OWB can be opened in a window at any size

Don't confuse the words /window/ and /screen/ as doing so makes it very difficult to understand what the other person is talking about 

A windows is something completely different then a screen.

I think i understand what you meant to say in that you can open Wanderer on any given screen resolution but that:
- Stil means all windows of all applications that you start are opened on the same screen (cluttering)
- You would have to change the screen resolution manually, each time you start up that one specific application that you wish to run in another resolution
- All other applications that you start would be using the same screen resolution
- You are still bound by the pen-colors as 'dictated' by the workbench.

The last one is especially cumbersome if for instance you would run a test editor that uses highlighting based on pen numbers. as each application is able to use its own set of pens.

If you once learned how to use Amiga-key+M/N then you never wish to go back 

[clusteruk]

What I want is OWB to be able to use a ZUNE defined public screen as in the way Amiga OS always has done with RTG rather than it covering the whole of the DOpus display.

It seems I can do this with OS3x with RTG, MorphOS but not AROS. I remember being able to do this though but it is not a big problem just a bit of a shame to have to mess with scripting when the code is in OWB to do this, it just ignores it for some reason.

Steve

I am sure this used to work by changing the MUI settings, create a new screen and select it in OWB and save, or was that MorphOS?

This also happens with MUI on OS3, however if I'm honest I didn't really understand what you would like to achieve, maybe if you make a video it would give a better understanding of your problem.

[jPV]

It seems I can do this with OS3x with RTG, MorphOS but not AROS.

Although RTG has nothing to do with it, MUI programs have always been able to use separate screens, even with AGA setups etc. With MUI 3.8 and earlier you had the separate PSI tool to create/open/edit the screens MUI programs were able to use. Later MUI versions have the PSI functionality built-in in the main MUI preferences (and also in the application specific prefs), so it's a bit easier/direct from MUI 3.9 (IIRC) onwards.

I think AROS/Zune still uses the old PSI approach, but if it's somehow unfinished and you can't move programs to separate screens through their prefs without hacking around... I don't know... quickly tried on some old hosted Icaros OWB didn't seem to go to the newly created screen as it should... but this is just a very quick test without an up-to-date setup. In any case I was able to config and open a new screen, so it's a bit weird that the last step (of making a program to use it) didn't work. It's quite a shame if it doesn't work at all, because screens are quite fundamental part of Amiga usage.

[clusteruk]

Excuse the volume but here is what I mean

https://www.youtube.com/watch?v=KWP4dFR4pW8

It may be that I mis remembered and it has never done it, but other apps support this feature and it is great having the browser on its own screen :-)

[magorium]

As stated by jPV.


AROS uses MUI 3.8 and thus never had this feature.


It is possible you remember otherwise because when you run AROS on 68k you can run any version of MUI (or other updated libraries for that matter) and thus have an "updated" AROS system (that is then incompatible with basic AROS).