vs2003 - Bug?

[Guest]

I have a form that had a button called but_Edit which had it's visible
property set to False. I have been working on an applicaiton using this form
for some time and all was going well and it ran fine and I could use the
but_Edit control making it visible when I wanted and etc.

However, it suddenly disappeared and I could no longer reference but_Edit in
code. The Form Designer code still had all the information showing where it
was added to the form. I had to remove all the designer code for the
but_Edit button and re-add the button to the form using the toolbox.

Has this happened to anyone?

Also, I had a user control which had a boolean property that I could set in
the Designer mode to either True or False and it worked fine. Then one day,
I could only set it to False as it would accept True. I had to remove the
property from my control then re-add it to get it to work again where I could
select True or False.

Any thoughts on these two problems?

 

[Cor Ligthert]

Dennis,

I thought knowing from a previous message from you that you are working with
VBNet 2002.

I was directly very happy with VSNet 2003 especially because all that crazy
behaviour of the IDE was gone. I don't know how much (regular) visitors of
this newsgroup are still using it. (I know at least one). So please tell
next time when you have strange IDE behaviour, that you are using VB2002
when I am right in that. And when I make a mistake in that, tell that as
well.

On the other hand when you have found a bug than:
Show the documentation how it should work
Give a piece of software where is reproducable that it is not working
accoording to that.

In otherways, please do not call something a directly a bug, with that goes
the attention from Microsoft on real bugs in this newgroup to nothing.

Cor

 

[Guest]

I have vs2003 and am working with it using VB.Net. You will note that I
qualified my bug in the subject with a ?. That MEANS that I am questioning
if it is really a bug.

As for the code, my problem does not lend itself to posting code. It
happens in the IDE which deletes one of my controls. I have no idea what
causes it, it just happens occasionally that my button control becomes
unusable. All the code in the desinger indicates that it is still there but
I just can't seem to get my program to recognize it when I run the
application.

 

[james]

I have never seen this sort of behavior in VB.NET either in 2002 or 2003. Could it be that somewhere in your code you have set
the button's Visible property to False? I would use Find and step thru all my code looking for every reference to this button
and you might be suprised to find that you have done something in your code to disable it. Or at least set it's visible property
to false .
I know I have done things before that have disabled a working control or routine and I could swear that I did not change
anything connected with the control or routine. Until, I went and looked at a backup copy of my app or used Find to check all
references to the control or routine and found that I had changed something.
Just a thought.
james

 

[Cor Ligthert]

Dennis,

I readed it wrong, I see that I remembered it me wrong in this thread, where
Nick said that he has VB2002. There are have completly tried to do what was
your problem and had no problem. When it is a bug it is reproducable you
know.

The question mark does in my opinon make no sense, because maybe you don't
do that however it can be readed that you are suggesting that it can be a
bug.

On that question will you get probably no answer, because probably nobody
knows about that bug, so there is no answer needed.

This is the thread where I am talking about where I did that problem what
you suggested as maybe a bug?.
http://tinyurl.com/6wly2

Therefore the answers on your questions can be, no I don't know that bug. Or
no answers at all.

In my opinion will when you make a better subject give a better answer, and
than not directly suggesting that it is a bug.

Mostly come this kind of problems because people are editing a little bit
without knowing what they are doing in the designer part of the code.

However just my thoughts

Cor

 

[Lloyd Sheen]

I had problems like this after my original install of VS 2003. After
unistalling and reinstalling whatever was causing the problem (what you
describe was one of the problems) it went away. Kind of a get out of the
car and back in to make it work. Another way you can get this is to do a
major reposition of controls on the form or setting controls to front or
back. After that I would loose controls often, as you say the controls
would disappear but when attempting to re-add them it would have problems
since somewhere in the project there were references. Once had to create a
new form with the controls where I wanted them and then copy the code from
the old form.

I have tried the new VB.Express and it seems that all the IDE problems I was
having with 2003 are gone now. So wait another year and this will be gone.

Lloyd Sheen

 

[Mick Doherty]

I have seen this on one or two occasions, but I could not reproduce it.
When it happened there were 50 or 60 buttons on a form and one or two of
them would not show up at all.
I believe I copied and pasted to the form, but I'm not 100% sure on that.

The missing buttons were properly Serialized in the InitializeComponent
method and I could select them, via the dropdownlist in the Property Browser
and change properties, but they would not show on the form.
To fix them I had to select them in the property browser click on the
Form.vb [Design] tab and press delete.
I was then able to replace them.

Not much of a help I know, but it is a confirmation that this has been seen
before.

 

[Mick Doherty]

Cor,

I usually don't disagree with you, but on this occasion I'm afraid I must.

Bugs are not always reproducable. Try to reproduce the bug where the cursor
is locked in a tabpage. I know of this bug and often encounter it, but I
have never found a way to reproduce it. I must just say that it is not only
the tabcontrol that it happens to, but it is usually the culprit.

I have also encountered this problem of controls not displaying on a form
even though they are properly serialized and have been added to the forms
collection, but again it was nothing I could reproduce.

 

[Cor Ligthert]

Mick,

We may disagree and I have not any problem with that, however in my opinion
is a bug repoducable.

A bug is a program error, did you not hear that there was an error in your
program because people would have it in another way than you had designed
it.

That does not mean that there are bugs that are hard to reproduce.

Before that time that it is not reproducable it is in in my opinion a
problem (and after that as well however not how to find but how to solve).

Just my thought,

Cor

"Mick Doherty"

news:[email protected]...

 

[Herfried K. Wagner [MVP]]

We may disagree and I have not any problem with that, however in my
opinion is a bug repoducable.

Sure, but only if you know the exact circumstances under which the bug
"occurs". Sometimes it's hard to find them.

 

[Cor Ligthert]

"Herfried K. Wagner [MVP]"

Sure, but only if you know the exact circumstances under which the bug
"occurs". Sometimes it's hard to find them.

This is what I wrote in the rest of the message that you deleted, so what is
the reason of your attachment?

Cor

 

[Landley]

This IS an IDE bug!

I have 2003 installed in 3 places at home, not to mention numerous machines
at work. This happens quite frequently. You could literally open a form in
the design view, close it without making any changes, and open it again, and
a control could vanish.

Now, the IDE does remove a line from within the Form Designer Code. The
declarations remains, the instantiation remains, the " ... Controls.Add( ...
" line vanishes.

I have managed to pin point a cause for this, but its been there since day
one. MS should have focused on getting IDE working instead of building a
new version (namely 2005) on top of 2003 buggy code. Basic project
management methinks.

L.

 

[Mick Doherty]

That's something different.
The Controls.Add(...) line is still present in this situation and the
control in question can be selected and manipulated in the property browser,
but does not show on the form despite all code being there to show it.