If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

That depends.... are they adding Form_Unload and the ability to Unload a
form and later Load it again and have the controls reset to the design-time
values while module-level variables are retained? Given that the WinForm
model doesn't have the same class/gui split that VB forms did it seems
doubtful and simply adding a Form_Load event is pretty meaningless.

Re: Rumors for beta 2

On the contrary there is a subtle difference between New and when the
form_load is called. New is called when an instance of the form is created.
The form_load event is fired when the form is actually shown. For code that
creates and shows the form immediatly afterwards, it has little new benefit,
but for code that does not, it is really useful to have the form_load event.

So for example if you were going to run an action that may take some time.
You have a class that does the action and also shows a form, with a cute
status animation and progress bar. The form will use a timer to update the
progressbar and the animation. You may want to be able to create an instance
of the class, then set some member variables, possibly even pass the form
around a bit. You then add code to the form_load event to start the timer
and the action that takes some time. Without the form_load event, it is not
easy to know when the form is actually opened. You could hook on one of the
other events such as activated, but you end up with a bunch of logic to
check if it is being called when the form is opened, or just brought to the
front again.

Sam

"Bob Butler" <butlerbob@earthlink.net> wrote in message
news:3ab7d3c9@news.devx.com...
>
> "Matthew Solnit" <msolnit@nospam.yahoo-com> wrote in message
> news:3ab7d13e$1@news.devx.com...
> > "Patrick Troughton" <Patrick@Troughton.com> wrote in message
> > news:3ab7d08d$1@news.devx.com...
> > >
> > > Rumors for beta 2....
> > >
> > > - Form_Load for Win Forms
> >
> > It seems to me like we could just use the form's constructor (Sub New).
> Am I
> > missing something?
>
> That depends.... are they adding Form_Unload and the ability to Unload a
> form and later Load it again and have the controls reset to the
design-time
> values while module-level variables are retained? Given that the WinForm
> model doesn't have the same class/gui split that VB forms did it seems
> doubtful and simply adding a Form_Load event is pretty meaningless.
>
>
>

Re: Rumors for beta 2

"Sam Spencer [msft]" <samsp@microsoft.com> wrote in message
news:3ab831bb$1@news.devx.com...
> On the contrary there is a subtle difference between New and when the
> form_load is called. New is called when an instance of the form is created.
> The form_load event is fired when the form is actually shown. For code that
> creates and shows the form immediatly afterwards, it has little new benefit,
> but for code that does not, it is really useful to have the form_load event.

Okay, so the constructor is like VB6's Form_Initialize, and Form_Load would be
just like VB6's Form_Load. Right?

Re: Rumors for beta 2

"Sam Spencer [msft]" <samsp@microsoft.com> wrote in message
news:3ab831bb$1@news.devx.com...
> On the contrary there is a subtle difference between New and when the
> form_load is called. New is called when an instance of the form is
created.
> The form_load event is fired when the form is actually shown. For code
that
> creates and shows the form immediatly afterwards, it has little new
benefit,
> but for code that does not, it is really useful to have the form_load
event.
>

I understand the difference in VB6 but it still seems pointless in VB.Net
without the corresponding behavior of the class vs gui distinctions. Adding
the Form_Load event is just more smoke and mirrors to hide the fact the the
underlying model is so drastically changed that virtually no code can be
moved from VB6 without some serious revisions.

Re: Rumors for beta 2

>
> I understand the difference in VB6 but it still seems pointless in VB.Net
> without the corresponding behavior of the class vs gui distinctions.
Adding
> the Form_Load event is just more smoke and mirrors to hide the fact the
the
> underlying model is so drastically changed that virtually no code can be
> moved from VB6 without some serious revisions.
>
>

It will be convenient to have this in vb.net though. Right now (I think),
the nearest event thrown is OnHandleCreated. The distinction between the
Handle being created and the Form actually being shown is convenient. This
way, we don't have to set some class level boolean and constantly check the
boolean throughout the code at various events during processing. Regardless
of any alleged smoke and mirrors, it will be a convenient event to have.

Re: Rumors for beta 2

On Tue, 20 Mar 2001 23:00:56 -0800, "Jonathan Allen"
<greywolf@cts.com> wrote:
>> Nothing about AND OR and NOT retaining their original properties?
>
>I don't see that happening. You will have to use either BitAnd or the And()
>function to get the old behavior.

You, and some others, have missed the point entirely on this one.

It's not simply about having AND OR NOT XOR as bitwise, it's about
logical expression evaluation on the whole. That also includes the
value of True and operator precedence. Here is how it's *supposed* to
work:

Re: Rumors for beta 2

Stop your trolling, it is getting old. He asked will it change back, I
answered no. At no time in this thread did we discuss wither or not that was
a good thing.

--
Jonathan Allen

"Dan Barclay" <dbarclay@ih2000.net> wrote in message
news:dcthbton0q9etklkngrn890det1ljnb900@4ax.com...
> On Tue, 20 Mar 2001 23:00:56 -0800, "Jonathan Allen"
> <greywolf@cts.com> wrote:
>
> >> Nothing about AND OR and NOT retaining their original properties?
> >
> >I don't see that happening. You will have to use either BitAnd or the
And()
> >function to get the old behavior.
>
> You, and some others, have missed the point entirely on this one.
>
> It's not simply about having AND OR NOT XOR as bitwise, it's about
> logical expression evaluation on the whole. That also includes the
> value of True and operator precedence. Here is how it's *supposed* to
> work:
>
> http://www.mvps.org/vb/tips/truth.htm
>
> Dan
> Language Stability is a *feature* I wish VB had!
> (#6)

Re: Rumors for beta 2

On Wed, 21 Mar 2001 11:04:51 -0800, "Jonathan Allen"
<greywolf@cts.com> wrote:
>>
>> You, and some others, have missed the point entirely on this one.
>
>Stop your trolling, it is getting old. He asked will it change back, I
>answered no. At no time in this thread did we discuss wither or not that was
>a good thing.

Not trolling, hotshot. You were discussing the issue of AND OR NOT
being bitwise. I am pointing out that being bitwise isn't the issue
that matters.

Re: Rumors for beta 2

"Sam Spencer [msft]" wrote:
>
> On the contrary there is a subtle difference between New and when the
> form_load is called. New is called when an instance of the form is created.
> The form_load event is fired when the form is actually shown. For code that
> creates and shows the form immediatly afterwards, it has little new benefit,
> but for code that does not, it is really useful to have the form_load event.

I'm not sure form_load is the best name for it. Isn't the pre-.net
form_load more like the .net "New" than the .net "form_load"?

I'm not arguing against the feature, just suggesting that there might
be a better name for it that conveys the meaning without giving false
impressions about similarities to functionality in previous versions.