- This topic has 9 replies, 2 voices, and was last updated 7 years, 1 month ago by
.
-
Posts
-
Internal skins are mostly what applications will use. In localization a programmer may change the internal name to something that makes sense in the local language. For instance “Zest” doesn't mean anything in Dutch. But in choosing the skin the user of the app must know what the skin “Zest” stands for, the programmer may change that name to the Dutch equivalent (“Citroen” or “Oranjeschil”).
Also, the addition of “(internal)” will make no sense to a user who can choose nothing else but internal skins.
By changing the internal name, the programmer looses the possibility to use “Update All Skins” in the InternalSkins dialog.
I suggest to store the original skin name inside of the skin, and to scan the external skins for this name.
It's not a good idea to use the filename to represent an internal skin name. The internal skin name may even contain characters that are not allowed in a file name.
'Support' wrote:Described feature will be implemented in the v12.06
Maybe I explained it wrongly.
My application is delivered with Internal Skins only.
Many of the internal skins are renamed to Dutch equivalents.
If I click “Update All” in the list if Internal Skins, none of the skins with a translated name are updated. I get the message: “These skins are not updated: ” followed by a list of renamed skin names.
My idea was that “Update All” would go for an update, using the original name, not the translated name. This would require that the Skin manager would maintain a list of original skin names against which the update would be done.
In that way, skin manager could also have a method for setting a skin using the original skin name (OrgSkinName := 'Notes Leather' would do the same as SkinName := 'Leder'). That would make the application easily localizable.
Internal skins should be updated after clicking the “Update all” button, even if renamed.
This feature doesn't work? Maybe you should remove all skins from list and add it again (old names will be stored in this case).
'Support' wrote:Internal skins should be updated after clicking the “Update all” button, even if renamed.
This feature doesn't work? Maybe you should remove all skins from list and add it again (old names will be stored in this case).
Strangest thing is: it works if you do it in the same Delphi session. However, if you terminate Delphi and restart it, the same problem occurs.
I have deleted and re-added these skins already several times. Always with the same result. I also downloaded one of the offending skins from the skin gallery: but it's the same skin, so that's not the problem either.
When I rebuild the latest AlphaSkins components, I always delete all old DCU's, DCP's and BPL's before regenerating. So, it can't be old stuff hanging around.
Another problem with SkinManager is this:
My SkinManager is placed on a DataModule. When I change the list of internal skins, and I close the project, Delphi does not see the change in SkinManager.InternalSkins. Therefore the change gets lost.
I think this is a simple oversight, easily corrected.
With respect of being unable to “Update All” internal skins, I tested that when I was sure, the DataModule was saved.
- You must be logged in to reply to this topic.