John wrote: > On Wednesday 10 February 2010 02:41:59 pm Ricardo Aráoz wrote: > >> John wrote: >> >>> Is there another (maybe better) way? I have considered not associating >>> the dropdown with a DataField and DataSource and handle the update and >>> save at the UI level. But that seemed to violate rule one of the >>> framework. >>> >>> Johnf >>> >> Does it? >> If your dropdown list where not dynamic, where would you populate the >> list? I guess in the form's AfterInit() which would call >> Form.contactChoices() which would call the appropriate bizobj method >> to get the list of choices. >> In this other case you would have a your grid's onGridCellSelected() (in >> case you used a grid to change parent's record) which would call >> Form.contactChoices() which would call the appropriate bizobj method >> to get the list of choices. >> I don't see too much of a difference. >> > > Yes I think you are close to what would be required for Ed's solution. > However, what I did using a subclass and the update() I also did not like. I > try hard not to go outside of the framework - if possible. I felt like what > I did was going outside of the framework. Which in turn made me consider > that maybe an attribute/property or method should be provided for situations > like this. > > Johnf >
I just took a look at the dropdown list's methods in the class designer. Are you aware there is an onUpdate() method where you could place the code you had placed in the update() method? Then you wouldn't be out of the framework, onUpdate() is there for you to customize. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
