Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Panel Keystrokes
Wed, Aug 22 2012 2:49 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

This is to Mark Brooks, specifically, and everyone else, generally.

Unfortunately, those changes that I made to the panels/forms at the last
minute to allow keystroke handling without any controls present are going to
need to get backed out in the second build.  They cause some minor focus and
display issues with various browsers.  So, this will mean that panels/forms
won't get keystroke events unless they have an actual input control on them
that can accept keystrokes and their KeyPreview property is True.

What I'm going to need to do instead is provide a separate component for
allowing this type of processing.  I'm planning on adding an image browser
component that will do something similar to this in terms of keystroke
handling - is this what you were looking to have ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Aug 23 2012 4:01 AMPermanent Link

Mark Brooks

Slikware

Avatar

<<Unfortunately, those changes that I made to the panels/forms at the last
minute to allow keystroke handling without any controls present are going to
need to get backed out in the second build.  They cause some minor focus and
display issues with various browsers.>>

Yup. Just discovered this myself. We test across IE, Chrome and Safari. No problem on IE, minor problem on Chrome, horrible on Safari (thick blue edging). Can you tell me if this is going to be a quick-fix or if there is something I can use as a workaround? If not, can I safely revert to a previous build for now? Certainly only expecting a reversion not a solution.

<<What I'm going to need to do instead is provide a separate component for
allowing this type of processing.>>

Sounds like a sensible idea to me Tim.

<<I'm planning on adding an image browser
component that will do something similar to this in terms of keystroke
handling - is this what you were looking to have ?>>

My scenario is a custom panel component that itself holds a list of child panels which themselves hold some images and labels. This provides a really nice scrollable list component with icons etc. Currently you can only move around with the mouse i.e you can;t scroll from item to item with the up / down keys. Not essential but woudl be nice.

Cheers
Mark
Thu, Aug 23 2012 3:20 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Mark,

<< Yup. Just discovered this myself. We test across IE, Chrome and Safari.
No problem on IE, minor problem on Chrome, horrible on Safari (thick blue
edging). Can you tell me if this is going to be a quick-fix or if there is
something I can use as a workaround? If not, can I safely revert to a
previous build for now? Certainly only expecting a reversion not a solution.
>>

What you want to do is just remove this line in the WebCtrls unit:

begin
  { This causes the container control to be focusable so that
    it can receive keyboard events properly }
  FClient.tabIndex:=-2; <<<<<<<<<<<<<<<<<<<<< Get rid of this (and the
comment, too Smile)

<< My scenario is a custom panel component that itself holds a list of child
panels which themselves hold some images and labels. This provides a really
nice scrollable list component with icons etc. Currently you can only move
around with the mouse i.e you can;t scroll from item to item with the up /
down keys. Not essential but woudl be nice. >>

I'm going to be adding a component like an image browser at some point, so
you should at least get some relief at that point.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Aug 24 2012 4:35 AMPermanent Link

Mark Brooks

Slikware

Avatar

"Tim Young [Elevate Software]" wrote:

<<What you want to do is just remove this line in the WebCtrls unit:

begin
  { This causes the container control to be focusable so that
    it can receive keyboard events properly }
  FClient.tabIndex:=-2; <<<<<<<<<<<<<<<<<<<<< Get rid of this (and the
comment, too Smile)>>

Sorted. Tks.
Image