Coming in late ... Looks like the original question was answered (and

then some!)

I'd just like to add my impression that Bindevents is a 'megatool'. In

the archives you'll find a discussion where I mentioned now being able

to add a single line of code to INIT for each new grid/class to add

column sorting to every column in the grid in one stroke, uniformly and

with assurance that later changes to the grid will not mess this feature

up in any way.

I think that, like every other tool in our bag, we need to know when to

use it and when not to. One concern I feel is that we also need to pay

special attention to documenting the use bindevents so we don't drive

Joe Maintainer nuts ("where the heck did THAT come from?").

Okay, just thought of this, but maybe similar to using an 'object

factory' to create objects, a 'bindevents factory' can handle

bindevents. The object factory (if I'm using the term correctly)

maintains a cursor of currently active objects. Similarly, the

bindevents factory can maintain a cursor all active bindevents, and that

way Joe can have diagnostics showing all current objects and active

bindevents (viewable in a separate diags screen, of course). Be a good

reminder they are active in the system.

Bill

> Hello, everyone

>

> I think I am missing the phylosophy here. What's the

> difference between

> these two? As far as I can understand, I can raise an event

> from any method;

> in other words, RaiseEvent can cause a custom method to

> behave like an

> event - to get executed when something happens. Well; let's

> assume in a

> button Click() snippet I enter a RaiseEvent() and raise a

> custom method as

> event. The same can be achieved by binding through BindEvent

> my custom

> method and button's Click(). Also, I can simply call my

> custom method from

> button Click().

>

> What's the difference? what can be done thru RaiseEvent and

> cannot be done

> thru BindEvent()? a sample would be greatly appreciated. I

> don't understand

> what I am missing, although I am obviusly missing something.

>

> Thank you.

>

>

>

[excessive quoting removed by server]