On 4/20/12 10:21 AM, Ed Leafe wrote: > On Apr 20, 2012, at 12:16 PM, Paul McNett wrote: > >>> There still is a problem, though. I have cursor with all different data >>> types, but they are all displayed using the default >>> self.stringRendererClass. I'm looking into where the code is failing to >>> properly set the renderer. >> >> If you are creating the string exactly how you want it displayed in the >> VirtualField, >> why do you care if it is displayed in the grid using the string renderer? > > You're missing the point. "Default" means that the grid should select > the appropriate renderer for the given data type. It isn't doing that.
Sorry, I thought you were commenting on my proposed VirtualFields solution. "There is still a problem, though" I took to mean as a problem with my approach. > Of course, if you go to all the trouble of defining VirtualFields for > all your data, then that's fine. But you shouldn't *have to* do that to get > correct behavior. I agree. Paul _______________________________________________ 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]
