Subject | Re: More Scroll Questions... (More Info) |
---|---|
Author | Eric Handbury |
Post date | 2002-10-16T00:57Z |
--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
row change. That row change may be a result of a grid operation, or a
NavigatorBar operation, or an Insert that has been cancelled, etc.
But these are all 'real' row changes initiated by 'user' operations.
Overall, with all events, I would want a separation between what
IBO must do internally from its published interface.
never possess, but I have to ask... aren't the current Scroll events
meant to do only what I ask? Why do we need a new event?
> Does this boil down to you wanting a distinction between an eventfor the
> actual surety that a scroll is happening or just that it may happen?In this instance, I want a before/after event which fires only on a
row change. That row change may be a result of a grid operation, or a
NavigatorBar operation, or an Insert that has been cancelled, etc.
But these are all 'real' row changes initiated by 'user' operations.
Overall, with all events, I would want a separation between what
IBO must do internally from its published interface.
> I'm confident there will not be any fundamental changes in thispart of IBO,
> but I would consider adding in a new event that had the behavior youI can appreciate that you have knowledge about IBO that I will
> desired.
never possess, but I have to ask... aren't the current Scroll events
meant to do only what I ask? Why do we need a new event?