Bug in notepad and multiline edit box


X

Xlnt

The first bug I would like to mention affects the select all functionality
in notepad. Once used the functionality is disabled. After making any
changes to the selection it should be enabled. However this isn't done when
changing the selection while keeping the length greater then zero.

The following steps should be enough to reproduce the error.
- Open notepad and make sure there is some text in it. Two characters should
be enough.
- Select all by using the menu or the shortcut key.
- Adjust the selection but make sure at least one character is selected.

After trying to select all by using the menu or the shortcut key again, you
will notice this isn't possible anymore. You can enable the functionality
again by removing the selection and then accessing the menu in any way or
pressing Ctrl+A. 'Removing the selection' means 'selecting nothing' or
'setting the selection length to zero'. Note that the latter option brings
you back in the disabled state. However, it works for one time.

The second bugs affects multiline edit boxes in general in multiple versions
of Windows. Is doesn't affect rich edit boxes. Whenever you double-click
below the last line in the box, the line is selected and the cursor placed
at its and. When this last line is empty and the box contains at least two
lines, the cursor is instead placed at the the beginning of the first line.
Note that 'at least two lines' means 'at least one sequence of \r\n', \r\n
being a cariage return and a new line character. This results in results in
unexpected behavior when typing a character when not changing the cursor
position.

The following steps should be enough to reproduce the error.
- Open an application with a multiline edit box, for example notepad. Make
sure there are at least two lines in the box and the last line is empty. One
character followed by a carriage return and a new line character should be
enough.
- Double-click below the last line in the box.

After typing a character you will notice blocks are showing up at the
beginning of lines. These actually are \r\n sequences being displayed as
characters. The display is restored as should after changing the text after
not having executed the mentioned steps. This bug exists already in Windows
95, so it's there for quite a few years!

This last report would be more appropriate in
microsoft.public.windows.general. That newsgroup however does not exist,
CMIIW. Could someone confirm these features to be bugs? If really bugs
should I inform Microsoft about them? Or isn't that necessary as this is a
Microsoft newsgroup?

Frank
 
Ad

Advertisements

R

Richard Urban

I just tried what you say. I do not have the same experience. For it to be a
bug, "all" systems must be affected. Otherwise, it's a local
machine/software condition!

--
Regards:

Richard Urban

aka Crusty (-: Old [email protected] :)
 
X

Xlnt

Richard Urban said:
I just tried what you say. I do not have the same experience. For it to be
a bug, "all" systems must be affected. Otherwise, it's a local
machine/software condition!

Are you talking about the multiline edit box bug? I recently heard more guys
are experiencing the same behavior. Are you sure you followed the steps
exactly? Especially, note that it doesn't work in a rich edit box like in
Outlook Express or Internet Explorer. Which operating system do you use?

Frank
 
N

Nico Tomacelli [MSFT]

Hi Xlnt,

Thank you for reporting the issues. Both issues have had bugs filed for
them. We were able to reproduce both issues internally. Keep in mind there
is some configuration issue that is related as this does not repro in all
environments.

Thanks again for reporting this.

Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=====================================================
 
Ad

Advertisements

X

Xlnt

Nico Tomacelli said:
Hi Xlnt,

Thank you for reporting the issues. Both issues have had bugs filed for
them. We were able to reproduce both issues internally. Keep in mind
there is some configuration issue that is related as this does not repro
in all environments.

You are welcome. Thank you for confirming the bugs.

Xlnt
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top