Vince Teachout wrote: > Sietse Wijnker wrote: >> Hi Vince, >> The point that's made in the previous post about the bindevent, is that you >> write the code to bind to the dblClick once in the grid(class) and the never >> have to worry about it again, because when the grid runs, all controls in >> the grid delegate their dblclick to the grids method you specified. That way >> you don't have to visit each and every control to place your code there, or >> write a 'builder' to put the code you've otherwise put there manually. >> There's just no need any more to code the controls. >> > > Ah yes, I see what you mean. That is another good approach. The only > downside I can see to that is that it might be a little trouble to > maintain. If I click a button, and something goes wrong, the first thing > I do is look in the click method of the button - in this case, there > will be nothing there. But I do see where it could have it's uses. Thanks!
That's what I do. I put the real call to the form method in the grid's double-click, and then each "cell" (Text1).DblClick method is just "this.parent.parent.DblClick()" Generic as can be without requiring any extra effort (other than putting them there to start). _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
