> "
> The problem here is that settings can not be removed by later calls.
>
>
Yes, I see:
procedure tskinextender.removeskin(const ainfo: skininfoty;
var handled: boolean);
begin
//dummy
end;
Next question:
Is this way t
On Saturday 14 February 2015 11:47:56 Alexandre Minoshi wrote:
> > "
> > The problem here is that settings can not be removed by later calls.
>
> Yes, I see:
>
> procedure tskinextender.removeskin(const ainfo: skininfoty;
> var handled: boo
>
> Yes, tfiledialog.execute() calls tfiledialogfo.create() -> twidget.loaded()
> calls updateskin().
>
>
No, I can not found by myself :-\
How to seize the moment when the MSEapplication creates a new window?
A.M.
--
D
On Saturday 14 February 2015 15:21:34 Alexandre Minoshi wrote:
> > Yes, tfiledialog.execute() calls tfiledialogfo.create() ->
> > twidget.loaded() calls updateskin().
>
> No, I can not found by myself :-\
>
> How to seize the moment when the MSEapplication creates a new window?
>
Use a tskincontrol
> Use a tskincontroller, set active to true. Either use the properties of
> tskincontroller in order to update the skin of loaded components or use
> tskincontroller.onafterupdate, ainfo.instance is the calling component.
>
> Martin
>
> --
And how without tskincontroller?
A.M.
--
On Saturday 14 February 2015 15:45:15 Alexandre Minoshi wrote:
> > Use a tskincontroller, set active to true. Either use the properties of
> > tskincontroller in order to update the skin of loaded components or use
> > tskincontroller.onafterupdate, ainfo.instance is the calling component.
> >
> >
6 matches
Mail list logo
