Example:
1. Make your preferred selections in the "Custom" view button.
2. Click either the "Most Important" or the "All" button.
3. Click Custom again. The user selections are gone. They are replaced with the previously pressed button settings.
This doesn't make sense, right? The Custom button is a user selection and should always stick as an independent setting.
AO 5.56, Windows 10 x64
Autorun Organizer: Custom view is not remembered
- Meddly
- Posts: 12
- Joined: Mon May 27, 2019 9:24 am
- Chemtable Software
- Developers Team
- Posts: 390
- Joined: Thu Aug 07, 2008 12:59 pm
Re: Autorun Organizer: Custom view is not remembered
Hello,
This behavior is exactly as it was intended to be. When you switch off to any item other than Custom, the latter's checked items are reset. But if you keep the Custom item active, the checked items will be restored even after Autorun Organizer reset.
This behavior is exactly as it was intended to be. When you switch off to any item other than Custom, the latter's checked items are reset. But if you keep the Custom item active, the checked items will be restored even after Autorun Organizer reset.
- Meddly
- Posts: 12
- Joined: Mon May 27, 2019 9:24 am
Re: Autorun Organizer: Custom view is not remembered
Ok, it's hardly a huge problem. However, I still fail to understand the logic.
Let's say the user only wants to see Registry and Drivers most of the time. The Custom mode does the job perfectly.
Now, the user wants to quickly check All. The All mode does the job.
Now, the problem emerges: We essentially now have two "All" buttons. There is no Custom mode any more. They are duplicate buttons, doing the exact same thing.
I guess you could say that the user can enable/disable entries in Custom mode, This has two issues:
a) it is more tedious than quickly switching modes (Most important/All/Custom)
b) it renders the other two buttons redundant, because if I have to manually enable everything in Custom mode, then what's the point of the All button?
In any case, not a major problem and your choices are fully respected.
Let's say the user only wants to see Registry and Drivers most of the time. The Custom mode does the job perfectly.
Now, the user wants to quickly check All. The All mode does the job.
Now, the problem emerges: We essentially now have two "All" buttons. There is no Custom mode any more. They are duplicate buttons, doing the exact same thing.
I guess you could say that the user can enable/disable entries in Custom mode, This has two issues:
a) it is more tedious than quickly switching modes (Most important/All/Custom)
b) it renders the other two buttons redundant, because if I have to manually enable everything in Custom mode, then what's the point of the All button?
In any case, not a major problem and your choices are fully respected.