Hello,
I discovered that Font.OnChange of Form and their Components after creation is already assigned (not nil). Is it Ok?
Valdas Jank?nas
Mailing lists / lazarus / 2012-11
Font.OnChange already occupied
4 messages · 2 people ·
- Mattias Gaertner 2
- Valdas Jankūnas 2
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hello, I discovered that Font.OnChange of Form and their Components after creation is already assigned (not nil). Is it Ok?
Yes.
Mattias
2012.11.21 14:46, Mattias Gaertner ra??:
Show quoted text 10 lines
On Wed, 21 Nov 2012 14:33:13 +0200
Valdas Jank?nas wrote:
> Hello,
>
> I discovered that Font.OnChange of Form and their Components after
> creation is already assigned (not nil). Is it Ok?
Yes.
So, if I use own "Font.OnChange" event handler, then correct way is: to call inherited event handler (saved before assignment) before font modification (of child components) in own event handler or after?
Valdas Jank?nas
Show quoted text 15 lines
2012.11.21 14:46, Mattias Gaertner ra??:
> On Wed, 21 Nov 2012 14:33:13 +0200
> Valdas Jank?nas wrote:
>
>> Hello,
>>
>> I discovered that Font.OnChange of Form and their Components after
>> creation is already assigned (not nil). Is it Ok?
>
> Yes.
>
So, if I use own "Font.OnChange" event handler, then correct way is: to
call inherited event handler (saved before assignment) before font
modification (of child components) in own event handler or after?
Yes.
Mattias