Creating an "invisible" user control

[Scott McNair]

Hi,

I'm creating a user control that has absolutely no visual pieces to it...
it's essentially a piece that sniffs a serial port awaiting incoming data.
I know that there are several controls that come natively with .NET that
don't actually reside on the form, but go to the bottom area, such as for
example database-related controls. How would I go about setting my own
control to do just that? Otherwise I'm left with the quandary of either
having the control be lost on the form (since there's no visual clues) or
having to put a graphic on it and then mark it as not visible.

Cheers,
Scott

[rowe_newsgroups]

On Jan 9, 4:06 pm, Scott McNair
<[e-mail]:

Hi,

I'm creating a user control that has absolutely no visual pieces to it...
it's essentially a piece that sniffs a serial port awaiting incoming data.
I know that there are several controls that come natively with .NET that
don't actually reside on the form, but go to the bottom area, such as for
example database-related controls. How would I go about setting my own
control to do just that? Otherwise I'm left with the quandary of either
having the control be lost on the form (since there's no visual clues) or
having to put a graphic on it and then mark it as not visible.

Cheers,
Scott

I believe you need to just create a Component, they reside in the bar
at the bottom of the form designer.

Thanks,

Seth Rowe [MVP]

[Lloyd Sheen]

"Scott McNair" <sm*****@beachexpress.takethispartout.comwrote in message
news:Xn**********************************@207.46.2 48.16...

Hi,

I'm creating a user control that has absolutely no visual pieces to it...
it's essentially a piece that sniffs a serial port awaiting incoming data.
I know that there are several controls that come natively with .NET that
don't actually reside on the form, but go to the bottom area, such as for
example database-related controls. How would I go about setting my own
control to do just that? Otherwise I'm left with the quandary of either
having the control be lost on the form (since there's no visual clues) or
having to put a graphic on it and then mark it as not visible.

Cheers,
Scott

Scott,
Since the "control" has no visible piece why is it a control? I think
you can think of a control as a class which in most cases is visible. You
can create the class for you work and then simply have it as a variable
within the form it is used in. If you are doing this to capture events you
can still capture events using AddHandler or the WithEvents keyword in the
declaration of the variable.

Hope this helps
Lloyd Sheen

[Jack Jackson]

On Wed, 09 Jan 2008 13:06:00 -0800, Scott McNair
<sm*****@beachexpress.takethispartout.comwrote:

>Hi,

I'm creating a user control that has absolutely no visual pieces to it...
it's essentially a piece that sniffs a serial port awaiting incoming data.
I know that there are several controls that come natively with .NET that
don't actually reside on the form, but go to the bottom area, such as for
example database-related controls. How would I go about setting my own
control to do just that? Otherwise I'm left with the quandary of either
having the control be lost on the form (since there's no visual clues) or
having to put a graphic on it and then mark it as not visible.

Cheers,
Scott

A class derived from Component resides below the visual area in the
designer.

If you don't need to set properties at design time, why not just make
it be a plain class that is instantiated at runtime?

[Herfried K. Wagner [MVP]]

"Scott McNair" <sm*****@beachexpress.takethispartout.comschrieb :

I'm creating a user control that has absolutely no visual pieces to it...
it's essentially a piece that sniffs a serial port awaiting incoming data.
I know that there are several controls that come natively with .NET that
don't actually reside on the form, but go to the bottom area

"Project" -"Add new item..." -"Component" (translated from the German
version of VS 2005).

Components, which reside in the components tray of the Windows Forms editor,
are classes which are derived from 'System.ComponentModel.Component'.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>