473,396 Members | 1,860 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,396 software developers and data experts.

Label Autosize Property... Possible bug??

Hi, I've made the next inherited class in Visual Studio 2005:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
MyBase.AutoSize = value
End Set
End Property
End Class

The problem is that Autosize Property remains always as true when I go
to design mode and put my LabelEx from the ToolBox to the form. Looking
at the designer file, I can see as every property I have set to all my
other extended controls is correct, except from autosize for labels...
Any idea??? I've been unable to find this anywhere, and it looks like a
bug, doesn't it? By the way, this code works properly in VS 2003, and
although the default in 2003 is Autosize=false, if I put it to true, it
works with no problem, the designer sets the value I've said...

Jun 16 '06 #1
8 3393
Jordi,
I noticed that the other day, it feels like a bug to me, as VS is "breaking"
the contract that System.ComponentModel.DefaultValue states.

I will see what I can find.

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Jordi Rico" <jo*******@gmail.com> wrote in message
news:11*********************@u72g2000cwu.googlegro ups.com...
| Hi, I've made the next inherited class in Visual Studio 2005:
|
| Public Class LabelEx
| Inherits System.Windows.Forms.Label
|
| Sub New()
| MyBase.New()
| Me.ForeColor = Color.Black
| Me.AutoSize = False
| Me.Height = 16
| End Sub
|
| <System.ComponentModel.DefaultValue(False)> _
| Public Overrides Property AutoSize() As Boolean
| Get
| Return MyBase.AutoSize
| End Get
| Set(ByVal value As Boolean)
| MyBase.AutoSize = value
| End Set
| End Property
| End Class
|
| The problem is that Autosize Property remains always as true when I go
| to design mode and put my LabelEx from the ToolBox to the form. Looking
| at the designer file, I can see as every property I have set to all my
| other extended controls is correct, except from autosize for labels...
| Any idea??? I've been unable to find this anywhere, and it looks like a
| bug, doesn't it? By the way, this code works properly in VS 2003, and
| although the default in 2003 is Autosize=false, if I put it to true, it
| works with no problem, the designer sets the value I've said...
|
Jun 16 '06 #2
Hi Jay,
if you find something please tell me, I'm looking everywhere and cannot
find anything clear...
Thank you
Jay B. Harlow [MVP - Outlook] ha escrito:
Jordi,
I noticed that the other day, it feels like a bug to me, as VS is "breaking"
the contract that System.ComponentModel.DefaultValue states.

I will see what I can find.

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
.NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Jordi Rico" <jo*******@gmail.com> wrote in message
news:11*********************@u72g2000cwu.googlegro ups.com...
| Hi, I've made the next inherited class in Visual Studio 2005:
|
| Public Class LabelEx
| Inherits System.Windows.Forms.Label
|
| Sub New()
| MyBase.New()
| Me.ForeColor = Color.Black
| Me.AutoSize = False
| Me.Height = 16
| End Sub
|
| <System.ComponentModel.DefaultValue(False)> _
| Public Overrides Property AutoSize() As Boolean
| Get
| Return MyBase.AutoSize
| End Get
| Set(ByVal value As Boolean)
| MyBase.AutoSize = value
| End Set
| End Property
| End Class
|
| The problem is that Autosize Property remains always as true when I go
| to design mode and put my LabelEx from the ToolBox to the form. Looking
| at the designer file, I can see as every property I have set to all my
| other extended controls is correct, except from autosize for labels...
| Any idea??? I've been unable to find this anywhere, and it looks like a
| bug, doesn't it? By the way, this code works properly in VS 2003, and
| although the default in 2003 is Autosize=false, if I put it to true, it
| works with no problem, the designer sets the value I've said...
|


Jun 16 '06 #3
Wouldn't you have to in your constructor set MyBase.AutoSize = False?

I thought the DefaultValue attribute just determines whether or not design
time code is generated when the property is the default value. When the
property is already the default value, it doesn't bother generating the line
of code, and the property value is not bold in the properties window. When
it's anything other then the default, only then does it bother generating a
line for it, and then it looks bold in the properties window so it's easier
to tell you've modified it.

"Jordi Rico" <jo*******@gmail.com> wrote in message
news:11*********************@u72g2000cwu.googlegro ups.com...
Hi, I've made the next inherited class in Visual Studio 2005:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
MyBase.AutoSize = value
End Set
End Property
End Class

The problem is that Autosize Property remains always as true when I go
to design mode and put my LabelEx from the ToolBox to the form. Looking
at the designer file, I can see as every property I have set to all my
other extended controls is correct, except from autosize for labels...
Any idea??? I've been unable to find this anywhere, and it looks like a
bug, doesn't it? By the way, this code works properly in VS 2003, and
although the default in 2003 is Autosize=false, if I put it to true, it
works with no problem, the designer sets the value I've said...

Jun 16 '06 #4
I was able to duplicated with the VS 2005 Team Suite. I also added a
msgbox in the set method to monitor the value, ie

<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
msgbox(value)
MyBase.AutoSize = value
End Set
End Property
Wether the defaultvalue is true or false, I get two windows in design
time: first one says false, second one says true.

Jordi Rico wrote:
Hi, I've made the next inherited class in Visual Studio 2005:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
MyBase.AutoSize = value
End Set
End Property
End Class

The problem is that Autosize Property remains always as true when I go
to design mode and put my LabelEx from the ToolBox to the form. Looking
at the designer file, I can see as every property I have set to all my
other extended controls is correct, except from autosize for labels...
Any idea??? I've been unable to find this anywhere, and it looks like a
bug, doesn't it? By the way, this code works properly in VS 2003, and
although the default in 2003 is Autosize=false, if I put it to true, it
works with no problem, the designer sets the value I've said...


Jun 16 '06 #5
Marina,
He has Me.AutoSize = False in his constructor. His overridden Property then
does a MyBase.AutoSize = false. Net effect is the same thing.

| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value.
Ah! There's the rub! or should I say there's the bug!

The DefaultValueAttribute determines whether or not design time code is
generated. The constructor determines the runtime code.
Well apparently in the case of Label, the new .NET 2.0 layout manager
decides to ignore both & applies AutoSize = True to the control...

A fellow MVP uses the following code as a workaround:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Private m_inited As Boolean

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

Protected Overrides Sub InitLayout()
MyBase.InitLayout()
m_inited = True
End Sub
<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
If Me.DesignMode AndAlso Not m_inited Then Return
MyBase.AutoSize = value
End Set
End Property

End Class

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Marina Levit [MVP]" <so*****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP03.phx.gbl...
| Wouldn't you have to in your constructor set MyBase.AutoSize = False?
|
| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value. When the
| property is already the default value, it doesn't bother generating the
line
| of code, and the property value is not bold in the properties window. When
| it's anything other then the default, only then does it bother generating
a
| line for it, and then it looks bold in the properties window so it's
easier
| to tell you've modified it.
|
| "Jordi Rico" <jo*******@gmail.com> wrote in message
| news:11*********************@u72g2000cwu.googlegro ups.com...
| > Hi, I've made the next inherited class in Visual Studio 2005:
| >
| > Public Class LabelEx
| > Inherits System.Windows.Forms.Label
| >
| > Sub New()
| > MyBase.New()
| > Me.ForeColor = Color.Black
| > Me.AutoSize = False
| > Me.Height = 16
| > End Sub
| >
| > <System.ComponentModel.DefaultValue(False)> _
| > Public Overrides Property AutoSize() As Boolean
| > Get
| > Return MyBase.AutoSize
| > End Get
| > Set(ByVal value As Boolean)
| > MyBase.AutoSize = value
| > End Set
| > End Property
| > End Class
| >
| > The problem is that Autosize Property remains always as true when I go
| > to design mode and put my LabelEx from the ToolBox to the form. Looking
| > at the designer file, I can see as every property I have set to all my
| > other extended controls is correct, except from autosize for labels...
| > Any idea??? I've been unable to find this anywhere, and it looks like a
| > bug, doesn't it? By the way, this code works properly in VS 2003, and
| > although the default in 2003 is Autosize=false, if I put it to true, it
| > works with no problem, the designer sets the value I've said...
| >
|
|
Jun 17 '06 #6
Thanks Jay, I'll try today and I'll tell how it works.

Jay B. Harlow [MVP - Outlook] ha escrito:
Marina,
He has Me.AutoSize = False in his constructor. His overridden Property then
does a MyBase.AutoSize = false. Net effect is the same thing.

| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value.
Ah! There's the rub! or should I say there's the bug!

The DefaultValueAttribute determines whether or not design time code is
generated. The constructor determines the runtime code.
Well apparently in the case of Label, the new .NET 2.0 layout manager
decides to ignore both & applies AutoSize = True to the control...

A fellow MVP uses the following code as a workaround:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Private m_inited As Boolean

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

Protected Overrides Sub InitLayout()
MyBase.InitLayout()
m_inited = True
End Sub
<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
If Me.DesignMode AndAlso Not m_inited Then Return
MyBase.AutoSize = value
End Set
End Property

End Class

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
.NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Marina Levit [MVP]" <so*****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP03.phx.gbl...
| Wouldn't you have to in your constructor set MyBase.AutoSize = False?
|
| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value. When the
| property is already the default value, it doesn't bother generating the
line
| of code, and the property value is not bold in the properties window. When
| it's anything other then the default, only then does it bother generating
a
| line for it, and then it looks bold in the properties window so it's
easier
| to tell you've modified it.
|
| "Jordi Rico" <jo*******@gmail.com> wrote in message
| news:11*********************@u72g2000cwu.googlegro ups.com...
| > Hi, I've made the next inherited class in Visual Studio 2005:
| >
| > Public Class LabelEx
| > Inherits System.Windows.Forms.Label
| >
| > Sub New()
| > MyBase.New()
| > Me.ForeColor = Color.Black
| > Me.AutoSize = False
| > Me.Height = 16
| > End Sub
| >
| > <System.ComponentModel.DefaultValue(False)> _
| > Public Overrides Property AutoSize() As Boolean
| > Get
| > Return MyBase.AutoSize
| > End Get
| > Set(ByVal value As Boolean)
| > MyBase.AutoSize = value
| > End Set
| > End Property
| > End Class
| >
| > The problem is that Autosize Property remains always as true when I go
| > to design mode and put my LabelEx from the ToolBox to the form. Looking
| > at the designer file, I can see as every property I have set to all my
| > other extended controls is correct, except from autosize for labels...
| > Any idea??? I've been unable to find this anywhere, and it looks like a
| > bug, doesn't it? By the way, this code works properly in VS 2003, and
| > although the default in 2003 is Autosize=false, if I put it to true, it
| > works with no problem, the designer sets the value I've said...
| >
|
|


Jun 19 '06 #7
Ok,
it works great!
Thank you very much!

Jordi Rico ha escrito:
Thanks Jay, I'll try today and I'll tell how it works.

Jay B. Harlow [MVP - Outlook] ha escrito:
Marina,
He has Me.AutoSize = False in his constructor. His overridden Property then
does a MyBase.AutoSize = false. Net effect is the same thing.

| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value.
Ah! There's the rub! or should I say there's the bug!

The DefaultValueAttribute determines whether or not design time code is
generated. The constructor determines the runtime code.
Well apparently in the case of Label, the new .NET 2.0 layout manager
decides to ignore both & applies AutoSize = True to the control...

A fellow MVP uses the following code as a workaround:

Public Class LabelEx
Inherits System.Windows.Forms.Label

Private m_inited As Boolean

Sub New()
MyBase.New()
Me.ForeColor = Color.Black
Me.AutoSize = False
Me.Height = 16
End Sub

Protected Overrides Sub InitLayout()
MyBase.InitLayout()
m_inited = True
End Sub
<System.ComponentModel.DefaultValue(False)> _
Public Overrides Property AutoSize() As Boolean
Get
Return MyBase.AutoSize
End Get
Set(ByVal value As Boolean)
If Me.DesignMode AndAlso Not m_inited Then Return
MyBase.AutoSize = value
End Set
End Property

