xanna (xanna) wrote in suggestions,

permit overwriting of inheritance in custom mood themes

permit overwriting of inheritance in custom mood themes

Short, concise description of the idea
Allow moods to remain undefined (i.e. have no image associated with them) even if they are a 'sub-mood' of a defined mood. e.g. have an image for 'happy' but not for 'refreshed'.

Full description of the idea
Currently the 'inheritance' feature of custom mood themes takes precendence over direct commands, so that a user cannot remove an image associated with a mood and leave it undefined. If s/he does this using the console or the webform, the mood will inherit an image from further up the hierarchy. I think moods should be allowed to be undefined if a user wishes.
At the moment only top-level moods (who have nothing to inherit) can be undefined.

Either take away the automation of the inheritance feature and let it be optional, or make sure that individual direct commands from a user take priority over the automated inheritance stuff.

An ordered list of benefits
  • User has more complete control over their customisation.
  • Moods will not become associated with inapproriate images if the user chooses.
  • Lose the inconsistency of some moods being allowed to be undefined and others not.

An ordered list of problems/issues involved
  • The inheritance idea is very useful, this shouldn't be allowed to break it.

An organized list, or a few short paragraphs detailing suggestions for implementation
  • Have inheritance happen not automatically, but on a button on the form / command on the console, to populate any blanks. But if the command isn't issued, let the blanks remain blank.
  • Or, make sure a direct command from a user on the console or webform is not overwritten by the automatic process.
Tags: mood themes, § rejected
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded