Hyperion Entertainment Message Boards

Amigo1 wrote:.....What I was trying to say is, it should recognize same screen modes.
For example:

Let's assume you have a checkmark on the "Detect settings automatically" checkbox and the "All supported modes" radio button selected in "SYS:Prefs/ScreenMode preferences/Monitors". The "Available Screenmodes Tab then list the following modes:
800x600
1024x768
1280x1024
1920x1080
(all of them in their respective CLUT8, RGB16, ARGB32 variant)

let's further assume you have set WB to 1920x1080 ARGB32 and also set the same resolution for OWB's own screen.
Now uncheck the "Detect setting automatically" in the "Monitors-Tab" and make sure "1920x1080 ARGB32" is available and check marked.
Reboot your machine.
What happens here is, Workbench is still correctly displayed in 1920x1080 while OWB refuses to open it's own screen, and the settings in SYS:Prefs/Screens for each entry in de "Defined screens list" is emptied.

Reverting back to "Detect settings automatically" and fast-rebooting the OS, refills the screenmode settings for each entry in the list and OWB opens in it's own screenmode again.

So again, what I was trying to say was: I would welcome if Screen Prefs could detect similar(?)/same screenmodes. I hope this expressed my thoughts and enhancement proposal in a clearer manner.

P.S. And btw a similar behavior is shown when swapping two entries manually in the Tooltypes of the Monitor icon, or if simply adding an entry at the end of the tooltypes.

I am new to OS4.x, so not everything makes sense to me, but your quote above did catch my interest, because it mentions a problem I had with my X1000 the first day I used it. I am only repeating my problem here, so anyone else reading this thread will have additional info available to them, if they are working on any bug fixes.

I use a 20" Dell widescreen LCD and probably the first thing I wanted to do after turning on my X1000, was to reset the screen resolution using the Preferences "Screen Mode" program. The native resolution of my monitor is 1680x1050, but that resolution was not available in the list of resolutions, so I came here and asked for advice on how to get the 1680x1050 resolution that I wanted, and someone told me to go to the "Monitor" tab and put a check in the box labeled "Detect Settings Automatically".

When I did this and closed the Screen Mode Preferences program, I got a requestor that warned me that the available screen resolutions would be erased. I can't remember the exact wording of the requestor, but I think there were two warnings, and then a requestor that told me that I needed to reboot to make these changes to my system. When I rebooted, all of the Radeon screen modes had been erased, but new ones that matched the capabilities of my monitor were not written in place of the earlier resolution list. That means that I only had the "Boot VGA" resolution, and a short list of "Fake Picasso96" modes. None of the "Fake Picasson96" modes would work and I would constantly get kicked back to the "Boot VGA" screen mode (which looked terrible on my monitor). To make it more difficult, the "Monitor" tab in the Screen Mode Preferences program, was grayed out, so I could not go into that window and "Undo" what I had done to create this problem.

I came back here and on one or two other Amiga forum sites and asked what had happened and how to fix it. One user (or beta-tester) told me that I should not have used the "Detect Settings Automatically" check box, as it has problems with some monitors. I followed his and other people's advice and went to the monitor icon in the Devs/Monitors drawer and used the Information menu item to edit the tool types and delete the line that activates the "Detect Settings Automatically" option. I also added a resolution of 1680x1050@60 line, to the list of resolutions in the tool types. Then I rebooted again and found that the Radeon screen modes had been restored to the list in the Screen Modes Preferences program, so I could choose the 1680x1050 resolution that I wanted.

Like I wrote earlier in this message, I only repeat this info in this thread for the benefit of any OS4.x programmer who might be working on any bug fixes.

My resolution is the way I want it now and everything seems to be working very well. If I should submit this information as a "Official Bug Report", please let me know and I will research how and where to submit official bug reports, and then do so for the benefit of the programmers.

I am finding using the sliding screens buggy for me.

Here is what I am trying to do.

I am running OWBMUI on my X1000 and in the MUI Prefs of OWBMUI I have assigned the browser its own screen. It opens in its own screen fine and I can use it, slide it up and down, but once I slide it down all the way and launch another application, say NetSurf, the OWB is not longer there to slide up.

