[HeDiBo]

The sSkinManager.SkinName list does not show (internal) to distinguish between internal and external skins.

Happy New Year 💥

[Support]

Hello!

'HeDiBo' wrote:

The sSkinManager.SkinName list does not show (internal) to distinguish between internal and external skins.

Do you mean that internal skins are not represented in the SkinName popup list?

Quote:

Happy New Year 💥

Happy New Year!

[HeDiBo]

'Support' wrote:

Hello!

Do you mean that internal skins are not represented in the SkinName popup list?

No the addition (internal) is lost

[Support]

Is it possible to make a demo with such behavior?

[HeDiBo]

'Support' wrote:

Is it possible to make a demo with such behavior?

In this project both Bejing and BlueIce are internal skins:

[attachment=9099:acIntHidden.zip]

This is what I see when I pull down SkinNames on the skin manager:

[attachment=9100:Intern Missing.jpg]

Only Bejing shows “(intern)”. BlueIce (intern) is missing.

[Support]

Is this correct demo? TsSkinManager hasn't any internal skins there.

[HeDiBo]

'Support' wrote:

Is this correct demo? TsSkinManager hasn't any internal skins there.

It was the correct demo.

Only the SkinManager's info in the dfm file was not updated.

This is an old bug: changing the internal skins in a skin manager is not enough to make it update the dfm file. That's the reason why I did not have an internal skin for BlueIce: it was not saved as internal skin. Now, by re-opening the project both internal skins are present in the pull down list.

So, you'll have to look for another bug: altered property InternalSkins does not let the dfm file be saved!!

By the way, this bug is much more important: http://www.alphaskins.com/forum/index.php?showtopic=10215&st=0&p=53226&fromsearch=1&#entry53226

[Support]

'HeDiBo' wrote:

So, you'll have to look for another bug: altered property InternalSkins does not let the dfm file be saved!!

I have some troubles with repeating of this problem.

You are choosing a skin, clicking the “Exit” button, opening the dialog again and see that list of skins was not changed?

[HeDiBo]

'Support' wrote:

I have some troubles with repeating of this problem.

You are choosing a skin, clicking the “Exit” button, opening the dialog again and see that list of skins was not changed?

• After adding a skin and pressing Exit, the skin does not show in the SkinName list property.[*]Clicking the InternalSkins property does show the skin name as if it is added.[*]After termination of the IDE (and saving the changes as requested) and restart the Internal skins are listed in the SkinName list property.[*]After adding a skin and pressing Exit. followed immediately by closing the IDE the IDE asks to save the project (as it should) and upon restart the SkinName list property is OK.[*]After adding a skin and pressing Exit, I can manually enter in the SkinName list property the internal skin name (eg “Flatline (Internal)”), although it is not in the list.

So, only the case where a skin is added to the internal skins list, the skin cannot be selected from the SkinName list property, unless the IDE is closed and reopened.

[Support]

So, skins are saved in the Dfm-file, but not shown after adding immediately. Right?

[HeDiBo]

'Support' wrote:

So, skins are saved in the Dfm-file, but not shown after adding immediately. Right?

That would be my preliminary conclusion.

[HeDiBo]

Things got much worse in 14.14.

Internal skins are not listed at all in the SkinNames list.

[Support]

Maybe they are not saved in the Dfm file? Can you show an example project with the issue, please?

[HeDiBo]

'Support' wrote:

Maybe they are not saved in the Dfm file? Can you show an example project with the issue, please?

This is the same project again.

Notice that the SkinName is Calcium(intern). I typed that in, to get at the internal skin. I could not select it from the list.

Pull down the list of skinnames: none of the internal skins are listed.

[attachment=9130:acIntHidden.zip]

If you do not have any internal skins in the dfm, when the project was shipped, SkinManager contained 5 internal skins. You must be able to verify this by viewing the ACIH.dfm file outside of the IDE.

Then I got a brainwave and renamed one of the skins form BlueIce (intern) to “Blauw IJs”. Subsequently I refreshed the internal skins: and now they were listed in the SkinName list.

This does not mean the problem is solved, it only means it's a complicated problem to reproduce.

I did the same thing in another project: only renaming an internal skin brought back all internal skins in the SkinName list.

[Support]

Thank you for the demo.

I have sent the patched sSkinManager.pas by PM, try it please.

[HeDiBo]

'Support' wrote:

Thank you for the demo.

I have sent the patched sSkinManager.pas by PM, try it please.

Thank you. It seems to have done something. I see the internal skins in the SkinName drop down list.

However if I drop a brand new TsSkinManager on a form and click the SkinName drop down list, it is completely empty . If I add one internal skin, all other skins appear also .

If I close the project and reopen it again, the skin names reappear

So, only if I drop a fresh skin manager on a form, no skins are selectable. After that all's fine.

[Support]

New file was sent, the issue is solved there.

[Support]

'Support' wrote:

New file was sent, the issue is solved there.

Did you see this new sSkinManager.pas already?

[HeDiBo]

'Support' wrote:

Did you see this new sSkinManager.pas already?

Yes. The new sSkinManager 2.0 had the problem, that dropping it on a form, the SkinName list was empty.

Now that I restarted the IDE, that problem has gone away too.

All's solved

[Author]

Posts