Annoying Behaviour in Notepad (Bug?)

[Raziel]

Hello all,

I encountered an annyoing behaviour in Notepad's search window.
I know of this actually for a long time, but only recently figured that it was not me, but the search window playing tricks on me.

Once you did an unsuccesfull search, the top bar of the search window will change to '"blahblah" not found'.
Now, if you type in a new search and type something very long.
In the meantime of typing the top bar result will change back to "Search", kicking you out of the search field...which is, to say at least, impudent
On a larger scale it's flat annoying...can something be done about it, please?

Steps to reproduce:

1) Load in a text file
2) Click on "Search" and enter "something" in the search field. It's important that it does not find it
3) Be sure to also set "From top", as if it seems that with this checkmark set, it always happens
4) When the top bar of the Search window has changed to '"something" not found', click again in the search field and start typing
5) Keep typing while you wait for the Search window's top bar to change back to "Search" and see getting kicked out of the search field or even some different behaviours (see below)

The behaviours i've witnessed so far:
1) It kicks you out of the search field (cursor gone) and never lets you type along until you click into the search field again (very often)
2) It stalls your input for a moment (2-3 seconds), then goes on processing your input, but with lots characters (the ones you typed while it stalled) (very seldom)
3) It keeps on processing your inputs without stalling and working fine (very seldom) - actually this kind of behaviour can be prevented completely by setting the "From top" checkmark

[xenic]

@Raziel
I tried at least 10 times and was unable to reproduce the problem. I don't use Notepad much so the Tooltypes are all disabled in the icon. Unless my X1000 is doing something faster that prevents the problem, I can't explain why I can't reproduce your the problem you describe. Maybe someone else can reproduce it.

[Raziel]

@Raziel
I tried at least 10 times and was unable to reproduce the problem. I don't use Notepad much so the Tooltypes are all disabled in the icon. Unless my X1000 is doing something faster that prevents the problem, I can't explain why I can't reproduce your the problem you describe. Maybe someone else can reproduce it.

I don't have any tooltypes used either.

maybe a mor easy way to reproduce it will help?

1) Open Notepad
2) Type something, anything and spread through some lines
3) Click on "Find" (yes i meant the find button in my original post, sorry)
4) Type something in the search field and click search
5) If it's not found the top bar will change to "blahblah" not found and immediately after that, the search field entry will get marked
6) Now start typing and don't stop, simply type the same char and watch the screen
7) As soon as the top bar information changes back to display "Find" it throws me out (it even managed to close the find window and throw me back into the Notepad main window)

That is clearly a bug, it wasn't supposed to close the find window, i never told it to do so

[xenic]

@Raziel
I wish I could help but I still can't reproduce the problem. The only thing I can say is that for the past several months clicking on some things once or hitting <Enter> once doesn't do anything and I have to click or hit <Return> a second time. That's mostly in Odyssey so I don't know the root cause.

I will suggest is that you reboot, enter the early startup screen and run without a startup-sequence to rule out interference from another program. I was actually surprised that Notepad runs without a startup-sequence. However, if I reboot and run without startup-sequence and enter "SYS:Utilities/Notepad" in the shell window, Notepad opens and appears to work normally.

It would be helpful if others would attempt to reproduce your Notepad problem and report the results.

[chris]

I'm not sure if it's related, but I always get a problem where the find string gadget gets deactivated in the middle of typing, and I end up toggling the checkboxes in the find window as I hit keys and haven't noticed.

[tbreeden]

It would be helpful if others would attempt to reproduce your Notepad problem and report the results.

I'm not able to all of the reported behaviours, but can reproduce one that maybe points towards something
with the search code that is not being totally initialized.

Try: 1. Start up NotePad (click on the NotePad Icon).
2. Open any text file (NotePad toolbar button "Open")
3. Click on NotePad toolbar "Find".
The Search requester will open with an empty, but activated textbox.
4. Type in a search pattern text that will fail (don't click the mouse)
5. Hit the Enter key to start the search (don't click on the "Find Next" button).
6. The search will fail, as described above and the search requester
textbox is still active, with the search pattern text selected.

The above steps are the only way I can make a failed search return with the
search pattern text selected.

And it only happens on the first popup of the search requester. All other times
a failed search returns with nothing selected in the pattern box and the
active cursor at the end of the search text that failed.

If you close the search requester and reopen it, or even left click the mouse
once in the search requester text box before searching you never get that
behaviour again.

This is AOS 4.1 upd 6, texteditor.gadget 53.19, NotePad 53.10
AmigaOne X1000.

Tom

[Raziel]

I'm not sure if it's related, but I always get a problem where the find string gadget gets deactivated in the middle of typing, and I end up toggling the checkboxes in the find window as I hit keys and haven't noticed.

Thats the behaviour i'm getting, thanks for rephrasing

[Raziel]

It would be helpful if others would attempt to reproduce your Notepad problem and report the results.

I'm not able to all of the reported behaviours, but can reproduce one that maybe points towards something
with the search code that is not being totally initialized.

Try: 1. Start up NotePad (click on the NotePad Icon).
2. Open any text file (NotePad toolbar button "Open")
3. Click on NotePad toolbar "Find".
The Search requester will open with an empty, but activated textbox.
4. Type in a search pattern text that will fail (don't click the mouse)
5. Hit the Enter key to start the search (don't click on the "Find Next" button).
6. The search will fail, as described above and the search requester
textbox is still active, with the search pattern text selected.

The above steps are the only way I can make a failed search return with the
search pattern text selected.

And it only happens on the first popup of the search requester. All other times
a failed search returns with nothing selected in the pattern box and the
active cursor at the end of the search text that failed.

If you close the search requester and reopen it, or even left click the mouse
once in the search requester text box before searching you never get that
behaviour again.

This is AOS 4.1 upd 6, texteditor.gadget 53.19, NotePad 53.10
AmigaOne X1000.

Tom

If i follow your step and proceed typing in the textfield after your step 6) it happens everytime for that, right in the moment when the find window sets it's top border message back to "Find", i'm being thrown out of the search field gadget.

Exactly what i'm getting at

Maybe it's some GUI prefs i have set that does it for me but nor for others?

[xenic]

@tbreeden
I tried your procedure and get the same results. The text is highlighted the first time you try to find some text after opening the Find window. If you start typeing while the text is highlighted, the highlighted text disappears. If you click on the string gadget before typing, the highlight text is unhighlighted but remains.

The same type of highlighting occurs in the "rename" requester that opens when you select the Workbench/Icon/Rename menu item. The rename text appears highlighted and disappears if you start typing before clicking on the string gadget. System string gadgets didn't work that way previously and I am constantly irritated when I forget to click on the rename string gadget and end up retyping the entire name.

Since we have a mixture of old programs, MUI programs and Reaction programs; there are a lot of inconsistancies in the way GUIs work (unfortunately).

[xenic]

@Raziel
It seems that chris has confirmed the problem in a general way. Since I can't reproduce your problem I don't think I can assist you in tracking down the cause of the problem.