|
|
You're in the
vb.net controls
group:Tab control
vb.net controls:
I have a tab page with 2 tabs on my form. The controls on tab A return a
visible property of False if tab B is currently selected even though the Control.Visible property for each control has been explicitly set to True. Is this how its supposed to work? Why does it go ahead and modify the properties of every control on my tab page? That ridiculous. How am I supposed to know, if the control is located on the non-active tab, whether it is going to be visible when the user clicks back to it? If they all return false then how am I supposed to know which ones are going to be visible when the tab is selected again? If you're going to say "Well the control isn't visible is it?" then why doesn't it set the .Visible property to False if I have another window covering the control? Or if the control is located outside the bounds of the screen? The other thing that I find stupid about the tab control is why it defaults the backcolor of each tab to Transparent? If you change them all to Control, and you add another tab, then its sets every single tabpage in the tabcontrol back to Transparent. Stupid thing.
"Luke R" <dont@spam.me>'s wild thoughts were released on
Fri, 29 Jun 2007 14:43:52 +1200 bearing the following fruit: [quoted text, click to view] >I have a tab page with 2 tabs on my form. The controls on tab A return a >visible property of False if tab B is currently selected even though the >Control.Visible property for each control has been explicitly set to True. > >Is this how its supposed to work? Why does it go ahead and modify the >properties of every control on my tab page? That ridiculous. It probably doesn't modify the property. If a control has it's visible property set to true but it's container's visible property is set to false then then the control will report it's visible property as false. Besides, it's not visible so why worry? [quoted text, click to view] >How am I supposed to know, if the control is located on the non-active tab, >whether it is going to be visible when the user clicks back to it? If they >all return false then how am I supposed to know which ones are going to be >visible when the tab is selected again? Why do you need to know? [quoted text, click to view] >If you're going to say "Well the control isn't visible is it?" then why >doesn't it set the .Visible property to False if I have another window >covering the control? Or if the control is located outside the bounds of the >screen? That's a different scenario and the control is still accessible even if it is off screen. J [quoted text, click to view] >The other thing that I find stupid about the tab control is why it defaults >the backcolor of each tab to Transparent? If you change them all to Control, >and you add another tab, then its sets every single tabpage in the >tabcontrol back to Transparent. Stupid thing. -- Jan Hyde
[quoted text, click to view]
> It probably doesn't modify the property. What difference does it make really? It returns false when it is actually set to true. It returns the wrong value. [quoted text, click to view] > Why do you need to know? I think the question should be, why should i be prevented from knowing? Doing it the way it currently stands has limitations, namely that you do not know the true visible property of each control in the container until that container is made visible. Doing it the other way (which would seem more logical to me) has no limitations. You could establish whether the controls were available on the screen by testing for Tab.Selected, and you could establish which controls in the non-active tab are really visible or not by looking at their visible property. You can have it both ways, instead of just one way. In answer to your question; I need to know because I perform actions depending on which controls are visible, and when a tab is not selected, all the controls say false when really .Visible has been set to true. [quoted text, click to view] "Jan Hyde (VB MVP)" <StellaDrinker@REMOVE.ME.uboot.com> wrote in message
news:mjhh83hjhgmn4dfqrn1e2ie4t5h40tdft2@4ax.com... > "Luke R" <dont@spam.me>'s wild thoughts were released on > Fri, 29 Jun 2007 14:43:52 +1200 bearing the following fruit: > >>I have a tab page with 2 tabs on my form. The controls on tab A return a >>visible property of False if tab B is currently selected even though the >>Control.Visible property for each control has been explicitly set to True. >> >>Is this how its supposed to work? Why does it go ahead and modify the >>properties of every control on my tab page? That ridiculous. > > It probably doesn't modify the property. If a control has > it's visible property set to true but it's container's > visible property is set to false then then the control will > report it's visible property as false. > > Besides, it's not visible so why worry? > > >>How am I supposed to know, if the control is located on the non-active >>tab, >>whether it is going to be visible when the user clicks back to it? If they >>all return false then how am I supposed to know which ones are going to be >>visible when the tab is selected again? > > Why do you need to know? > >>If you're going to say "Well the control isn't visible is it?" then why >>doesn't it set the .Visible property to False if I have another window >>covering the control? Or if the control is located outside the bounds of >>the >>screen? > > That's a different scenario and the control is still > accessible even if it is off screen. > > J > >>The other thing that I find stupid about the tab control is why it >>defaults >>the backcolor of each tab to Transparent? If you change them all to >>Control, >>and you add another tab, then its sets every single tabpage in the >>tabcontrol back to Transparent. Stupid thing. > > > -- > Jan Hyde > > https://mvp.support.microsoft.com/profile/Jan.Hyde
"Luke R" <dont@spam.me>'s wild thoughts were released on
Tue, 3 Jul 2007 12:53:19 +1200 bearing the following fruit: [quoted text, click to view] >> It probably doesn't modify the property. >What difference does it make really? It returns false when it is actually >set to true. It returns the wrong value. It returns the correct value, just depends on you point of view I guess ;-) [quoted text, click to view] >> Why do you need to know? >I think the question should be, why should i be prevented from knowing? >Doing it the way it currently stands has limitations, namely that you do not >know the true visible property of each control in the container until that >container is made visible. No the question is why do you want to know. I can't help unless I know. It may be we can offer you alernative methods to achieve your goal. [quoted text, click to view] >Doing it the other way (which would seem more logical to me) has no >limitations. You could establish whether the controls were available on the >screen by testing for Tab.Selected, and you could establish which controls >in the non-active tab are really visible or not by looking at their visible >property. You can have it both ways, instead of just one way. > >In answer to your question; I need to know because I perform actions >depending on which controls are visible, and when a tab is not selected, all >the controls say false when really .Visible has been set to true. Can you give me any examples? J [quoted text, click to view] > >"Jan Hyde (VB MVP)" <StellaDrinker@REMOVE.ME.uboot.com> wrote in message >news:mjhh83hjhgmn4dfqrn1e2ie4t5h40tdft2@4ax.com... >> "Luke R" <dont@spam.me>'s wild thoughts were released on >> Fri, 29 Jun 2007 14:43:52 +1200 bearing the following fruit: >> >>>I have a tab page with 2 tabs on my form. The controls on tab A return a >>>visible property of False if tab B is currently selected even though the >>>Control.Visible property for each control has been explicitly set to True. >>> >>>Is this how its supposed to work? Why does it go ahead and modify the >>>properties of every control on my tab page? That ridiculous. >> >> It probably doesn't modify the property. If a control has >> it's visible property set to true but it's container's >> visible property is set to false then then the control will >> report it's visible property as false. >> >> Besides, it's not visible so why worry? >> >> >>>How am I supposed to know, if the control is located on the non-active >>>tab, >>>whether it is going to be visible when the user clicks back to it? If they >>>all return false then how am I supposed to know which ones are going to be >>>visible when the tab is selected again? >> >> Why do you need to know? >> >>>If you're going to say "Well the control isn't visible is it?" then why >>>doesn't it set the .Visible property to False if I have another window >>>covering the control? Or if the control is located outside the bounds of >>>the >>>screen? >> >> That's a different scenario and the control is still >> accessible even if it is off screen. >> >> J >> >>>The other thing that I find stupid about the tab control is why it >>>defaults >>>the backcolor of each tab to Transparent? If you change them all to >>>Control, >>>and you add another tab, then its sets every single tabpage in the >>>tabcontrol back to Transparent. Stupid thing. >> >> >> -- >> Jan Hyde >> >> https://mvp.support.microsoft.com/profile/Jan.Hyde -- Jan Hyde
[quoted text, click to view]
> No the question is why do you want to know. I can't help > unless I know. It may be we can offer you alernative methods > to achieve your goal. I appreciate your offer for assistance, but I have had to rewrite sections of my code, and my issue is already solved. I just think its really poor that the tab control works this way. One thing you can help me with is how do I stop the tab control from defaulting the backcolor of each tab to Transparent? If I go and set them all manually to Control, then each time I add or remove a new tab, every single tab page in the collection goes back to Transparent. Very annoying. [quoted text, click to view] "Jan Hyde (VB MVP)" <StellaDrinker@REMOVE.ME.uboot.com> wrote in message
news:341k8399sfehdqhnk01d6h2meigrrghqv6@4ax.com... > "Luke R" <dont@spam.me>'s wild thoughts were released on > Tue, 3 Jul 2007 12:53:19 +1200 bearing the following fruit: > >>> It probably doesn't modify the property. >>What difference does it make really? It returns false when it is actually >>set to true. It returns the wrong value. > > It returns the correct value, just depends on you point of > view I guess ;-) > >>> Why do you need to know? >>I think the question should be, why should i be prevented from knowing? >>Doing it the way it currently stands has limitations, namely that you do >>not >>know the true visible property of each control in the container until that >>container is made visible. > > No the question is why do you want to know. I can't help > unless I know. It may be we can offer you alernative methods > to achieve your goal. > >>Doing it the other way (which would seem more logical to me) has no >>limitations. You could establish whether the controls were available on >>the >>screen by testing for Tab.Selected, and you could establish which controls >>in the non-active tab are really visible or not by looking at their >>visible >>property. You can have it both ways, instead of just one way. >> >>In answer to your question; I need to know because I perform actions >>depending on which controls are visible, and when a tab is not selected, >>all >>the controls say false when really .Visible has been set to true. > > Can you give me any examples? > > J > >> >>"Jan Hyde (VB MVP)" <StellaDrinker@REMOVE.ME.uboot.com> wrote in message >>news:mjhh83hjhgmn4dfqrn1e2ie4t5h40tdft2@4ax.com... >>> "Luke R" <dont@spam.me>'s wild thoughts were released on >>> Fri, 29 Jun 2007 14:43:52 +1200 bearing the following fruit: >>> >>>>I have a tab page with 2 tabs on my form. The controls on tab A return a >>>>visible property of False if tab B is currently selected even though the >>>>Control.Visible property for each control has been explicitly set to >>>>True. >>>> >>>>Is this how its supposed to work? Why does it go ahead and modify the >>>>properties of every control on my tab page? That ridiculous. >>> >>> It probably doesn't modify the property. If a control has >>> it's visible property set to true but it's container's >>> visible property is set to false then then the control will >>> report it's visible property as false. >>> >>> Besides, it's not visible so why worry? >>> >>> >>>>How am I supposed to know, if the control is located on the non-active >>>>tab, >>>>whether it is going to be visible when the user clicks back to it? If >>>>they >>>>all return false then how am I supposed to know which ones are going to >>>>be >>>>visible when the tab is selected again? >>> >>> Why do you need to know? >>> >>>>If you're going to say "Well the control isn't visible is it?" then why >>>>doesn't it set the .Visible property to False if I have another window >>>>covering the control? Or if the control is located outside the bounds of >>>>the >>>>screen? >>> >>> That's a different scenario and the control is still >>> accessible even if it is off screen. >>> >>> J >>> >>>>The other thing that I find stupid about the tab control is why it >>>>defaults >>>>the backcolor of each tab to Transparent? If you change them all to >>>>Control, >>>>and you add another tab, then its sets every single tabpage in the >>>>tabcontrol back to Transparent. Stupid thing. >>> >>> >>> -- >>> Jan Hyde >>> >>> https://mvp.support.microsoft.com/profile/Jan.Hyde > > -- > Jan Hyde > > https://mvp.support.microsoft.com/profile/Jan.Hyde
[quoted text, click to view]
"Luke R" <dont@spam.me> wrote in message news:%23NxHMVdvHHA.356@TK2MSFTNGP02.phx.gbl... > > One thing you can help me with is how do I stop the tab control from > defaulting the backcolor of each tab to Transparent? If I go and set them > all manually to Control, then each time I add or remove a new tab, every > single tab page in the collection goes back to Transparent. Very annoying. > Set the TabPages UseVisualStyleBackColor property to false. -- Mick Doherty http://www.dotnetrix.co.uk/nothing.html
Don't see what you're looking for? Try a search.
|
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |