473,545 Members | 2,543 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

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.Compone ntModel.Default Value(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 3403
Jordi,
I noticed that the other day, it feels like a bug to me, as VS is "breaking"
the contract that System.Componen tModel.DefaultV alue 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*******@gmai l.com> wrote in message
news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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.Componen tModel.DefaultV alue 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*******@gmai l.com> wrote in message
news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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*******@gmai l.com> wrote in message
news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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.Compone ntModel.Default Value(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.Compone ntModel.Default Value(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 DefaultValueAtt ribute 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.InitLayo ut()
m_inited = True
End Sub
<System.Compone ntModel.Default Value(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******** ******@TK2MSFTN GP03.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*******@gmai l.com> wrote in message
| news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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 DefaultValueAtt ribute 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.InitLayo ut()
m_inited = True
End Sub
<System.Compone ntModel.Default Value(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******** ******@TK2MSFTN GP03.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*******@gmai l.com> wrote in message
| news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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 DefaultValueAtt ribute 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.InitLayo ut()
m_inited = True
End Sub
<System.Compone ntModel.Default Value(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******** ******@TK2MSFTN GP03.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*******@gmai l.com> wrote in message
| news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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*******@gmai l.com> wrote in message
news:11******** **************@ p79g2000cwp.goo glegroups.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 DefaultValueAtt ribute 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.InitLayo ut()
| > > m_inited = True
| > > End Sub
| > >
| > >
| > > <System.Compone ntModel.Default Value(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******** ******@TK2MSFTN GP03.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*******@gmai l.com> wrote in message
| > > | news:11******** *************@u 72g2000cwu.goog legroups.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.Compone ntModel.Default Value(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
2023
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 anyone know what other property I need to set to get this to work properly? I have looked through them all and cant find any. PreferredHeight is...
0
3643
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 the text inside the label to change fontsize based on the size of the label. I know it is possible (with the autosize property) to have the label...
2
2073
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 at times. When the MyText property of the containing form is set, I want to: a) Set the Label1.Text property appropriately. b) Change the width of...
10
27572
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 scroll down so you can't see the new messages. I want to do one of two things if possible. Either get the label to automatically scroll down or add...
1
1938
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 the Eventhandler OnIdle never occurs! If the Property AutoSize is set to false the OnIdle - Handler will be called...
2
2149
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 the form automatically expand to make room for it (which could be just a few words, or several paragraphs). In VB6 I used to use a useful trick...
1
12226
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? Shouldn't AutoSize adjust the "Size" "Auto"matically to fit the string?
1
1857
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
11472
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 wrap from happening) and Anchor to Left, Right (to enable the with autosize). How do i prevent a tool-tip from happening if the text is to large...
0
7464
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, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
0
7396
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 effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
7656
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
7805
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 tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
1
7413
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 Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
1
5323
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
4943
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
0
3449
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in...
0
3440
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?

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.