Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

"Negate" Option for On-Demand Inactive After Initial Filter Operation #1495

Closed
wbedard opened this issue Mar 3, 2014 · 0 comments
Closed
Labels

Comments

@wbedard
Copy link

wbedard commented Mar 3, 2014

Hardware/Software Used:
Nexus7 (stock 4.4.2, XP r64)

Steps taken to reproduce:
With "Restrict On Demand" enabled (a first for me...), use the filter capability to clear out all existing FOD settings. Enabled FOD filter and applied...list updated with all apps with FOD enabled.

After disabling FOD in those apps, attempted to modify filter to add "Negate" option to FOD filter. The negate control was disabled (greyed-out) and non-responsive.

Proceeded to clear FOD filter and apply...app list updated as expected.

Went back to filter and enabled FOD. Once FOD is checked, Negate option is enabled ( not greyed-out) and is responsive. After applying the filter and returning to the filter dialogue, the Negate option for FOD is disabled, regardless of the state of the FOD filter control. Toggling the FOD filter control does re-enable the negate option, where it responds as expected.

@M66B M66B closed this as completed in 716d7cd Mar 3, 2014
@M66B M66B added the bug label Mar 3, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants