You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which plugin are you requesting the feature for?
Hide in Queue
Is your feature request related to a problem? Please describe.
Many times, for most of my children Rems I would want to hide in the queue the parent's name, ir order to avoid hints that make to easy recalling what is asked. But for one or two of the children Rem it is vital that the parent's name is shown.
For example, the parent may be a concept, and I may have one or two descriptors (for which hiding the concept in the queue would make no sense), but also many other contents that are arrange under that concept in the material I am following, for which hiding the parent's name would be desirable.
Describe the solution you'd like
The plugin has been improved lately. The "No Hierarchy" was a very welcome addition, as many times only for certain Rems we would like to hide the parents' names.
But in certain cases, as explained above, the contrary happens, and only for certain Rems you would like to show the hierarchy.
So, I propose adding a "Show Hierarchy" function, that would overlap any "Hide in Queue" or "Remove from Queue" eventually existing in the parents of a Rem, forcing them to be shown in the queue for the present Rem.
As an example, the image below shows the structure of the International Code of Signals, which gives a lot of two-letter signals, each one with a specific meaning. For the cards asking the meaning of the two-letter groups (there will be a lot of these cards), I don't want the section names to be shown; but for the cards asking the range of the signals for each specific subject (e.g. from AU to CA the codes relate to distress in aircrafts or helicopters), the name of the subject obviously must be shown. If I could tag this "Range" descriptor card with "Show Hierarchy", overlapping the "Hide in Queue" of its parents, my problem would be solved in the best way.
The text was updated successfully, but these errors were encountered:
Which plugin are you requesting the feature for?
Hide in Queue
Is your feature request related to a problem? Please describe.
Many times, for most of my children Rems I would want to hide in the queue the parent's name, ir order to avoid hints that make to easy recalling what is asked. But for one or two of the children Rem it is vital that the parent's name is shown.
For example, the parent may be a concept, and I may have one or two descriptors (for which hiding the concept in the queue would make no sense), but also many other contents that are arrange under that concept in the material I am following, for which hiding the parent's name would be desirable.
Describe the solution you'd like
The plugin has been improved lately. The "No Hierarchy" was a very welcome addition, as many times only for certain Rems we would like to hide the parents' names.
But in certain cases, as explained above, the contrary happens, and only for certain Rems you would like to show the hierarchy.
So, I propose adding a "Show Hierarchy" function, that would overlap any "Hide in Queue" or "Remove from Queue" eventually existing in the parents of a Rem, forcing them to be shown in the queue for the present Rem.
As an example, the image below shows the structure of the International Code of Signals, which gives a lot of two-letter signals, each one with a specific meaning. For the cards asking the meaning of the two-letter groups (there will be a lot of these cards), I don't want the section names to be shown; but for the cards asking the range of the signals for each specific subject (e.g. from AU to CA the codes relate to distress in aircrafts or helicopters), the name of the subject obviously must be shown. If I could tag this "Range" descriptor card with "Show Hierarchy", overlapping the "Hide in Queue" of its parents, my problem would be solved in the best way.
The text was updated successfully, but these errors were encountered: