Cursor Position After AutoComplete

Just a question regarding the cursor jumping to beginning of line when
pressing Enter after AutoComplete.

In another post, this reply is given:
=================================================
This is a well-known issue which (as guys from JetBrains say) is hardly
possible to fix. The possible workaround is to open the code beforeopening
the designer. Here is also a reference which may be useful:
http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
=================================================

Are you saying you can't fix this? You say its hardly possible to fix, yet
none of your competitors have this glitch. This is a major problem for me
as I can only use one hand to type due to a disability, and it really slows
me down to have to switch to the tab key to complete something.

You say to open the code first, but this does not seem to work consistently.
Also, if I leave forms/code open and VS reopens them, the bug manifests
itself.

Is there really nothing you can do about this?

Thanks,
John Campion



7 comments
Comment actions Permalink

Are you saying you can't fix this? You say its hardly possible to fix,
yet none of your competitors have this glitch.


Which competitors do you mean? I mean competitors that replace VS intellisense list if their own.


Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Just a question regarding the cursor jumping to beginning of line when
pressing Enter after AutoComplete.

In another post, this reply is given:
=================================================
This is a well-known issue which (as guys from JetBrains say) is
hardly
possible to fix. The possible workaround is to open the code
beforeopening
the designer. Here is also a reference which may be useful:
http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
=================================================
Are you saying you can't fix this? You say its hardly possible to fix,
yet none of your competitors have this glitch. This is a major
problem for me as I can only use one hand to type due to a disability,
and it really slows me down to have to switch to the tab key to
complete something.

You say to open the code first, but this does not seem to work
consistently. Also, if I leave forms/code open and VS reopens them,
the bug manifests itself.

Is there really nothing you can do about this?

Thanks,
John Campion


0
Comment actions Permalink

Hello John,

I can only promise that we'll try to find the source of this problem and fix it again. We already tried it several times before but
to no effect. The problem seems to root deeply in the event dispatching mechanisms inside VS.NET, and it's difficult for us
to find its reason, as we have no enough information about VS internals. But I realize that this does not matter for end-users
suffering from this issue, I'm just trying to find an excuse for the fact it has not been fixed yet.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Just a question regarding the cursor jumping to beginning of line when
pressing Enter after AutoComplete.

In another post, this reply is given:
=================================================
This is a well-known issue which (as guys from JetBrains say) is
hardly
possible to fix. The possible workaround is to open the code
beforeopening
the designer. Here is also a reference which may be useful:
http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
=================================================
Are you saying you can't fix this? You say its hardly possible to fix,
yet none of your competitors have this glitch. This is a major
problem for me as I can only use one hand to type due to a disability,
and it really slows me down to have to switch to the tab key to
complete something.

You say to open the code first, but this does not seem to work
consistently. Also, if I leave forms/code open and VS reopens them,
the bug manifests itself.

Is there really nothing you can do about this?

Thanks,
John Campion


0
Comment actions Permalink

I'm looking at switching from VisualAssist, and it nor CodeRush doesn't have
any such problem.

I really like your product, don't get me wrong. I actually want to buy it,
but this issue is stopping me from doing so. I just thought I'd ask again
before I give up...

John

"Valentin Kipiatkov (JetBrains)" <valentin@jetbrains.com> wrote in message
news:ck5qp4$nlf$1@is.intellij.net...
>> Are you saying you can't fix this? You say its hardly possible to fix,
>> yet none of your competitors have this glitch.
>

Which competitors do you mean? I mean competitors that replace VS
intellisense list if their own.

>
>

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Just a question regarding the cursor jumping to beginning of line when
>> pressing Enter after AutoComplete.
>>
>> In another post, this reply is given:
>> =================================================
>> This is a well-known issue which (as guys from JetBrains say) is
>> hardly
>> possible to fix. The possible workaround is to open the code
>> beforeopening
>> the designer. Here is also a reference which may be useful:
>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
>> =================================================
>> Are you saying you can't fix this? You say its hardly possible to fix,
>> yet none of your competitors have this glitch. This is a major
>> problem for me as I can only use one hand to type due to a disability,
>> and it really slows me down to have to switch to the tab key to
>> complete something.
>>
>> You say to open the code first, but this does not seem to work
>> consistently. Also, if I leave forms/code open and VS reopens them,
>> the bug manifests itself.
>>
>> Is there really nothing you can do about this?
>>
>> Thanks,
>> John Campion



0
Comment actions Permalink

Hi John,

Good news is that it looks like we've managed to address this annoying issue in the upcoming build 113 (which has not been published yet).
If the fix will not cause any regression, we'll make it available thru EAP builds & bugfix updates.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello John,

I can only promise that we'll try to find the source of this problem
and fix it again. We already tried it several times before but

to no effect. The problem seems to root deeply in the event
dispatching mechanisms inside VS.NET, and it's difficult for us

to find its reason, as we have no enough information about VS
internals. But I realize that this does not matter for end-users

suffering from this issue, I'm just trying to find an excuse for the
fact it has not been fixed yet.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Just a question regarding the cursor jumping to beginning of line
>> when pressing Enter after AutoComplete.
>>
>> In another post, this reply is given:
>> =================================================
>> This is a well-known issue which (as guys from JetBrains say) is
>> hardly
>> possible to fix. The possible workaround is to open the code
>> beforeopening
>> the designer. Here is also a reference which may be useful:
>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
>> =================================================
>> Are you saying you can't fix this? You say its hardly possible to
>> fix,
>> yet none of your competitors have this glitch. This is a major
>> problem for me as I can only use one hand to type due to a
>> disability,
>> and it really slows me down to have to switch to the tab key to
>> complete something.
>> You say to open the code first, but this does not seem to work
>> consistently. Also, if I leave forms/code open and VS reopens them,
>> the bug manifests itself.
>>
>> Is there really nothing you can do about this?
>>
>> Thanks,
>> John Campion

