Intellisense and colors

[Lloyd Sheen]

I am in the process of adding themes to an app. There is lots of code
dealing with colors.

VS 2008 really falls down in this area (at least at the default settings).

I have many properties of type Color. When I attempt to add the code the
property handlers (Get/Set) it does not do a very good job. Let me correct
that. I does a deplorable job.

For example:

Public Property TopColor() As Color
Get
Return _TopColor
End Get
Set(ByVal value As Color)
_TopColor = value
End Set
End Property

is the code for one of the properties. If you want to see how bad it is
place this in a class and then attempt both the Get and Set coding (first
take out the return and =values statements).

For example the return statement. There is nothing you can do to make
NonIntellesense deal with this. As you type return you will get a list of
colors (ok but....) and that is it. If I type in the _ to get the list of
variable starting with _ , what do I get???? Nothing.

Same for _TopColor =. It will give me a list of colors but I have to type
value all the way.

MS are you watching, listening. This is a terrible implementation for this.

LS

 

[Tom Shelton]

I am in the process of adding themes to an app. There is lots of code
dealing with colors.

VS 2008 really falls down in this area (at least at the default settings).

I have many properties of type Color. When I attempt to add the code the
property handlers (Get/Set) it does not do a very good job. Let me correct
that. I does a deplorable job.

For example:

Public Property TopColor() As Color
Get
Return _TopColor
End Get
Set(ByVal value As Color)
_TopColor = value
End Set
End Property

is the code for one of the properties. If you want to see how bad it is
place this in a class and then attempt both the Get and Set coding (first
take out the return and =values statements).

For example the return statement. There is nothing you can do to make
NonIntellesense deal with this. As you type return you will get a list of
colors (ok but....) and that is it. If I type in the _ to get the list of
variable starting with _ , what do I get???? Nothing.

Same for _TopColor =. It will give me a list of colors but I have to type
value all the way.

MS are you watching, listening. This is a terrible implementation for this.

LS

You make a good point. The intellisense in the VB.NET IDE is pathetic. The
C# IDE has been much better since VS2005.

private Color topColor;
public Color TopColor
{
get
{
return topColor;
}
set
{
topColor = value;
}
}

Never once puts up an intellisense box, unless I type:

topColor = C

In the set method

In C#3.0 (2008) it's even easier because of auto implemented properties:

public Color TopColor {get; set;}

That's it. No member variable, no get/set block stuff. Don't worry, you guys
get auto implemented properties in VB10. Though, from the appearance of
things, they are somewhat crippled. In C#, I can do:

public Color TopColor {get; private set;}

Basically, making the property readonly outside of the class - it doesn't look
like that is the case in VB.NET 10. I could be wrong though

 

[Armin Zingler]

I am in the process of adding themes to an app. There is lots of code
dealing with colors.

VS 2008 really falls down in this area (at least at the default
settings).
I have many properties of type Color. When I attempt to add the code
the property handlers (Get/Set) it does not do a very good job. Let
me correct that. I does a deplorable job.

For example:

Public Property TopColor() As Color
Get
Return _TopColor
End Get
Set(ByVal value As Color)
_TopColor = value
End Set
End Property

is the code for one of the properties. If you want to see how bad it
is place this in a class and then attempt both the Get and Set coding
(first take out the return and =values statements).

For example the return statement. There is nothing you can do to make
NonIntellesense deal with this. As you type return you will get a
list of colors (ok but....) and that is it. If I type in the _ to
get the list of variable starting with _ , what do I get???? Nothing.

Same for _TopColor =. It will give me a list of colors but I have to
type value all the way.

MS are you watching, listening. This is a terrible implementation
for this.

