Small addition for usability.
Macro creates toolbar button for Flashblock on/off switching.

Just select 16 or 24 version (according to your taste and habits), download and unpack into KM folder.

Then restart.

Now you can easily switch Flash on/off and see whether it's switched on or not (the button image is changed according to preference value).



Edited 2 time(s). Last edit at 12/13/2012 01:41PM by rodocop.

cool. can it work with just about any version of K-meleon or just the latest versions of KM?

I think it should work with any version supporting flashblock out of the box.

Quote
rodocop
I think it should work with any version supporting flashblock out of the box.

You still didn't rename your skin folders. :O

If you add (Large) to large skin folder names,
you'll only need one macro that selects an icon.

Macro command index($SkinName, "Large") is -1 for
small skins and bigger than 0 for large skins.

Some people change skins every day.

May look irrelevant now, but I have 2 questions:

1) this extension works fine in all 1.x versions and in KM74, but it crashes (!) KM 75-76.
Previously I was faced such an effect only when wrong bitmap filenames are written in toolbars.cfg

But I have no glue how can the single kmm-file crash K-Meleon.

Maybe this question is primarily for JamesD who created the runcode (of button change) this extension is based on and who maintains the Macrolanguage docs so he knows all the changes between versions that might be the reason of crashes.

2) I totally missed the message by deadlock so I understand he spoke about the way to automate button size changing according to skin selected.
But I really cannot catch the macrocoding logic to get this done.

Moreover, now things have changed and this may be done, perhaps, using multisized ico-files instead bmp ones.

to 2)
he seems to suggest to check if the current skin name (from the pref) contains the word "Large", and depending from this if-condition choose the button name. But wouldn't work for all the large skins out there which do not use "Large" as part of folder name. And with the modernized skin handling I'm not familiar, how different sizes are created in out-of-box KM now, or if contained at all.

to 1)
no idea and not tested, just took a very short look over the macro, and wonder if it might cause any issues that the "default" folder name is now written "Default" in dorians zips, but still in traditional small caps in the macro zip...
Or if checking a BOOL pref with writing "false" in quotes might now be a prob? Technically this is a text string if quotes are added. KM does auto-conversion for numbers with/without quotes, no idea if also for true/false or if it depends from KM-version...
OR it might have to do with the completely rewritten new skinning system, possible using the newer commands instead of the traditional ones might help?

(PS the resources line contains a different button name as the real image, but of course only a comment so not bug-related.
Then again, perhaps this other name might have been better, it's unique and avoids possible conflicts with other flashblock-macros)

PS2:
the menu name for the button doesn't exist? At any rate don't see it created in the macro

PS3:
It's using "setbuttonimage", that means flat buttons, not visibly "pressed". Like the Proxy-Toggle macros. Do those still work?



Edited 2 time(s). Last edit at 02/08/2017 07:56AM by siria.

It's basically the same principle as any other macro which just toggles a simple pref and creates a button for it, like e.g. the standalone proxy buttons.

Thank you, siria!

Cannot say I understood all the said but I'll try to change things abd see what will happen ;-)

If you have a proxy button macro which still works (?), I'd perhaps first try to copy that one and modify it for a simply BOOL pref, and other names of course for everything.

FOUND IT!!!

The reason was the change in icon indexing inside graphics files.

I fix all by changing all the entries looking like

$FBlockButtonImageHot = "FBlockButton16.bmp[0]" ;

to

$FBlockButtonImageHot = "FBlockButton16.bmp[0,16,16]" ;

This solved the problem!

NB!!! Sure this works for 16x16 version.

24x24 version needs:

$FBlockButtonImageHot = "FBlockButton24.bmp[0,24,24]" ;

Edited 2 time(s). Last edit at 02/09/2017 01:16AM by rodocop.

Uaah.... does that mean that now ALL old button-macros are crashing?? <shock>

Quote
siria
Uaah.... does that mean that now ALL old button-macros are crashing?? <shock>

Only those using more than 1 icon per BMP-file (or other graphics types supported like PNG)

Not so much do exist really of such type.



Edited 2 time(s). Last edit at 02/09/2017 01:46AM by rodocop.

Well. Here go the updated extensions.

- Ready for KM 75 and newer;
- Fixed image names and descriptions in KMM;
- macro renamed to avoid naming collisions between 16 and 24 versions;
- localization template inside.



Edited 1 time(s). Last edit at 02/09/2017 01:43AM by rodocop.