photools.com Community

IMatch Bug Reports and Feature Requests => Bug Reports => Solved Bug Reports (for next version) => Topic started by: Darius1968 on February 08, 2024, 05:23:10 PM

Title: Filter Panel Can't Be Disabled From Caption Bar
Post by: Darius1968 on February 08, 2024, 05:23:10 PM
So, I have said filter active via the filter panel.  The caption bar is blue and contains the button meant for disabling the filter panel.  However, it's non-functional.  So, I can only disable the filter from within the filter panel itself. 
Yes, I am using the latest version:  IMatch 2023.7.2. 
Title: Re: Filter Panel Can't Be Disabled From Caption Bar
Post by: Mario on February 08, 2024, 06:28:13 PM
Works here. I would need more details. Any detail may matter!

I enable the "Rating, Labels and Collections" filter in the Filter Panel. The File Window updates and the blue caption bar shows with the funnel icon.

I click the funnel icon. The Filter Panel is paused and the File Window updates to show all files again.
Title: Re: Filter Panel Can't Be Disabled From Caption Bar
Post by: Darius1968 on February 08, 2024, 07:11:52 PM
UPDATE: 
The button in the caption bar on my end will turn on/off the filter panel as long as the panel is always on display and not in the auto-hide mode.  But as soon as I engage auto-hide, that caption-bar-button not longer is in play. 

Additionally, the keyboard shortcut (Ctrl+F6) to pause/unpause the filter panel now only works if the filter panel is focused or not in the auto-hide mode.  I think this behavior is the first time for me to observe. 
Title: Re: Filter Panel Can't Be Disabled From Caption Bar
Post by: Mario on February 08, 2024, 08:27:01 PM
When a panel is in auto-hide, it might not even exist yet. The framework creates the Filter Panel it the first time it is expanded.Commands which require the filter panel to exist won't work in this situation.

Can this be the case?
Title: Re: Filter Panel Can't Be Disabled From Caption Bar
Post by: Mario on February 09, 2024, 09:04:38 AM
It was as I assumed. I have fixed this for the next release.