The Color type is one of the few exceptions by listing the Color.* members.
(I don't remember any other one ATM.) Not a big issue: You can always press
Ctrl+Space after typing "_". Or type "_T" and press Ctrl+Space and have it
completed immediatelly.


Armin

 

[rowe_newsgroups]

I am in the process of adding themes to an app.  There is lots of code
dealing with colors.

VS 2008 really falls down in this area (at least at the default settings)..

I have many properties of type Color.  When I attempt to add the code the
property handlers (Get/Set) it does not do a very good job.  Let me correct
that.  I does a deplorable job.

For example:

 Public Property TopColor() As Color
  Get
   Return _TopColor
  End Get
  Set(ByVal value As Color)
   _TopColor = value
  End Set
 End Property

is the code for one of the properties.  If you want to see how bad it is
place this in a class and then attempt both the Get and Set coding (first
take out the return and =values statements).

For example the return statement.  There is nothing you can do to make
NonIntellesense deal with this.  As you type return you will get a listof
colors (ok but....) and that is it.  If I type in the _ to get the listof
variable starting with _ , what do I get????  Nothing.

Same for _TopColor =.  It will give me a list of colors but I have totype
value all the way.

MS are you watching, listening.  This is a terrible implementation for this.

LS

I'm sorry for the tone of this post, but it was bound to be posted by
someone.

This newsgroup should not be used for listing your personal complaints
about Visual Studio, or the PowerPacks, or the language features etc.
No one here cares - we are not Microsoft employees (and if we are we
aren't here on their behalf). The only time you are going to get a
response from a Microsoft employee in an "official" capacity here is
if you subscribe to their service. The rest of us are volunteers
trying to help out other professionals, if you want to rant / complain
start a blog or email the product team, posting it here does little to
nothing.

If you have an actual question of Visual Basic.NET, most of us here
are happy to help. But complaining about how you actually have to type
out the name of a property prefixed with an underscore instead of
selecting it from a popup is nothing but a waste of time for everyone
involved.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

 

[Lloyd Sheen]

I am in the process of adding themes to an app. There is lots of code
dealing with colors.

VS 2008 really falls down in this area (at least at the default settings).

I have many properties of type Color. When I attempt to add the code the
property handlers (Get/Set) it does not do a very good job. Let me correct
that. I does a deplorable job.

For example:

Public Property TopColor() As Color
Get
Return _TopColor
End Get
Set(ByVal value As Color)
_TopColor = value
End Set
End Property

is the code for one of the properties. If you want to see how bad it is
place this in a class and then attempt both the Get and Set coding (first
take out the return and =values statements).

For example the return statement. There is nothing you can do to make
NonIntellesense deal with this. As you type return you will get a list of
colors (ok but....) and that is it. If I type in the _ to get the list of
variable starting with _ , what do I get???? Nothing.

Same for _TopColor =. It will give me a list of colors but I have to type
value all the way.

MS are you watching, listening. This is a terrible implementation for
this.

LS

I'm sorry for the tone of this post, but it was bound to be posted by
someone.

This newsgroup should not be used for listing your personal complaints
about Visual Studio, or the PowerPacks, or the language features etc.
No one here cares - we are not Microsoft employees (and if we are we
aren't here on their behalf). The only time you are going to get a
response from a Microsoft employee in an "official" capacity here is
if you subscribe to their service. The rest of us are volunteers
trying to help out other professionals, if you want to rant / complain
start a blog or email the product team, posting it here does little to
nothing.

If you have an actual question of Visual Basic.NET, most of us here
are happy to help. But complaining about how you actually have to type
out the name of a property prefixed with an underscore instead of
selecting it from a popup is nothing but a waste of time for everyone
involved.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/



Seth,

One of the things I was hoping (never expected to get MS involved) was
that maybe someone else had encountered the same problem and had a
workaround. Without asking (even in terms of a rant) I would not get
forward.

Perhaps the integration of VS and VB.Net make it hard for some to see
the differences. If I were using notepad and doing batch compiles then
there would be no complaint. But since I am not I feel free to complain.
When you get your own newsgroup you can police it as you want.

If this wastes your time then I would suggest another course of action,
like (don't spend time responding to questions / rants which you deem below
the level of this group).

I have gotten much info from this group and have given back. The only
posts I see as a waste of time are those which become a platform for those
in favour of one language or another.

LS
LS

 

[rowe_newsgroups]

I'm sorry for the tone of this post, but it was bound to be posted by
someone.

This newsgroup should not be used for listing your personal complaints
about Visual Studio, or the PowerPacks, or the language features etc.
No one here cares - we are not Microsoft employees (and if we are we
aren't here on their behalf). The only time you are going to get a
response from a Microsoft employee in an "official" capacity here is
if you subscribe to their service. The rest of us are volunteers
trying to help out other professionals, if you want to rant / complain
start a blog or email the product team, posting it here does little to
nothing.

If you have an actual question of Visual Basic.NET, most of us here
are happy to help. But complaining about how you actually have to type
out the name of a property prefixed with an underscore instead of
selecting it from a popup is nothing but a waste of time for everyone
involved.

Thanks,

Seth Rowe [MVP]http://sethrowe.blogspot.com/

Seth,

    One of the things I was hoping (never expected to get MS involved) was
that maybe someone else had encountered the same problem and had a
workaround.  Without asking (even in terms of a rant) I would not get
forward.

    Perhaps the integration of VS and VB.Net make it hard for some tosee
the differences.  If I were using notepad and doing batch compiles then
there would be no complaint.  But since I am not I feel free to complain.
When you get your own newsgroup you can police it as you want.

    If this wastes your time then I would suggest another course of action,
like (don't spend time responding to questions / rants which you deem below
the level of this group).

    I have gotten much info from this group and have given back. The only
posts I see as a waste of time are those which become a platform for those
in favour of one language or another.

LS
LS

The issue is that before one can determine if a message has an
answerable question, they must read the post. In your first post about
the Datarepeater (titled "A Plea for MS - please someday issue
meaningful error messages") there was nothing to be found that could
be answered, the second post on the topic I gave all the advice I
could think of at the time. In both cases I had a lot of rant to go
through before finding something answerable.

The simplest solution would be to just throw something in the subject
that marks non-question or discussion posts as such, that way those
who want to get involved can, and grumpy folks like me can stay away,
or join the topic with a different attitude.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/