Great, looks like you're getting the hang of it
But if
some priv-buttons are not red/green, that is intentionally, because those buttons have no allow/block setting! Like the UserAgent, the "Clear" buttons and the "Kill" buttons. A little misunderstanding?
For a
Reload-All-Tabs button (in current window), use command "
macros(_Reload_ReloadAll)", and I think you can create the rest yourself by now :cool:
(PS: just noticed
this macro was renamed from earlier KM-versions! Usually most commands can be found in file "commands.html", but that still lists the old version in 75.1RC. In such cases either do an explorer search inside the "macros" folder, searching for the menu entry, or search inside the default "menus.cfg")
=====
For a
Stop-Loading-All-Tabs button (in current window), am not sure if that exists already. Sorry am not quite up-to-date yet with all new functions... But perhaps the Offline-Function will do? Then again, it might pop up some "broken connection" warning?
Anyway, if you'd like to test, click
menu File>Work Offline, or create a button using "navOffline" or "ID_OFFLINE". Note that these are NO "macros()"
If it doesn't help, you need a little macro.
Here are 2 suggestions: The first uses the normal "Stop" button function, the second is probably a bit tougher, it also stops animated gifs, meta-refresh etc.
Use in
toolbars.cfg: "macros(StopAllTabs_stopNav)" or "macros(StopAllTabs_stopWin)"
(The button-creation can also be done by the macro itself, but you have more creative freedom doing it yourself in toolbars.cfg :cool
Copy this text into notepad and save it as "StopAllTabs.kmm" (without txt-ending) into your macros folder:
StopAllTabs_stopNav{
$_x=$TabNumber; while($_x>0) {
id(ID_NAV_STOP);
$_x=$_x-1; id(ID_TAB_NEXT);
}}
StopAllTabs_stopWin{
injectJS("window.stop()","alltabs");
}