I started using Scribble and like the toolbar behaviour. It is like the old toolbar class from Alfie: no border, highlights when you move the mouse over it (although you had to set this in MUI settings for his toolbar but it was possible a long time ago). I would like to configure YAM and Ambient the same. In YAM the icon does not highlight but I get a border. Without mouse on the graphic there is no bortder. How can I change this behaviour to the one from Scribble?
And the same for Ambient: Ambient lister buttons always have a border but this wastes space. And they do not light up when I move my mouse over them. How can I configure it the same way as Scribble automatically does? Or better could you update Ambient to act the same way with the next MorphOS release?

Quote:

Ambient und all other windows are individual displayable.

The great secret: Screenshot of ambient icon.jpg
In german, but you can find it without knowing the language.

Two steps to change the buttons:

1. Enter the mui settings window of the special prog (like Scribble)
2. Find the mui setting "Button" and then "Frame/Background"

Change the frame of the button, till its full transparent.
Change the space between the buttons. (in the same window)
Change the background of the button, if its wrong.

You see, it' ease!

So OWB does not use the standard settings from Ambient but it has to be configured new there. Or how can I do it for all programs at once? It is a pity that we have so many different toolbar classes which all behave differently. There should be one with all settings included. Then all programs would look the same -> more professional.

Quote:

There is no standard toolbar class in mui, so there is no way to configure them at once.

In fact there is no need to create a toolbar class, as it is basically a horizontal group class full of gadgets. The needs are so different in applications, that it makes no sense to actually create a specific class for all of them.

Ambient Windows need other features (horizontal, vertical, button, popup, animation, custom contents,...) for the buttons, than OWB and OWB others than Scribble. In the end, when creating some universal toolbar class, you end up with the same features the group class has, which already is available.

Developers using an external thirdparty mui class did not really understand the mui way of creating classes. Once they need features not available in such external classes, they have the choice of using group class the real way, force the developer of that third party class to implement a specific feature that probably only this application needs, or (if possible) subclass that specific external toolbar class to add the feature.

In any case using a thirdparty non standard mui class is always a bad choice as it will cause problems, when that class is missing, outdated or contains bugs like it for example happens with n#?.classes all the time.

In easy words: Use the group settings in mui to adapt application toolbars. If the application has specific features (like Ambients panels and screen bars, which are a kind of a tool bar, too), you have the application specific settings at their usual places.

If an application does not respond to group class changes, then the e.g. border for example is hard coded and cannot be changed.

Also you need to understand that OWB, Scribble *and* Ambient are normal applications. There are no settings in Ambient that effect any other application and vice versa.

It may be a little confusing that there are menu items "mui settings" and "system settings". Both are just launcher for the external settings or global mui and system preferences. E.g. you can open the system settings by using the shell "MOSSYS:Prefs/preferences". MUI settings open on "MOSSYS:Prefs/MUI" That is exactly what Ambient does when you select the menu items and nothing more.

"ambient" and "ambient mui" menu items are opening the settings and the mui prefs for the *application* Ambient and only effect ambient and its look. In OWB you have "OWB..." and "MUI..." items in settings menu, which are exactly the same. First opens the application settings and the mui one, does configure the look and feel. These two are available in most in mui applications.

If you ignore the MUI one, you can setup the look and feel of the entire OS by using the one from ambient menu or call "MOSSYS:Prefs/MUI". Changing anything here will change *all* applications at once. If you want to reset the mui look of an application, open the "ENVARC:mui/" drawer and simply delete the "applicationname.1.prefs" file.




[ Edited by geit 14.11.2014 - 10:55 ]