TsWebLabel and mouseover

Viewing 20 posts - 1 through 20 (of 24 total)
  • Author
    Posts
  • #33348
    eledh
    Participant

    Hello,
    In latest AC 6.46 there is problem with TsWebLabel. It does not change font atributes when mouseover.
    I use the same parameters in Font and HoverFont property, but HoverFont with underline style.
    In AC 6.46 it is not working, text in this label is still normal. HoverFont is not applied, or maybe “mouseover” event is ignored.

    BR.

    #40826
    Support
    Keymaster

    Hello
    Where this label is placed? If you have a working example – give it please.
    Thanks.

    #40827
    eledh
    Participant

    Hi,
    this TsWebLabel is placed on TImage and TImage is on TsPanel on the form.
    I can send example today later.

    #40828
    Support
    Keymaster

    Thank you!
    Problem will be solved in the nearest release I think.

    #40885
    eledh
    Participant

    Hi,
    I am sorry for delay.
    I found that problem is with some skins only, for example with Topaz and Cold.
    Here is sample app, TImage placed on form, and TsWebLabel over image.
    BR.
    [attachment=3544:TsWebLab…6problem.zip]

    #40886
    eledh
    Participant

    I would like also mention anything else. When form is showed up, text in title (caption) is normal text (not bold), but when the form lost focus, text is changed to bold. I suppose that it should be bold all time. I noticed this issue in Win7 and Vista, in XP it seems OK.
    Thanks,
    BR

    #40861
    Support
    Keymaster

    Problem must be solved in the v6.47 already, try it please.

    #40879
    eledh
    Participant

    Hi,
    Both problems solved, thanks

    #40905
    Support
    Keymaster

    Font style is taken from system now. You think will be better to have another style?

    #40957
    eledh
    Participant

    Hi, yes I think that it would be great if I can set font style of form caption. Or at least make caption bold for every system. I test this in win7 and caption is not bold and in win XP it is bold. Please use bold style for caption everytime or give us option (property on skinprovider) to set own font and its style

    #40990
    Support
    Keymaster

    We must think how to organize it more handy…
    Maybe to make a global object CustomTitleFont : TFont = nil and check this object. When it's not nil then may be used for drawing in the form title…
    What you think?

    #41036
    eledh
    Participant

    Hi,
    yes, it sounds good. It will be global for all form, same style for all forms, but I think it is enought. Would be it too complicated to add this “CustomTitleFont” to SkinProvider? And specify so different font styles for each form individualy. This property should be accessible in object inspector, so we can set font style easily in design time. Where should be global object “CustomTitleFont” set? In main form OnCreate event? Or in DPR file?
    I think that individual “CustomTitleFont” property is more comfortable.

    I will be grateful for any of these options. It depends on you, what is easier for you

    #41045
    HeDiBo
    Participant

    QUOTE (Support @ Nov 9 2009, 10:13 AM) <{POST_SNAPBACK}>
    Maybe to make a global object CustomTitleFont : TFont = nil and check this object.

    I also think, putting it in SkinProvider as a published property is a better solution

    #41068
    Support
    Keymaster

    Hello!

    QUOTE (HeDiBo @ Nov 11 2009, 06:05 PM) <{POST_SNAPBACK}>
    I also think, putting it in SkinProvider as a published property is a better solution
    #41089
    HeDiBo
    Participant

    QUOTE (Support @ Nov 16 2009, 10:19 AM) <{POST_SNAPBACK}>
    I must say that question is not easy..

    If it's that much trouble, I wouldn't bother.

    #41108
    Support
    Keymaster

    QUOTE (HeDiBo @ Nov 16 2009, 06:26 PM) <{POST_SNAPBACK}>
    If it's that much trouble, I wouldn't bother.
    #41116
    HeDiBo
    Participant

    QUOTE (Support @ Nov 17 2009, 12:13 PM) <{POST_SNAPBACK}>
    But maybe one global property will be more handy for developer?

    I simply hate globals: in the end they always end up becoming non-global.

    QUOTE (Support @ Nov 17 2009, 12:13 PM) <{POST_SNAPBACK}>
    What about first two problems?
    #41121
    Support
    Keymaster

    Eledh, what you think?

    #41129
    eledh
    Participant

    Hi,
    If you mean “What about first two problems”, problems with sWebLabel and mouseover, it is solved and it works properly now. <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />
    My opinions to your post (Nov 16):

    2. Yes, I think that is not problem, if dialogs will have standard font, from system, like now. Sometimes I ignore DPI in forms (Scaled), and I want to draw all items in all systems in the same size. So in this case, it would by very useful, if form caption (and whole form's captionbar) is always in the same style too. But it is not important for dialogs, so these can be drawn according to system settings.

    1. I do not know how it is hard to make this, but if may I suggest:
    Add “CustomTitleFont : TFont” and “UseCustomTitleFont : boolean” to SkinProvider. If UseCustomTitleFont is false, then you can use standard font from system like now, if it is true and CustomTitleFont not nil, then CustomTitleFont style can be used.
    And publish these two properties in object inspector.
    Of course, if it is too hard to implement this, I think that global variable is enought and there is nothing bad on it. What I need is option to set font style (fsBold especially).
    Frankly, I probably have no use for individual font style of each form caption for now, just it would be a nice feature <img src="style_emoticons//smile.gif” style=”vertical-align:middle” emoid=”:)” border=”0″ alt=”smile.gif” />
    I appreciate any option how to make form caption bold/non-bold.

    #41130
    HeDiBo
    Participant

    If dialogs go back to the standard font, I wouldn't be very happy

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