close
Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Opened 2 years ago

Closed 22 months ago

Last modified 17 months ago

#358 closed bug (invalid)

A list of emails will cancel "pop up selection"

Reported by: padrino Owned by:
Priority: undecided Milestone:
Component: undefined Version: nightly build
Severity: major Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

Description

Select any char you like to test this with.

Write a mail, pressing that char as email address to see what list of alternatives YAM has to offer.

Now descide for a name, that will be placed in between.

Let's say you took "a" and the list shows

a
ab
abc

We want to place our list at 3rd position.

So open the addressbook add a list (not group) named abb.

Try writing another mail.

On "a" YAM will offer you

a ... ...
ab ... ...
abb - -
abc ... ...

Go down, and as you reach "abb" the popup will be closed.

At least it's here that way, every time, no matter at which position the email-list will be.

Attachments (0)

Change History (11)

comment:1 Changed 45 years ago by padrino

  • Status changed from pending to new

comment:1 Changed 2 years ago by tboeckel

Strange, does not happen here. I have a list since several years now in my address book but navigating in the popup list with the cursor keys never closes the list unless I press RETURN, no matter what kind of entries are displayed in the list.

comment:2 Changed 2 years ago by padrino

I removed my keyboard an tried another with the same result. :(

I wonder if it has to do, that here YAM "autoswitches" to body area while typing a subject or address sometimes/very often.

Maybe other SAM440ep users could have a look at it...

comment:3 Changed 2 years ago by tboeckel

I must add that navigating within the popup list is solely controled by NList. Although YAM performs some actions when the active list entry changes the list will be closed of certain key pressed only. These are: Return, Escape, Delete, Tab and comma. Did you press one of these by accident? I really doubt this to happen on a specific type of machine only.

comment:4 follow-up: Changed 2 years ago by padrino

Nope, I didn't press any of those by accident.
And I can repeat it as often and as slow as I want to, with the same result.

Cause of a "mistery key" I changed the keyboard, to see if my keyboard might have some kind of "shirt circuit". But as I said, different keyboard, same problem.

I can see, if I find older versions of nlist to test.

Maybe you could supply a debug version of nlist keystrokes it receives, to see of one of those mentioned mentioned by you is triggered?

comment:5 in reply to: ↑ 4 Changed 2 years ago by tboeckel

Replying to padrino:

Maybe you could supply a debug version of nlist keystrokes it receives, to see of one of those mentioned mentioned by you is triggered?

Not necessary for the beginning. Just start with a GUI debug log of YAM. That will contain the key press codes already.

comment:6 Changed 2 years ago by padrino

Ok, here is the output, till it "autocloses" (the popup had the testmail and the testlist on 2nd in it).

00:D: Recipientstring.c:652:event muikey 28 code 41
00:D:  AddressmatchPopup.c:296:Match this: 'test'
00:D: Recipientstring.c:652:event muikey -1 code c1
00:W:  YAM_UT.c:4246:MapRawKey returned != 1 (00000000)
00:D: Recipientstring.c:652:event muikey 3 code 4d
00:D:    Recipientstring.c:1197:replace selected: 'safd@asd.de'
00:D: Recipientstring.c:652:event muikey -1 code cd
00:W:  YAM_UT.c:4246:MapRawKey returned != 1 (00000000)
00:D: Recipientstring.c:652:event muikey 3 code 4d
00:D:    Recipientstring.c:1197:replace selected: ''
00:D: Recipientstring.c:652:event muikey -1 code cd
00:D:  AddressmatchPopup.c:296:Match this: ''
Last edited 22 months ago by damato (previous) (diff)

comment:7 Changed 22 months ago by damato

  • Status changed from new to pending

Does that problem still exist? AFAIR thore and me reworked the recipientstring right before the release of 2.8 quite significantly and with that rework I also fixed a problem where the matchwindow was automatically closed as soon as the autosave did happen. This pretty much sounds like the problem you encountered weeks before.

So please try to reproduce with 2.8 or the latest nightly builds and report back if the problem is solved.

comment:8 Changed 22 months ago by padrino

Seems gone - can be closed. Thanks.

comment:9 Changed 22 months ago by tboeckel

  • Milestone set to YAM 2.8p1
  • Resolution set to invalid
  • Status changed from new to closed

My guess is that this issue was most probably caused by trashed memory of BetterString.mcc. At least this explains why I was unable to reproduce it myself, as the memory trashing must not necessarily cause the same symptoms on different systems.

I'm glad to hear the fix for BetterString.mcc magically fixes lots of other issues.

comment:10 Changed 17 months ago by damato

  • Milestone YAM 2.8p1 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Mario Cattaneo(Reporter, Participant)