aurumdigitus wrote:BTW - What is your wish ADMIN is cerebrating on?
It's for a
GetList function which you could use to retrieve the Power Filters list. Then you could use that with Load/PopupMenu to customize the menu with your own additions.
Don put it on the backburner though so there's no ETA.
aurumdigitus wrote:TheQwerty wrote:Maybe you've already considered it but you could make an imitation Visual Filter button...or make a Power Filter button of it's own
Do not comprehend. Explanation please.
Sorry I didn't explain that better.
You could create a CTB that imitates the Visual Filter button through use of the Button command. For example:
Open the
snippet importer (go to "::Snippet;" in the address bar).
Paste the following and hit okay:
Code: Select all
Snip: CTB 1
XYplorer 11.90.0208, 1/17/2013 9:20:18 AM
Action
NewUserButton
Name
Filter
Icon
:visualfilter
ScriptL
Button('visualfilter', 1);
ScriptR
"Power Filters" Button('visualfilter', 8);
"Edit Power Filters" #652;
"Options" Button('visualfilter', 2);
FireClick
1
That creates an imitation Visual Filter button. It's an imitation because the Right Click requires an additional click to access the other menus. EDIT: But otherwise it offers all the same actions the builtin Visual Filter does.
I know there's been discussion on auto-executing CTB's right-click scripts, but sadly I haven't paid close enough attention to know if something came of those, nor have I played with improving this with "<get trigger>".
The other option would be to just create a CTB that displays a menu of filters you want to apply and pretend like the Power Filters list and menu don't actually exist in XY - so you'd manage them however you'd like in your script. After all "Power Filters" is just a fancy name for "Visual Filters which work on Properties."
Since my wish doesn't sound like it will be granted soon if you wanted to incorporate the Power Filters list or Most Recently Used filters into this CTB you'd have to read them in from the config file, which is why I say it's easier to pretend they don't exist and manage it all within a script.
Hope that helps!