0
Comment actions Permalink

That is good news! I look forward to trying it out...

Thanks,
John

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:ckdcja$vfa$1@is.intellij.net...

Hi John,

>

Good news is that it looks like we've managed to address this annoying
issue in the upcoming build 113 (which has not been published yet).
If the fix will not cause any regression, we'll make it available thru EAP
builds & bugfix updates.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>
>> Hello John,
>>
>> I can only promise that we'll try to find the source of this problem
>> and fix it again. We already tried it several times before but
>>
>> to no effect. The problem seems to root deeply in the event
>> dispatching mechanisms inside VS.NET, and it's difficult for us
>>
>> to find its reason, as we have no enough information about VS
>> internals. But I realize that this does not matter for end-users
>>
>> suffering from this issue, I'm just trying to find an excuse for the
>> fact it has not been fixed yet.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Just a question regarding the cursor jumping to beginning of line
>>> when pressing Enter after AutoComplete.
>>>
>>> In another post, this reply is given:
>>> =================================================
>>> This is a well-known issue which (as guys from JetBrains say) is
>>> hardly
>>> possible to fix. The possible workaround is to open the code
>>> beforeopening
>>> the designer. Here is also a reference which may be useful:
>>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
>>> =================================================
>>> Are you saying you can't fix this? You say its hardly possible to
>>> fix,
>>> yet none of your competitors have this glitch. This is a major
>>> problem for me as I can only use one hand to type due to a
>>> disability,
>>> and it really slows me down to have to switch to the tab key to
>>> complete something.
>>> You say to open the code first, but this does not seem to work
>>> consistently. Also, if I leave forms/code open and VS reopens them,
>>> the bug manifests itself.
>>>
>>> Is there really nothing you can do about this?
>>>
>>> Thanks,
>>> John Campion



0
Comment actions Permalink

Excellent! Congratulations and Kudos! (and my fingers are crossed that
everything goes well!)

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:ckdcja$vfa$1@is.intellij.net...

Hi John,

>

Good news is that it looks like we've managed to address this annoying

issue in the upcoming build 113 (which has not been published yet).

If the fix will not cause any regression, we'll make it available thru EAP

builds & bugfix updates.
>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>

Hello John,

>

I can only promise that we'll try to find the source of this problem
and fix it again. We already tried it several times before but

>

to no effect. The problem seems to root deeply in the event
dispatching mechanisms inside VS.NET, and it's difficult for us

>

to find its reason, as we have no enough information about VS
internals. But I realize that this does not matter for end-users

>

suffering from this issue, I'm just trying to find an excuse for the
fact it has not been fixed yet.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Just a question regarding the cursor jumping to beginning of line
>> when pressing Enter after AutoComplete.
>>
>> In another post, this reply is given:
>> =================================================
>> This is a well-known issue which (as guys from JetBrains say) is
>> hardly
>> possible to fix. The possible workaround is to open the code
>> beforeopening
>> the designer. Here is also a reference which may be useful:
>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
>> =================================================
>> Are you saying you can't fix this? You say its hardly possible to
>> fix,
>> yet none of your competitors have this glitch. This is a major
>> problem for me as I can only use one hand to type due to a
>> disability,
>> and it really slows me down to have to switch to the tab key to
>> complete something.
>> You say to open the code first, but this does not seem to work
>> consistently. Also, if I leave forms/code open and VS reopens them,
>> the bug manifests itself.
>>
>> Is there really nothing you can do about this?
>>
>> Thanks,
>> John Campion

>


0
Comment actions Permalink

Just wanted to confirm that it is fixed. Thanks and congratulations on
finding it!

I'll be registering shortly...

John

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:ckdcja$vfa$1@is.intellij.net...

Hi John,

>

Good news is that it looks like we've managed to address this annoying
issue in the upcoming build 113 (which has not been published yet).
If the fix will not cause any regression, we'll make it available thru EAP
builds & bugfix updates.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>
>> Hello John,
>>
>> I can only promise that we'll try to find the source of this problem
>> and fix it again. We already tried it several times before but
>>
>> to no effect. The problem seems to root deeply in the event
>> dispatching mechanisms inside VS.NET, and it's difficult for us
>>
>> to find its reason, as we have no enough information about VS
>> internals. But I realize that this does not matter for end-users
>>
>> suffering from this issue, I'm just trying to find an excuse for the
>> fact it has not been fixed yet.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Just a question regarding the cursor jumping to beginning of line
>>> when pressing Enter after AutoComplete.
>>>
>>> In another post, this reply is given:
>>> =================================================
>>> This is a well-known issue which (as guys from JetBrains say) is
>>> hardly
>>> possible to fix. The possible workaround is to open the code
>>> beforeopening
>>> the designer. Here is also a reference which may be useful:
>>> http://www.intellij.net/tracker/resharper/viewSCR?publicId=1601
>>> =================================================
>>> Are you saying you can't fix this? You say its hardly possible to
>>> fix,
>>> yet none of your competitors have this glitch. This is a major
>>> problem for me as I can only use one hand to type due to a
>>> disability,
>>> and it really slows me down to have to switch to the tab key to
>>> complete something.
>>> You say to open the code first, but this does not seem to work
>>> consistently. Also, if I leave forms/code open and VS reopens them,
>>> the bug manifests itself.
>>>
>>> Is there really nothing you can do about this?
>>>
>>> Thanks,
>>> John Campion



0

Please sign in to leave a comment.