Hi Jukka,
Thanks for the comments and ideas. I believe it may be possible to use
the mouse wheel button to activate the Alt key quasimode tools. That should
enable mouse wheel zooming while the button was held down.
Larry
On Wed, Feb 4, 2009 at 2:05 AM, Rahkonen Jukka <[email protected]>wrote:
> Hi,
>
> Myself I have never user arrow keys and Page up / Page down shortcuts.
> Neither when digitizing nor for layer control. It does not mean that they
> are unnecessary, people have different tastes. But for me Shift-Alt-Drag
> shortcut for panning and Alt-Left click/Right click for zooming feel
> better. There may be cases when arrow keys and PgDown/PgUp might still be
> better. At least they make it possible to handle the map view and continue
> digitising with one hand only by one-handed operator or by two-handed user
> driving a car or having a phone in the other hand on helpdesk. Even in that
> case the layer list operations are pretty easy to do with mouse only. For
> my mind those shortcuts could be disabled by default. But have a try with
> one-handed digitising, it's funny. I started immediately to hunger for two
> features:
> 1) Open layers style Click and drag panning
> 2) Mouse wheel zoom to be operational all the time. Now mouse wheel is
> listened only when the traditional zoom or panning tools are selected.
>
> I do not know how difficult those extra features would be to implement.
> Mouse wheel is not used for anything else so at least if should not make any
> confuse. Click and drag does have a meaning for lots of tools (selecting,
> moving vertex or feature, drawing a box or circle etc.) and users might feel
> it inconvenient if click and drag is sometimes panning and sometimes doing
> other things. But could it be possible to start listening for middle click?
> Then middle click and drag could be used for panning always.
>
> -Jukka Rahkonen-
>
> ------------------------------
> *Lähettäjä:* Larry Becker [mailto:[email protected]]
> *Lähetetty:* 3. helmikuuta 2009 18:09
> *Vastaanottaja:* OpenJump develop and use
> *Aihe:* Re: [JPP-Devel] Pan and Zoom shortcut keys problem
>
> If no one really needs the pan and zoom shortcut keys, we could just
> disable InstallKeyPanPlugIn in the default-plugins.xml file. Those who
> really need it and are willing to accept the side effects can add it to
> their workbench-properties.xml file. Comments?
>
> regards,
> Larry
>
> On Thu, Jan 29, 2009 at 1:49 PM, Larry Becker <[email protected]>wrote:
>
>> I now have a pretty complete understanding of the "Pan and Zoom shortcut
>> keys problem". I have attempted to fix it, but nothing seems to work. To
>> reiterate the problem, when the arrow and page up/page down keys are used to
>> move the cursor while editing layer names, they continue to pan and zoom the
>> layer view. This unexpected behavior also occurs during other arrow key
>> uses like menu selection. I consider this a "must fix" problem because is
>> makes the UI unpredictable. Here is what I've found out so far:
>>
>> 1) Pan and Zoom key shortcuts are implemented in a separate plugin written
>> by Ugo.
>> 2) It uses the WorkBenchFrame#addKeyboardShortcut method (I'm doing this
>> from memory so don't quote me on the exact name).
>> 3) It implements no checks to determine the context before executing the
>> shortcut commands.
>> 4) It is possible to add an EnableCheck when the keyboard shortcut is
>> defined.
>> 5) I have tried several EnableCheck versions, but so far have not found a
>> way to restrict the pan and zoom behavior to only the layer view. This
>> seems trivial, but isn't because the methods are called multiple times with
>> different panels "active".
>> 6) The LayerNamePanel and the LayerViewPanel are implemented as JSplitPane
>> panels under the TaskFrame.
>> 7) Here is the real problem: There doesn't seem to be a definition in Java
>> of "front most" component in a split pane, so both panels get all of the key
>> events.
>> 8) In order to fix the problem it is necessary to restrict the scope of
>> the pan and zoom keyboard shortcuts.
>> 9) I could not find a way to ensure that the LayerViewPanel is "not
>> active" when the task window active. I'm not even sure if this would be a
>> good idea.
>> 10) Unless someone can see a way out of this trap, it doesn't look like
>> the problem has a code solution.
>>
>> The floor is open for alternative solutions. We could, for instance,
>> check for less often used key combinations like control-arrow which might
>> minimize the conflicts.
>>
>> regards,
>> Larry
>> --
>> http://amusingprogrammer.blogspot.com/
>>
>
>
>
> --
> http://amusingprogrammer.blogspot.com/
>
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code
> to
> build responsive, highly engaging applications that combine the power of
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK
> and
> Ajax docs to start building applications today-
> http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Jump-pilot-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>
--
http://amusingprogrammer.blogspot.com/
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
