Submitted by Tom on 2011/07/18 11:08
GUI Tweak that would be very helpful:
 
When an item is selected, and I press Enter to create a new item - the new item is also selected. 
If I then press F2 to edit, nothing happens.
I then have to use tabkey, but focus jumps first to the # column and then from there to the field to the right of the item/tree field i.e. item field gets skipped. I then have to use Shift+Tab to get back.
i.e. it's very messy trying to create and type in the new item.
 
Suggestions (dont know if possible)
if an item is selected, and F2 is pressed, the tree field would go into edit-mode.
AND /  OR
if an item is selected and Tab key is pressed, the focus would go to the item field first - or second after the # field (but maybe there's a reason for the other behaviour?)
 
 

Comments

Hi Tom,
 
To understand it properly, I would need a video of it. Too much depends on the actual grid setup
 

Tom

2011/07/22 07:20

In reply to by Pierre_Admin

[quote=Pierre_Admin]
To understand it properly, I would need a video of it. Too much depends on the actual grid setup 
[/quote]
 
Hi Pierre,
 
 
I cant do a video but the problem is easily visible in a sample file:
 
with the default sample file (nothing changed), select an item using the # column.
Press Enter => new item created
 
Same situation, the whole item is selected. 
Also same that F2 does Not do anything.
 
Tab indents the item so I'm not even sure how to edit the item field without resorting to the mouse.

 
My settings are that tab moves between fields, otherwise behaviour is the same.

Hope that that is clearer?
 
Suggestions would be:

if an item is selected, and F2 is pressed, the tree field would go into edit-mode. 
AND /
 OR [ with Options 1.2.11 (use tab key to indent) disabled   ]
if an item is selected and Tab key is pressed, the focus would go to the item field first - or second after the # field (but maybe there's a reason for the other behaviour?)
 

Pierre_Admin

2011/07/22 17:47

In reply to by Tom

Ok, got it.
 
Fixed in v0.9.25V
 

Tom

2011/08/02 07:26

In reply to by Pierre_Admin

[quote=Pierre_Admin]
Ok, got it.
 
Fixed in v0.9.25V[/quote]
 
thanks Pierre, works a treat

[quote=Tom][using the tabkey on a selected item:] focus jumps first to the # column and then from there to the field to the right of the item/tree field i.e. item field gets skipped. I then have to use Shift+Tab to get back [to the item field][/quote]
 
is there a reason for this behaviour BTW?
 
It seems related to mantis issue 1133 where right-clicking on selected item(s) causes focus to go to # column resulting in that column being copied if context-menu>Copy is used.
I made a note on that mantis issue btw, cause you had marked it as fixed on the 17 July but it's not in 25V3 - maybe it's coming in W?
 

Pierre_Admin

2011/08/03 16:31

In reply to by Tom

>is there a reason for this behaviour BTW?
 
This is the behaviour if the option Tab key indents is set. The reason is that you don't want to indent items by mistake. So when the focus is to the right of the tree column, a "virtual" right pane is created and the tab key moves the focus within that virtual right pane.
 
re Mantis 1133: It is now fixed in v0.9.25W
 

Tom

2011/08/04 08:24

In reply to by Pierre_Admin

[quote=Pierre_Admin]
>is there a reason for this behaviour BTW?
 
This is the behaviour if the option Tab key indents is set. The reason is that you don't want to indent items by mistake. So when the focus is to the right of the tree column, a "virtual" right pane is created and the tab key moves the focus within that virtual right pane.[/quote]
 
the behaviour I describe is when the option to use the tab key to indent is not selected. (I've never used the tab key to indent, so dont know what happens there.)
 
 
PS thanks for the mantis clarification

Pierre_Admin

2011/08/05 20:05

In reply to by Tom

[quote=Tom]
the behaviour I describe is when the option to use the tab key to indent is not selected. (I've never used the tab key to indent, so dont know what happens there.)
[/quote]
 
Humm... I'm not able to reproduce it when "tab key indents" is not checked. Focus cycles in this order:
  1. # (whole item selected)
  2. Item
  3. Column X
  4. Column Y
  5. #
  6. ...
Read-only columns are skipped using the tab key, could that be it ? Otherwise, I have no idea. A small video would help !
 

Tom

2011/08/09 06:37

In reply to by Pierre_Admin

 
with a new portable "install"
  1. I deselect the option to use TAB to indent (1.2.11 in Options)
  2. Open a new sample file
  3. Add a few columns to grid (for testing)
  4. Select item usíng the # column
  5. Press TAB key, focus goes to:
    1. # column
    2. column to the right of the item column
    3. continues to the right to end of the row
    4. then full item selected again
    5. back to [1] the # column - and so on
 
Summary:
Item field is never selected using the TAb key (when the option to use TAB to indent is deselected)
 
Can anyone confirm or deny this? Please list your OS
 
Thanks, Tom
____________________________
Win7 Pro 64bit latest portable version

Armando

2011/08/09 19:44

In reply to by Tom

Dunno if that'll be helpful. Made a little screencast, following your indications. Here's what happens when I press tab after selecting the first column (#).
 
 
Notes :
 
- After pressing tab, the first column/cell after # is not completely selected per se (not greyed). It's got a dotted rectangle inside, but that's it.
- Pressing delete when "focus" was on the second column/cell deleted the number in the # column instead of deleting the date value in the "focused" cell.
 
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 2
Dell Vostro 1500, Ram:3gb, CPU:Core2Duo T7500 2.2ghz

Tom

2011/08/10 02:51

In reply to by Armando

[quote=Armando]

- After pressing tab, the first column/cell after # is not completely selected per se (not greyed). It's got a dotted rectangle inside, but that's it.
[/quote]
OK, thanks Armando,
that's what got me - it is selected (column 2) but it is not shown as selected in the same manner as other columns (why?)
 
 
[quote=Armando]
- Pressing delete when "focus" was on the second column/cell deleted the number in the # column instead of deleting the date value in the "focused" cell.
[/quote]
Also, copy copies the # column instead of second column
This probably related to the bug where copying selected item via context menu only copies the # column (which I think Pierre has fixed in "W", so maybe this is fixed too?)
 

Win 7 Pro 64bit ~ Portable latest IQ  (9.25.V3)