ReportControl: SelectionChanged Event Bug

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   The 'SelectionChanged' event fires when no selection change has taken place.  If you select any row in the ReportControl, the 'SelectionChanged' event will fire.  Now click again in the same row and same item you clicked the first time.  Again, the 'SelectionChanged' event will fire.  This event should only change if you select a different row or different item in the same row.
You can verify this bug using the sample application.  Just watch the output window and you'll see the message posted by the 'SelectionChanged' event.
I hope a fix for this can make it into the next release of ReportControl.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Boyd Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 08 December 2003 Location: United States Status: Offline Points: 285	Post Options Post Reply Quote Boyd Report Post Thanks(0) Quote Reply Topic: ReportControl: SelectionChanged Event Bug Posted: 29 December 2004 at 7:48pm
	The 'SelectionChanged' event fires when no selection change has taken place. If you select any row in the ReportControl, the 'SelectionChanged' event will fire. Now click again in the same row and same item you clicked the first time. Again, the 'SelectionChanged' event will fire. This event should only change if you select a different row or different item in the same row. You can verify this bug using the sample application. Just watch the output window and you'll see the message posted by the 'SelectionChanged' event. I hope a fix for this can make it into the next release of ReportControl.

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply Posted: 22 February 2005 at 10:30am
	This will be fixed in version 9.60.1 (releasing very soon).