Update All Internal skins fails

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #56464
    Support
    Keymaster

      Interesting idea, I will think.

      #56512
      Support
      Keymaster

        Described feature will be implemented in the v12.06

        #56517
        HeDiBo
        Participant
          'Support' wrote:

          Described feature will be implemented in the v12.06

          Really great a3.gif

          #56825
          HeDiBo
          Participant
            '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.

            #56829
            Support
            Keymaster

              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).

              #56833
              HeDiBo
              Participant
                '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.

                #56836
                HeDiBo
                Participant

                  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.

                  #56840
                  Support
                  Keymaster

                    You are right, I see a problem now. I will fix it on the next week.

                    #57135
                    HeDiBo
                    Participant
                      'Support' wrote:

                      You are right, I see a problem now. I will fix it on the next week.

                      Replacing skins with local names still does not work. I thought.

                      But when I removed the translated ones, added them again and translated them again, then it worked. a3.gif

                    Viewing 9 posts - 1 through 9 (of 9 total)
                    • You must be logged in to reply to this topic.