Instead of Ctrl+Y redoing what's stored in 'future history', it
REPLACES that information (which will then be forever lost) with a new
command: delete current line. This shortcut is so ridiculous I
actually contemplated that I must have accidentally changed it to this
myself, but I don't see how that could have possibly happened.

Where can I / should I report this?

It doesn't exist in Visual C# .NET, so it's not generic to VS .NET.

Zytan

Maybe you can use your Passport login & login to http://beta.microsoft.com &
report it there

If that is wrong then maybe the beta group with let you know the correct
site.

Not sure where else to suggest.

--
Newbie Coder
(It's just a name)

Zytan wrote:
> Instead of Ctrl+Y redoing what's stored in 'future history', it
> REPLACES that information (which will then be forever lost) with a new
> command: delete current line. This shortcut is so ridiculous I
> actually contemplated that I must have accidentally changed it to this
> myself, but I don't see how that could have possibly happened.
>
> Where can I / should I report this?

If you've configured the IDE to use the Visual Basic 6 keys (in
Tools/Options/Environment/Keyboard) then it's picking up the standard
behaviour of Ctrl+Y from VB6, which is indeed "delete line." Ctrl+Y is
commonly used in a number of application to mean "Delete Line", usually with
Ctrl+Shift+Z as Redo.

(FWIW, I agree, I use Ctrl+Y as Redo as well and hate the fact that by
default it deletes lines in VB).

It's only a few seconds' work to remap the shortcut to Redo.

I strongly suspect that if you reported this to Microsoft as a bug, they
would just tell you that it is "by design," which, really, it is.

--

(O)enone

> Maybe you can use your Passport login & login tohttp://beta.microsoft.com&
> report it there

Going through that is like trekking through a muddy marsh at night
time. I wish they could just make it easier. I have about 50 things
to report. They pop up every 5 seconds, it seems. Is it possible to
report bugs just to the newsgroup, and have Microsofties deal with it
themselves?

Thanks for the suggestion.

Zytan

Oenone,

> If you've configured the IDE to use the Visual Basic 6 keys (in
> Tools/Options/Environment/Keyboard) then it's picking up the standard
> behaviour of Ctrl+Y from VB6, which is indeed "delete line." Ctrl+Y is
> commonly used in a number of application to mean "Delete Line", usually with
> Ctrl+Shift+Z as Redo.

Actually, VB 2005 Express doesn't have any such option. I am
surprised. All it has is (Default).

This is the first app that I've seen use Ctrl+Y as delete line. But I
understand that, just by looking at the keyboard shortcut changes from
version to version in VS that it's all pretty much up for grabs. They
just set them to whatever. Cut 'n Paste and F1 are about the only
things that are guaranteed to work. Even F2 doesn't work -- dammit.
It's enough to drive someone insane.


> (FWIW, I agree, I use Ctrl+Y as Redo as well and hate the fact that by
> default it deletes lines in VB).
>
> It's only a few seconds' work to remap the shortcut to Redo.

Yup, already done. I just hate this, since what happens on the next
machine with VB on it... they are all different. Keyboard mapping is
soooo important, and it's just an afterthought for the designers.


> I strongly suspect that if you reported this to Microsoft as a bug, they
> would just tell you that it is "by design," which, really, it is.

Yeah, that's what I'm afraid of. It should be a bug. UI issues are
bugs. The ignorance on this issue is very frustrating.

Zytan

On Feb 2, 12:21 pm, "Zytan" <zytanlith...@yahoo.com> wrote:
> Oenone,
>
> > If you've configured the IDE to use the Visual Basic 6 keys (in
> > Tools/Options/Environment/Keyboard) then it's picking up the standard
> > behaviour of Ctrl+Y from VB6, which is indeed "delete line." Ctrl+Y is
> > commonly used in a number of application to mean "Delete Line", usually with
> > Ctrl+Shift+Z as Redo.
>
> Actually, VB 2005 Express doesn't have any such option. I am
> surprised. All it has is (Default).
>
> This is the first app that I've seen use Ctrl+Y as delete line. But I
> understand that, just by looking at the keyboard shortcut changes from
> version to version in VS that it's all pretty much up for grabs. They
> just set them to whatever. Cut 'n Paste and F1 are about the only
> things that are guaranteed to work. Even F2 doesn't work -- dammit.
> It's enough to drive someone insane.
>
> > (FWIW, I agree, I use Ctrl+Y as Redo as well and hate the fact that by
> > default it deletes lines in VB).
>
> > It's only a few seconds' work to remap the shortcut to Redo.
>
> Yup, already done. I just hate this, since what happens on the next
> machine with VB on it... they are all different. Keyboard mapping is
> soooo important, and it's just an afterthought for the designers.
>
> > I strongly suspect that if you reported this to Microsoft as a bug, they
> > would just tell you that it is "by design," which, really, it is.
>
> Yeah, that's what I'm afraid of. It should be a bug. UI issues are
> bugs. The ignorance on this issue is very frustrating.
>
> Zytan

