We always used data binding – so the object that it was bound to was populated long before the UI would be clicked on anyway (in most cases).
Regards Mitch Denny Readify | Chief Technology Officer Suite 408 Life.Lab Building | 198 Harbour Esplanade | Docklands | VIC 3008 | Australia M: +61 414 610 141 | E: [email protected]<mailto:[email protected]> | W: www.readify.net<http://www.readify.net/> The content of this e-mail, including any attachments is a confidential communication between Readify Pty Ltd and the intended addressee and is for the sole use of that intended addressee. If you are not the intended addressee, any use, interference with, disclosure or copying of this material is unauthorized and prohibited. If you have received this e-mail in error please contact the sender immediately and then delete the message and any attachment(s). From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Wednesday, 24 November 2010 12:27 PM To: 'ozDotNet' Subject: RE: Azure DB performance Mitch, this certainly won’t turn us off Azure DB as the benefits of the facility far outweigh any performance curiosities. In real life I doubt if anyone is going to sit at their machine and insert thousands of records. We will work the way it wants, not the other way around. And yeah, WinForms tab controls do stink sometimes. The contents of the tab contents don’t get a Window handle created until the first time they’re shown, so you can’t “push” values into them and the timing gets fiddly. I haven’t noticed yet if the WPF tab control has the same behaviour. Greg
<<inline: image001.png>>
