Hi Jukka,
> OJ user cannot do anything in the cloned windows nowadays.  It used to be 
> possible to pan, zoom, select features, and edit in any of the cloned 
> windows.  Now cloned windows are only reflecting the situation of the main 
> window but all the actions must be done in the main window. There is an 
> exception: right click actions work also in the cloned windows and zooming is 
> possible that way.
I cannot reproduce what you describe with the current version (r3034) 
and have not noticed anything special since the following bug fix
https://sourceforge.net/tracker/?func=detail&aid=3536708&group_id=118054&atid=679906
> The cloned windows option has always lacked one feature which would have made 
> it very nice and useful: possibility to show different layers in different 
> windows.  If that was possible user could digitize on top of raster maps, 
> aerial images, satellite images etc. and select the most suitable background 
> image in a very flexible way. Or user could do visual change detection by 
> having a few images from different acquisition times open for synchronized 
> browsing. I have been told before that cloning is done in such a way that 
> controlling layer visibility individually in different windows is not 
> possible.
I may have told that. Because a cloned window uses the same LayerManager 
than the source windows (then the same set of layers). What you ask is 
between the cloned window and the new project because it needs to have 
different layers, but same datasets. Of course, nothing is impossible 
and I encourage you to write a Feature Request (although I make very 
slow progress on the FR list ;-()

Michaël

> Cloned windows were still somehow usable for editing because user could show 
> the vectors at different scales.  Even that did not work pretty well when 
> adding new features because they did not appear automatically into all the 
> cloned windows. Editing existing features worked fine, though.
>
> It would be good if zooming, panning and editing in the cloned windows could 
> be activated again.
>
> Versions used in comparison: OJ 1.4.2 and r.3032.
>
> -Jukka Rahkonen-
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Jump-pilot-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to