Details Ticket 2689


Comment | Reply | Take | Resolve


Serial Number 2689
Subject i.vpoints: menu falls off end of monitor
Area bug
Queue grass
Requestors hamish_nospam@yahoo.com
Owner none
Status open
Last User Contact Never contacted
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Wed Jun 28 09:02:10 2006 (2 yr ago)
Created Sat Nov 13 10:43:41 2004 (4 yr ago)

Transaction History Ticket 2689


Sat, Nov 13 2004 10:43:41    Request created by guest  
Subject: i.vpoints misc minor problems

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 5.7cvs_1nov2004

some i.vpoints problems:

bug:
when the monitor is too narrow you can't select input method: [keyboard or screen]
(window needed to be ~ 900 pixels wide to select keyboard)

bug:
I also managed to hard-lock the program somehow.
 (needed 'pkill -9 i.vpoints' and xkill the x0 window)
Not quite sure exactly how.

bug:
can't unzoom vector map beyond WIND in target mapset

bug:
can't backspace during keyboard input of GCPs.

bug:
analyze window columns are too crowded and overlap

bug:
doesn't use DEFAULT_BG_COLOR for background, possible consequence of this is
green button commands' edges at bottom hard to distinguish from each other.
This looks nice in i.points.

wish:
add support for lat/lon ddd:mm:ss keyboard input like v.points has.
[done; currently have to explicity label east "E" (eg 123:55E 45:30S)]


see also bug # 1077
http://intevation.de/rt/webrt?serial_num=1077


Hamish
Sat, Jun 17 2006 11:29:10    Comments added by hbowman  
I think I fixed the hard-lock problem. d.frame was in the wrong place and
locked waiting for access to the display after an error.


Hamish
Tue, Jun 27 2006 05:25:18    Comments added by hbowman  
> bug:
> when the monitor is too narrow you can't select input method:
>  [keyboard or screen] (window needed to be ~ 900 pixels wide to
>  select keyboard)

menu condensed where possible. Font size needs a max I think.


> bug:
> I also managed to hard-lock the program somehow.
> (needed 'pkill -9 i.vpoints' and xkill the x0 window)
> Not quite sure exactly how.

"d.frame -e" was in the wrong place, fixed in CVS.


> bug:
> can't unzoom vector map beyond WIND in target mapset

outstanding, but is this really a problem?


> bug:
> can't backspace during keyboard input of GCPs.

workaround: ^H.


> bug:
> analyze window columns are too crowded and overlap

see above max fontsize comment (auto from window height)

> bug:
> doesn't use DEFAULT_BG_COLOR for background, possible consequence of this is
> green button commands' edges at bottom hard to distinguish from each other.
> This looks nice in i.points.

green->grey in CVS.


> wish:
> add support for lat/lon ddd:mm:ss keyboard input like v.points has.

> [done; currently have to explicity label east "E" (eg 123:55E 45:30S)]



> see also bug # 1077
>  http://intevation.de/rt/webrt?serial_num=1077



so still outstanding:

* when the monitor is too narrow you can't select input method or see rms
error text
* can't unzoom vector map beyond WIND in target mapset [won't fix?]
* can't backspace during keyboard input of GCPs [workaround: ^H]


Hamish
Wed, Jun 28 2006 09:00:57    Comments added by hbowman  
backspace issues fixed in CVS for both imagery modules.
(octal check for DEL as well as BS)


So only real issue remaining for this bug is the too narrow display.
I've condensed i.vpoints (the main offender)'s menus where possible.
setting a max font size might help.


Hamish
Wed, Jun 28 2006 09:02:10    Subject changed to i.vpoints: menu falls off end of monitor by hbowman  
Comment | Reply | Take | Resolve

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request