End Class

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
.NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Marina Levit [MVP]" <so*****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP03.phx.gbl...
| Wouldn't you have to in your constructor set MyBase.AutoSize = False?
|
| I thought the DefaultValue attribute just determines whether or not design
| time code is generated when the property is the default value. When the
| property is already the default value, it doesn't bother generating the
line
| of code, and the property value is not bold in the properties window. When
| it's anything other then the default, only then does it bother generating
a
| line for it, and then it looks bold in the properties window so it's
easier
| to tell you've modified it.
|
| "Jordi Rico" <jo*******@gmail.com> wrote in message
| news:11*********************@u72g2000cwu.googlegro ups.com...
| > Hi, I've made the next inherited class in Visual Studio 2005:
| >
| > Public Class LabelEx
| > Inherits System.Windows.Forms.Label
| >
| > Sub New()
| > MyBase.New()
| > Me.ForeColor = Color.Black
| > Me.AutoSize = False
| > Me.Height = 16
| > End Sub
| >
| > <System.ComponentModel.DefaultValue(False)> _
| > Public Overrides Property AutoSize() As Boolean
| > Get
| > Return MyBase.AutoSize
| > End Get
| > Set(ByVal value As Boolean)
| > MyBase.AutoSize = value
| > End Set
| > End Property
| > End Class
| >
| > The problem is that Autosize Property remains always as true when I go
| > to design mode and put my LabelEx from the ToolBox to the form. Looking
| > at the designer file, I can see as every property I have set to all my
| > other extended controls is correct, except from autosize for labels...
| > Any idea??? I've been unable to find this anywhere, and it looks like a
| > bug, doesn't it? By the way, this code works properly in VS 2003, and
| > although the default in 2003 is Autosize=false, if I put it to true, it
| > works with no problem, the designer sets the value I've said...
| >
|
|


Jun 19 '06 #8
Thank you for following up that it worked!

