I confirm this is correct. The original idea of cloned windows was to be able to use them as a zoomed view or overview of the main window. I can see how different layer visibility might be nice - but as pointed out that would be a bit tricky to do in the current architecture, since both views share the same underlying Layer model.
You might be able to do this by creating a new view with a new set of layers based on FeatureCollections wrapping the FCs in the original view. Or maybe even clone the Layers but point them to the same FCs as the original? This would let you change the entire symbology, in fact - which might be useful in some situations. This seems like it could get confusing, tho... By the way, do you know that if you drag out on the left side of the clone window you can see the Layer list? Another cool thing I had some thoughts about would be to slave the clone view to the main view, with the clone displaying a zoomed view of the main. A tool would display the clone outline on the main, and allow moving and changing the extent of the clone view. This would provide a nice outline capability. You could even cascade these views... although that might be overkill and confusing. Sunburned Surveyor wrote: > Michael wrote: > > "Somebody will correct me if I am wrong. I think visibility cannot be > easily managed on a per window basis because this is a layer attribute > and cloned windows share a same layer manager (that means also the same > set of layers with their visibility attribute)." > > I believe this is correct. This means Michael's description of the > technical challenge in creating cloned windows with separate layer > visibility is also correct. Really a cloned window is simply a > duplicate view of the same LayerManager. > > The Sunburned Surveyor > > On Thu, Jun 12, 2008 at 11:41 PM, Michael Michaud > <[EMAIL PROTECTED]> wrote: > >> Rahkonen Jukka a écrit : >> >>> Hi, >>> >>> Option b) was in my mind because I was thinking that a clone is exact copy >>> of the mother window. So I wondered that having different layers in cloned >>> windows would be impossible. Per perhaps switching visibility of the >>> layers could be done independently? >>> >>> >> Somebody will correct me if I am wrong. I think visibility cannot be >> easily managed on a per window basis because this is a layer attribute >> and cloned windows share a same layer manager (that means also the same >> set of layers with their visibility attribute). >> >> The only easy way I can imagine to implement the feature you ask would >> be to clone layers creating a new layer around an existing feature >> collection. I'm not sure this would help or just be more confusing (but >> I'm quite sure the api makes it possible). >> Why I think it may be confusing : because you would have to use two >> different tasks (I think two cloned windows must have exactly the same >> layers in the current jump framework), and I cannot see an easy way to >> distinguish layers of task 2 sharing their feature collection with >> layers of task 1 from layers of task 2 having their own (I'm not sure >> I'm clear). >> >> my 2 cents, >> >> Michael >> >>> -Jukka- >>> >>> >>> -----Alkuperäinen viesti----- >>> Lähettäjä: [EMAIL PROTECTED] puolesta: Stefan Steiniger >>> Lähetetty: pe 13.6.2008 6:13 >>> Vastaanottaja: OpenJump develop and use >>> Aihe: Re: [JPP-Devel] Question about Cloned windows >>> >>> Hei Jukka, >>> >>> I had to think about it a while until I understood. >>> So what you propose is, that the cloned windows: >>> a) allow different layers to be displayed, or alternatively >>> b) allow to set the visibility individually per "clone"? >>> >>> but.. similar to Landon, I have no clue how the cloning is done >>> internally. Just by observation how it works now, I would say it is >>> difficult to do de decoupling. But maybe I am wrong. >>> >>> stefan >>> >>> Sunburned Surveyor schrieb: >>> >>> >>>> Jukka, >>>> >>>> I'm afraid that I can't answer your question. Hopefully the programmer >>>> or programmers that implemented the cloned window functionality will >>>> have time to comment in the next day or two. >>>> >>>> You can always add a feature request to our sourceforge tracker. >>>> >>>> The Sunburned Surveyor >>>> >>>> On Tue, Jun 10, 2008 at 7:34 AM, Rahkonen Jukka >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> Are cloned windows inevitably working such tightly together that changing >>>>> layer visibility in one window is toggling it in all windows? Being able >>>>> to >>>>> control layer visibility individually cloned windows would make the fine >>>>> new >>>>> feature of Synchronized windows extremely usable. Features could be >>>>> examined on top of different maps and images and edited in any window. >>>>> Now >>>>> if cloned windows are used feature editing is possible in any window but >>>>> background layer is the same in all windows. If several project windows >>>>> are >>>>> opened they can be synchronized and layers can be selected individually, >>>>> but edids done is one window do not get updated to other windows. >>>>> >>>>> Developers, do you think that it would be possible to implement >>>>> independent >>>>> layer visibility control for cloned windows? >>>>> >>>>> Peppe inserted just a screen capture from my computer at >>>>> >>>>> http://jump-pilot.sourceforge.net/wikiimages/other/OJ_Synchronized_windows.JPG >>>>> >>>>> That image is done by opening the same OJ project to four different >>>>> project >>>>> windows. It would be nice to see the same result with one project cloned >>>>> to >>>>> three other windows. >>>>> >>>>> >>>>> >>>>> >>>>> -Jukka Rahkonen- >>>>> ------------------------------------------------------------------------- >>>>> Check out the new SourceForge.net Marketplace. >>>>> It's the best place to buy or sell services for >>>>> just about anything Open Source. >>>>> http://sourceforge.net/services/buy/index.php >>>>> _______________________________________________ >>>>> Jump-pilot-devel mailing list >>>>> Jump-pilot-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> _______________________________________________ >>>> Jump-pilot-devel mailing list >>>> Jump-pilot-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>>> >>>> >>>> >>>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
