The problem is fixed in: Name: Pier-All-lr.230 Author: lr Time: 17 August 2007, 6:35:49 pm UUID: 49baa1a6-da58-4dfb-8c98-ec9d1c2a521e Ancestors: Pier-All-lr.229 Dependencies: Pier-Model-lr.162, Pier-Tests-lr.73, Pier-Seaside-lr. 194, Pier-Security-lr.87, Pier-Blog-lr.58 - fixes: "when i added a system users component to a page, when i click on any thing on the component which invokes a callback. i get the following error 'Components not found while processing callbacks: an Array(a PUUsersWidget)'. " (thanks to isaiah) -- Lukas Renggli http://www.lukas-renggli.ch

This is something currently not supported by Magritte. That's why the add and edit step are separated. In case of PRComponent there are even 3 steps required: (1) choose to add a component, (2) select the kind of component class to add, and (3) setup the properties of the component class. Of course it would be nice to combine those steps into one, but as I said Magritte is not really designed to support that kind of functionality all automatic. There are many different kind of objects involved and one can think of many different ways how this interaction could happen, which makes it difficult to do meta- descriptions. What I suggest is that you override #asComponent in you command and put some glue code that builds different Magritte forms and displays them depending on the state of the other Magritte components. That works quite well and requires only little manual code to be written. Moreover it can be even combined with manual created forms, etc. Lukas -- Lukas Renggli http://www.lukas-renggli.ch