I take my pointer all the way to the bottom of the screen but she is not there to slide up. I then relaunch OWB and it starts a 2nd instance of it I guess on workbench screen so non of my normal settings are apparent.

Is this a bug?

How can I get the slide down OWB screen to be accessible again?

tj

EDIT: I figured it out. Use the icon upper right side of workbench window and once clicked I can now see the top of the OWB window I slide down.

amigasociety wrote: Is this a bug?

No, it isn't. Perfect and usual AmigaOS behaviour since the first 1.x releases AFAIK. It *is* in deed unusual for non-Amiga users, but you'll get used to it.

It might seem undetermined what happens to which screen in which state - but there is indeed a logic behind this... Your "problem" with not being able to access the little bit of screen from MUI OWB is that you haven't seen the screen switching from the (tiny rest focus of MUI OWB screen) to the screen of (for example) Netsurf/Workbench. In this case the MUI OWB screen is - of course - switched to the back and the little visible rest slide of the MUI OWB screen isn't visible anymore. The switching of the screen stack is (more or less) unrelated to the "sliding" state of each screen!

amigasociety wrote:I am finding using the sliding screens buggy for me.

I then relaunch OWB and it starts a 2nd instance of it I guess on workbench screen so non of my normal settings are apparent.

Is this a bug?

tj

No it is just the way MUI-OWB has been coded. Each time you run it, it starts a new programme, and for each one you need to define the MUI setiings, and each has its own Arexx prot

If the MUI tag that would force each start of MUI-OWB to be a single task - like IBrowse and YAM, then you would only need ever define one set of MUI settings for MUI-OWB. Each new window would run on the same screen.

I got round it by defining several levels for the OWB-MUI prefs but it is not an ideal way to do it.

amigasociety wrote:How can I get the slide down OWB screen to be accessible again?
...
EDIT: I figured it out. Use the icon upper right side of workbench window and once clicked I can now see the top of the OWB window I slide down.

There is an alternative solution: If you are using the DepthToFront commodity, then right-clicking on the screen's depth gadget (the thing you left-clicked on in the top-right of the screen) brings up a list of all the open screens, from which you can choose which one you want to come to the front.

Good to know Chris H, thanks!

tj

ChrisH wrote:

xenic wrote: I think another option should be added to the Screen mode block in the Screens Preferences Display tab. A "Like Workbench" option should be added for Screen modes.

Yeah, I've wanted something like that for a long time.

Wow, great idea
Enhancement created...

@amigasociety

amigasociety wrote:I am finding using the sliding screens buggy for me.

Here is what I am trying to do.

I am running OWBMUI on my X1000 and in the MUI Prefs of OWBMUI I have assigned the browser its own screen. It opens in its own screen fine and I can use it, slide it up and down, but once I slide it down all the way and launch another application, say NetSurf, the OWB is not longer there to slide up.

I take my pointer all the way to the bottom of the screen but she is not there to slide up. I then relaunch OWB and it starts a 2nd instance of it I guess on workbench screen so non of my normal settings are apparent.

Is this a bug?

How can I get the slide down OWB screen to be accessible again?

tj

EDIT: I figured it out. Use the icon upper right side of workbench window and once clicked I can now see the top of the OWB window I slide down.

More than a year later, but here another option to slide up the "lost" screen again:

1) Open GUI-Prefs and select "Control" from the left list.
2) You can look for the "Global Intuition controls" "Miscellaneous" section and
3) activate (marked checkbox) the "Front screen activation" checkbox
4) Press "User" or "Save"

Now, whenever you slide a Screen all the way down to the bottom and activate another screen, you just need to click the "Screen Depth" gadget and take the mouse pointer down, the screen should slide up, if it doesn't just click the "Screen Depth" gadget again..

And there's the lcommand m shortcut to traverse the list of every open screen. Of course, if there's no suitable key on the keyboard and no gadget (upper right corner), that's annoying.