--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley - http://www.tsbradley.net
"Jordi Rico" <jo*******@gmail.com> wrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...
| Ok,
| it works great!
| Thank you very much!
|
| Jordi Rico ha escrito:
|
| > Thanks Jay, I'll try today and I'll tell how it works.
| >
| > Jay B. Harlow [MVP - Outlook] ha escrito:
| >
| > > Marina,
| > > He has Me.AutoSize = False in his constructor. His overridden Property
then
| > > does a MyBase.AutoSize = false. Net effect is the same thing.
| > >
| > > | I thought the DefaultValue attribute just determines whether or not
design
| > > | time code is generated when the property is the default value.
| > > Ah! There's the rub! or should I say there's the bug!
| > >
| > > The DefaultValueAttribute determines whether or not design time code
is
| > > generated. The constructor determines the runtime code.
| > >
| > >
| > > Well apparently in the case of Label, the new .NET 2.0 layout manager
| > > decides to ignore both & applies AutoSize = True to the control...
| > >
| > > A fellow MVP uses the following code as a workaround:
| > >
| > > Public Class LabelEx
| > > Inherits System.Windows.Forms.Label
| > >
| > > Private m_inited As Boolean
| > >
| > > Sub New()
| > > MyBase.New()
| > > Me.ForeColor = Color.Black
| > > Me.AutoSize = False
| > > Me.Height = 16
| > > End Sub
| > >
| > > Protected Overrides Sub InitLayout()
| > > MyBase.InitLayout()
| > > m_inited = True
| > > End Sub
| > >
| > >
| > > <System.ComponentModel.DefaultValue(False)> _
| > > Public Overrides Property AutoSize() As Boolean
| > > Get
| > > Return MyBase.AutoSize
| > > End Get
| > > Set(ByVal value As Boolean)
| > > If Me.DesignMode AndAlso Not m_inited Then Return
| > > MyBase.AutoSize = value
| > > End Set
| > > End Property
| > >
| > > End Class
| > >
| > >
| > >
| > > --
| > > Hope this helps
| > > Jay B. Harlow [MVP - Outlook]
| > > .NET Application Architect, Enthusiast, & Evangelist
| > > T.S. Bradley - http://www.tsbradley.net
| > >
| > >
| > > "Marina Levit [MVP]" <so*****@nospam.com> wrote in message
| > > news:OH**************@TK2MSFTNGP03.phx.gbl...
| > > | Wouldn't you have to in your constructor set MyBase.AutoSize =
False?
| > > |
| > > | I thought the DefaultValue attribute just determines whether or not
design
| > > | time code is generated when the property is the default value. When
the
| > > | property is already the default value, it doesn't bother generating
the
| > > line
| > > | of code, and the property value is not bold in the properties
window. When
| > > | it's anything other then the default, only then does it bother
generating
| > > a
| > > | line for it, and then it looks bold in the properties window so it's
| > > easier
| > > | to tell you've modified it.
| > > |
| > > | "Jordi Rico" <jo*******@gmail.com> wrote in message
| > > | news:11*********************@u72g2000cwu.googlegro ups.com...
| > > | > Hi, I've made the next inherited class in Visual Studio 2005:
| > > | >
| > > | > Public Class LabelEx
| > > | > Inherits System.Windows.Forms.Label
| > > | >
| > > | > Sub New()
| > > | > MyBase.New()
| > > | > Me.ForeColor = Color.Black
| > > | > Me.AutoSize = False
| > > | > Me.Height = 16
| > > | > End Sub
| > > | >
| > > | > <System.ComponentModel.DefaultValue(False)> _
| > > | > Public Overrides Property AutoSize() As Boolean
| > > | > Get
| > > | > Return MyBase.AutoSize
| > > | > End Get
| > > | > Set(ByVal value As Boolean)
| > > | > MyBase.AutoSize = value
| > > | > End Set
| > > | > End Property
| > > | > End Class
| > > | >
| > > | > The problem is that Autosize Property remains always as true when
I go
| > > | > to design mode and put my LabelEx from the ToolBox to the form.
Looking
| > > | > at the designer file, I can see as every property I have set to
all my
| > > | > other extended controls is correct, except from autosize for
labels...
| > > | > Any idea??? I've been unable to find this anywhere, and it looks
like a
| > > | > bug, doesn't it? By the way, this code works properly in VS 2003,
and
| > > | > although the default in 2003 is Autosize=false, if I put it to
true, it
| > > | > works with no problem, the designer sets the value I've said...
| > > | >
| > > |
| > > |
|
Jun 19 '06 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
by: Harvey | last post by:
Hello: I am trying to use Autosize=true on a long string and it extends off of my form, rather than increasing the number of lines of the Label as the documentation says it should do. Would...
0
by: Tim Mulholland | last post by:
I'm writing an app in C# that requires labels to scale as the size of the window grows/shrinks. Getting the actual label itself to scale is very easy using the anchor property. But i need to get...
2
by: David Sworder | last post by:
Hi, A Windows form that I'm developing will have two controls: Label1 and Label2. Both controls are of type Label (go figure). The text of Label1 will not be known until runtime and may change...
10
by: Darrell Blake | last post by:
I'm writing an IRC client to teach myself C# and have run into a small problem. I'm using a label to display all the text and when the text gets to the bottom of the label it doesn't automatically...
1
by: Weber Samuel | last post by:
Hi NG i try to catch the Application.Idle Event: --> Application.Idle += new EventHandler(OnIdle); Here's my problem: If i put a Label on my Form and set the Property AutoSize = true then...
2
by: Oenone | last post by:
I'm trying to create a form similar to a VB messagebox but with custom content. One of the things I want to be able to do is display some text in a label at the top of the messagebox form and have...
1
by: Patrick Lioi | last post by:
Label label = new Label(); label.Width = 1; label.AutoSize = true; label.Text = "A long string, requiring a width larger than 1."; //At this point, Width is still 1. What am I missing? ...
1
by: Ryou kaihou | last post by:
As we known, in Visual Stdio 2003 or 2005, the property of Autosize of Label is set to True by defaut, how can I customize this and set property of Autosize to False? Any ideas? Thanks
11
by: Peter Larsen [] | last post by:
Hi, I have two questions related to the Label control. How do i prevent the label from expand the canvas into 2 lines (word wrap) ?? At the moment i set AutoSize to false (to prevent the word...
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
0
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.