XY Color Filters Broken at 22.30.0002

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
Post Reply
Zardoz2293
Posts: 619
Joined: 09 Nov 2011 20:20
Location: USA

XY Color Filters Broken at 22.30.0002

Post by Zardoz2293 »

Example: Color Filters set to "name:!~!" (white foreground, green background)

245.png


XY Builds v22.30.0001 and Prior:

243.png


XY Builds v22.30.0002 and Current (v22.30.0100):

244.png
To see the attached files, you need to log into the forum.
MacOS Tahoe v26.5.2
VM (Client): Windows 11 Pro (AArch64), 25H2.26200.8894 (10.0)
Windows Display: Main=MacBook 4112 x 2658 @200%; External 3840 x 2160 @125%

highend
Posts: 14993
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XY Color Filters Broken at 22.30.0002

Post by highend »

Please explain the pattern name:!~! in the context of < 22.30.0002
One of my scripts helped you out? Please donate via Paypal

admin
Site Admin
Posts: 66624
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XY Color Filters Broken at 22.30.0002

Post by admin »

Confirmed.

I recently worked on the consistency between the various filters and the search patterns. I took care not to break old code but in your case it happened. The pattern !~! is now interpreted as "NOT ~!". This can usually be handled by escaping the !-operator: \!~!. However, escaping doesn't work with Color Filters in the current version. :bug: It will work in the next beta.

Post Reply