One could argue that it's not a bug. CTRL-Y has stood for Delete Line
since the IDE's available in DOS! One could argue that changing to
Redo is the bug!

Zytan wrote:
> Actually, VB 2005 Express doesn't have any such option. I am
> surprised. All it has is (Default).

Ah, not used Express so I can't comment on that.

> This is the first app that I've seen use Ctrl+Y as delete line.

There are lots of others:

http://www.google.com/search?hl=en&q...=Google+Search

>> It's only a few seconds' work to remap the shortcut to Redo.
>
> Yup, already done. I just hate this, since what happens on the next
> machine with VB on it... they are all different. Keyboard mapping is
> soooo important, and it's just an afterthought for the designers.

Actually I disagree -- again, can't comment on the Express version, but I
was very impressed with the level of compatibility VS2005's Visual Basic 6
mode had with the real VB6, all the bizarre undocumented (as far as I know)
shortcuts all worked perfectly.

The fact that they went as far as to provide eight different built-in key
mapping schemes makes me think this was far from an afterthought. Again,
this may be different in Express.

Can you import and export your configuration in Express? I recently had to
reinstall XP and lost all my VS2005 settings, but I just imported the
settings I had saved when I configured everything how I wanted before and
they all came straight back. I was very pleased with that.

> Yeah, that's what I'm afraid of. It should be a bug. UI issues are
> bugs. The ignorance on this issue is very frustrating.

I don't think there's any ignorance, not a bug, just a difference of
opinion.

--

(O)enone

Microsoft only responds to posts in the managed newsgroups for people with
MSDN support. They don't read it to pick up comments about their products,
or bugs therein.

Don't forget your mosquito spray. ;-)

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
"Zytan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> Maybe you can use your Passport login & login
>> tohttp://beta.microsoft.com&
>> report it there
>
> Going through that is like trekking through a muddy marsh at night
> time. I wish they could just make it easier. I have about 50 things
> to report. They pop up every 5 seconds, it seems. Is it possible to
> report bugs just to the newsgroup, and have Microsofties deal with it
> themselves?
>
> Thanks for the suggestion.
>
> Zytan
>

On Feb 2, 1:21 pm, "Zytan" <zytanlith...@yahoo.com> wrote:
> Oenone,
>
> > If you've configured the IDE to use the Visual Basic 6 keys (in
> > Tools/Options/Environment/Keyboard) then it's picking up the standard
> > behaviour of Ctrl+Y from VB6, which is indeed "delete line." Ctrl+Y is
> > commonly used in a number of application to mean "Delete Line", usually with
> > Ctrl+Shift+Z as Redo.
>
> Actually, VB 2005 Express doesn't have any such option. I am
> surprised. All it has is (Default).
>
> This is the first app that I've seen use Ctrl+Y as delete line. But I
> understand that, just by looking at the keyboard shortcut changes from
> version to version in VS that it's all pretty much up for grabs. They
> just set them to whatever. Cut 'n Paste and F1 are about the only
> things that are guaranteed to work. Even F2 doesn't work -- dammit.
> It's enough to drive someone insane.
>
> > (FWIW, I agree, I use Ctrl+Y as Redo as well and hate the fact that by
> > default it deletes lines in VB).
>
> > It's only a few seconds' work to remap the shortcut to Redo.
>
> Yup, already done. I just hate this, since what happens on the next
> machine with VB on it... they are all different. Keyboard mapping is
> soooo important, and it's just an afterthought for the designers.
>
> > I strongly suspect that if you reported this to Microsoft as a bug, they
> > would just tell you that it is "by design," which, really, it is.
>
> Yeah, that's what I'm afraid of. It should be a bug. UI issues are
> bugs. The ignorance on this issue is very frustrating.
>
> Zytan

I'm not trying to start a flame war here, but my goodness you complain
a lot! Visual Basic .Net is not C++ and the VB 2005 ide is not the ide
you are used to using, so either adjust to the new language/ide (or
adjust it to you) or go back to what you used to use! Besides, you do
realize you are complaining about a feature in a program (vb 2005
express edition) that was free right?

And to prevent too many people from yelling at me for ranting, I'll
apologize here for being a bit of a jerk - it's been a long week :-)

Thanks,

Seth Rowe

> One could argue that it's not a bug. CTRL-Y has stood for Delete Line
> since the IDE's available in DOS! One could argue that changing to
> Redo is the bug!

Chris, you are exactly right. If they didn't mess up the first time,
then I wouldn't be here complaining that it was changed back. So,
it's the same problem, really. You can't say which is better. It's
just whatever we are used to. But, if someday, everyone decided to
use a standard, and we all switched to it (like we did when Ctrl+C and
Ctrl+V were introduced), then after a bit of grumbling by us oldies,
we'd all be much happier. The way to make us upset, though, is to
have no standard whatsoever within the same company, for the same
product, for different versions only 2 years apart.

People are just ignorant towards how important UI issues are.
Pressing a key combo and having the thing not do its expected job
means it is broken. Maybe not AS broken as if the feature didn't
exist, but it's still broken.

Zytan