You can certainly put the grid definition in the grid init, especially if it does not change after it comes up. The particular scenario that took me to use form level methods to handle this involved changing the number of columns (and data) shown based on the user selecting a different option in the UI after the initial grid instantiation. Think of a form with a grid and radio buttons to change the grid view. Being a bit on the pedantic side, I don't like calling the INIT of a control after it's been...INITed. :-)
-- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, June 05, 2014 11:46 AM To: [email protected] Subject: Re: How to trigger an update in a grid On 2014-06-05 04:51, Alan Bourke wrote: > On Wed, Jun 4, 2014, at 11:25 PM, Richard Kaye wrote: >> Over >> the years, when I've had the need to do really fun stuff with grids, >> I've ended up writing methods to set the datasource and rebuild the >> grid in code. > > This. It really is easier and more flexible in the long run IMO. See the email I sent awhile back with the grid.SaveSource and grid.RestoreSource code and how I set my columns in grid.Init too in my framework. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD044239A77A546@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
