File requesters open on WB not on custom screen

I don't know really when it started. might be with OS4.1 update 6

I use muiOWB on its own screen. When trying to load a local page or save a page to harddisk, the file requester opens on WB

It is getting on my nerve. Anybody experiencing the same? Can i correct this behaviour?

It did work beforee, didn't it?

Have you tried to change the "Position" in ASL Prefs?

@JosDuchit
The requester always opened on the WorkBench screen (when running MUIOWB on another screen) for me. It is a bit of a nuisance.

@xenic
Same for me, MUI-OWB has always done it.

It is strange, because it should't : Thore added support of all of this year ago in mui. Dunno if it in 3.9, or only in 4.0. I even do not remember all the stuff about, all what i remember is that we worry about it and it was fixed.

ps. tested right now muiowb on latest mui4-beta: i open it on my own screen, then do "open file" => asl requester open on that new screen, not on WB one. Same for "save as html" or "save as pdf". If it didn't works on mui3.9, then seems it was added to mui4 only. I will ask Thore if he can bring it to 3.9 as well in meanwhile.

The next update will open all ASL requesters on the application's screen.

@tboeckel

Nice, thank you

@Xenic

Strange.

I always found that MUI-OWB on my XE opened requesters on the WB screen which is a bit of a pain.

Yet on my X1000 the requesters always open on the MUI-OWB custom screen.

I never figured out why the behaviour differed.

@kas1e


The version of MUI should not come into it. Though using MUI4 beta on the X1000 may explain the difference of behaviour I get between the two machines.

But to ensure file requesters appear on a custom screen all you need do is:

SetProcWindow((struct Window *)xget(MUI_BackWindow,MUIA_Window_Window));

Where MUI_BackWindow is the MUI ID of your main OWB window. Then the requesters will open on whatever screen the window is on.

@BiLLe

Quote:

Because it is different code in different versions of mui.

Quote:

It is :) Our 3.9 and 4.0 versions are different by code and by features by many reassons.

Quote:

Of course it explain. It should be like this.

Quote:

All the necessary code in browser already done by Fab years ago and it is already in the binary of os4 version which all of users have. Its just our mui on those times didn't support some stuff in MUI_AllocAslRequest(). After some tests Thore implement it, but it was only in mui4, and yesterday he backport that part of code to mui3.9, which will avail in some of next updates.

I.e. all the necessary code already in binary which users have, is was just mui3.9 which wasn't support some stuff in MUI_AllocAslRequest, and once users will have new version of mui3.9, its all will works rigth after update.