Quote
msea
I feel a little bit like a grease monkey talking with rocket scientists. but I'm fairly clever monkey. :drool:
LOL! Funny put for "boah is that complicated!!"
Button config may need a bit training of course, which is the price for being extremely customizable, but actually that wasn't the prob here - just that some of this talk wasn't actually directed at yourself!
Instead just us more experienced users here discussing solutions among ourselves, which of course sounds extra confusing for others. OUR prob is that meanwhile there exist various different methods to create KM-buttons, older and newer ones. The newer ones being fundamentally different from the older ones, and additionally some of us here are stuck on old OS systems, using personally only old skins too. While those on modern systems have long since customized their toolbars to their liking too, years ago when only the old system existed, and still continue to use that one as well. So now when needing to give tips to new users using the new skins, a slight confusion breaks out :cool:
Quote
msea
On that score, um... I realized that because I am using two monitors at same time, the task bar on my laptop monitor has the K-Melon button/tile whatever it's called - and right clicking on that allows me to resize the browser (sans title bar). I didn't see it initially because it comes and goes, depending on what screen I click on!
Yeah that's what I've been asking in my previous reply too, if that tab in the taskbar couldn't be used. Okay, so this works for you while using 2 monitors, great! But not when using just one, not so great. While you're here, please hang around a bit longer and prepare that too, even if toggled off while still using 2 monitors.
What James' reply meant, translated:
no need anymore to add any additional "bmp" images or lines, because KM already has those min-max-window icons predefined! The only prob is, only the icons are predefined, but the toolbar itself not yet. Oh well.
============================= Try this:
menu Edit > Configuration > Toolbars
This opens the active toolbars.cfg, a simply text file.
(Before changing this default file, better make a backup copy of it. Also see more tips further down)
Inside this file create a NEW TOOLBAR by adding this text:
Window Size{
WinMin{
windowMinimize|&View
Minimize Window (right-click for menu)
}
WinMax{
windowToggle|&View
Toggle Window Max (right-click for menu)
}
WinClose{
windowClose|&View
Close Window (right-click for menu)
}
}
=============================
If you add this on top or bottom or the middle doesn't matter, as long as you don't accidentally insert it INSIDE another toolbar.
TIPS:
1) In KM each button can also show a MENU at right-click. Which one is freely choosable. Find this kinda handy and in the example above have added the "&View" menu, but you can use any other too or none at all. The "&" must be added before any underlined character you see in the menu names.
2) The NAME of the toolbar and the single buttons is free text, change it if you like. Same for the tooltip-line.
3) The only thing that matters is the exact COMMAND name (windowMinimize etc.) and the syntax { { } } You can also just compare how the other buttons and toolbars are build to get more ideas for own ones or customizations.
4) The COMMAND names can be found in various places, e.g. in menus.cfg or in macros or in commands.html or the wiki... or asking here.
5) Users can easily create their
OWN personal skin folder. Highly recommend!
Next to "default, Klassic and shared" folders in KM/skins/. Name it e.g. "myskin" or whatever.
Put a copy of the default toolbars.cfg and skin.cfg inside it.
Images optional, not necessary. Those lying inside this folder will be used, while KM will find missing ones in "default" and "shared" folder.
Restart the browser and choose this "new skin" in F2>GUI. Restart AGAIN.
This own skin folder with own toolbars.cfg in it etc. prevents to accidentally break the DEFAULT skin config.
And also prevents to accidentally lose your customizations some day when updating KM to a newer version, when choosing the "overwrite" method!
6) Permission probs: modern Windows versions are extremely restrictive with writing rights in the program folder. In that case move your skin folder into the current profile folder (Edit>Configuration>ProfileDirectory). Probably need to first create the parent "skin" folder there too, but haven't tested.
OK...? :cool: