- This topic has 4 replies, 2 voices, and was last updated 7 years, 11 months ago by
.
-
Posts
-
I have an issue here which may be discussed.
SkinSelector is linked with SkinManager and fully synchronized with this Manager, list of available skins is fully equal now.
SkinManager is a source of this list. So, if list of available skins in Manager is limited, then this list should be limited in the SkinSelector too.
I mean, maybe will be better to add the “SkinSource: (Internal, External, All)” property to the SkinManager.
SkinSelector will show list of skins which available in this SkinManager.
'Support' wrote:SkinSelector is linked with SkinManager and fully synchronized with this Manager, list of available skins is fully equal now.
SkinManager is a source of this list. So, if list of available skins in Manager is limited, then this list should be limited in the SkinSelector too.
Limiting the skins in SkinSelector to skins available in SkinManager is totally acceptable. I didn't expect anything else.
But SkinSelector for the user is the window fo the skins in SkinManager (which is further unknown to the user). By user I mean the end user of the program.
The choice from all available skins in SkinManager could be limited to a number of criteria: only dark skins, only free skins, only internal skins. I was suggesting the latter, but thinking about it, it is simply:
SkinSelector offers a choice of skins from SkinManager; this choice may be limited to certain skin criteria, internal skins being one of them.
- You must be logged in to reply to this topic.