. sub menus make sense, but can we do that for mouse menus? . we also have a (bug) tracker category for guy improvements - not just bugs and feature requests
stefan Sunburned Surveyor wrote: > I should have known that. :] > > I will try to file the items in the previous thread to either the bug > tracker or the feature tracker on my lunch break today, unless Peppe > wants to beat me to it. > > SS > > On Mon, Dec 15, 2008 at 8:27 AM, Larry Becker <becker.la...@gmail.com> wrote: >> Hi SS, >> >> There is separate tracker for feature requests: >> >> http://sourceforge.net/tracker/?group_id=118054&atid=679909 >> >> regards, >> Larry >> >> On Mon, Dec 15, 2008 at 10:23 AM, Sunburned Surveyor >> <sunburned.surve...@gmail.com> wrote: >>> Larry and Stefan, >>> >>> Thanks for clarifying the copy/paste issue. >>> >>> Peppe and Jukka, >>> >>> This type of feedback is really invaluable. Thanks for taking the time >>> to provide it. >>> >>> All, >>> >>> I could enter the items mentioned above into our bug tracker. Does >>> anyone know how to separate true "bugs" from suggested improvements >>> like changes to the user interface/user interaction. I would think it >>> might be helpful to distinguish the two categories of items in the >>> tracker. >>> >>> SS >>> >>> On Sun, Dec 14, 2008 at 12:47 AM, Rahkonen Jukka >>> <jukka.rahko...@mmmtike.fi> wrote: >>>> Hi, >>>> >>>>> 1) Image Layer Manager: not sure where it comes from - we may change >>>>> the >>>>> behaviour as you proposed, i.e. disable the option) >>>> I remember that it came with the JUMP image support from Vivid solutions >>>> but I may be wrong. I have never quite understood what value it is >>>> supposed >>>> to give for the user. >>>> >>>> >>>>> 2) refresh layers: I have not used it either. I think it was useful a >>>>> while ago? However, we need to check its function (what probably >>>>> requires a database - which I don't have) >>>> It is essential for DB layers. Usually DB layer features are cached by >>>> OJ and updates in the database do not show before refreshing them. If the >>>> function does not do anything with other data sources perhaps it could be >>>> renamed to "refresh DB layer" then? >>>> >>>> I have a couple of remarks: >>>> >>>> - Image layers cannot be saved into project file. Perhaps it would not >>>> be very difficult to make them saveable? >>>> - DB layer can be saved into project files. Therefore the database query >>>> for the layers is saved. However, the used cannot see the actual SQL while >>>> using OJ. It would be useful sometimes to see the SQL in the properties or >>>> even to be able to edit it without a need to make a new layer. Editing SQL >>>> should naturally be followed by automatic refresh if original features were >>>> in disk cache. >>>> - I use usually scale bar as a hint while digitizing. It does not get >>>> saved into project file but scale bar must be added by hand every time. >>>> >>>> -Jukka Rahkonen- >>>> >>>> > 1) Image Layer Manager (Test) - It works only if I click on a >>>>> single raster layer. It doesn't work if I click on 2 or more raster >>>>> layers. >>>>> > It has an "Add" option which doesn't work (at least with my test >>>>> JPG). The "Delete" option, of coarse works and.. the image >>>>> disapears >>>>> on the Layer view. It is not possible to let it come back (Add >>>>> doesn't work!) until I close and open again the raster. >>>>> > Option "Close", of coarse, close the window. >>>>> > Below the window, In the show metadata section, the coordinates >>>>> of upper left and lower right point are displayed. >>>>> > Since only this last function seems to be useful, I ask if we >>>>> can >>>>> remove this function and substitute it with a general "Show raster >>>>> metadata" one which save the last function >>>>> > >>>>> > 2) Refresh-layers >>>>> > I still haven't seen working this function. It is never >>>>> available >>>>> on any projects I did with OpenJUMP. Its tooltip shows that "Layer >>>>> must have a data souce". Is this function connected to PostGIS and >>>>> Oracle datasource? If yes, Why not to move this function on Menu >>>>> bar>Layer menu? >>>>> > This will probabily simplify the layer list (less items) >>>>> > >>>>> > ***************************** >>>>> > Another observation. >>>>> > When a user wants to cut and past items, he has to use the Layer >>>>> View menu to copy and the Layer List menu to paste. It would be >>>>> better if both Copy and Paste items will be on the same menu, in >>>>> this case the Layer View >>>>> > >>>>> > >>>>> > Regards >>>>> > >>>>> > Peppe >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
