20 Jul
2010
20 Jul
'10
4:55 p.m.
Lukas Renggli wrote:
I forgot to make it clear that the situation is for different login
sessions - i.e. the settings change is made in a designer session, but
in a concurrent guest session, the settings change only appears if I let
the guest session expire, then login again.
My image is about 5 weeks old, but I will be updating soon.
Suppose a
Seaside component is added to a Pier page using a PRComponent. The
Seaside component is initialized using values stored in the PRComponent
settings dictionary. If these settings are changed later on, these changes
are not reflected in the corresponding Seaside component instances until the
corresponding session expires, and the Seaside component is then recreated.
To handle this, I've created a PRRefreshCommand, which does:
self structure flush
in its #doExecute.
Why is this necessary? At least in my image, the settings
automatically reflect in all instantiated components. If not that
would be a bug.