[IDV #GFM-139212]: IDV - Sigma coordinates in IDV

Hi Andrew,

> OK, thanks for that. I've created a 2x3 skin (attached) which seems to
> work OK. I've added these lines my RBI file:
> 
> <resources name="application.resource.skin"  loadmore="true">
> <resource location="%SITEPATH%/sixpanel_skin.xml"/>
> </resources>
> 
> I do have a couple more questions though:
> 
> 1) How can I make this skin appear under the New Window->Map Display
> menu, instead of on its own?
You add a label attribute with a category:
    <resource
       location="%IDVPATH%/skins/skin.xml"
       label="Map Display&gt;One Pane">

The "&gt;" is really a ">" which is the category separator in the label.


> 2) The new skin always appears as the default map display when I start
> IDV. How do I stop that from happening?
The IDV creates the first UI from the highest priority skin resource, which
in your case is your skin (i.e., we always place more emphasis on the 
non-default
system resources).  A work around is to completely overwrite the skin resource
definitions with all of the skins. See attached. We'll try to add a "default 
skin"
flag to the resources so it doesn't just pick up the first one.


> 3) Can I change the default projection used in the skin?
You cannot. There is a properties attribute in the idv.view tag:
          <idv.view
             class="${left_view_class}"
             viewid="viewleft%version%"
             id="viewleft"
             
properties="clickToFocus=true;shareViews=true;showControlLegend=false;initialSplitPaneLocation=0.2;legendOnLeft=true;size=300:400;shareGroup=view%versionuid%;"/>

that allows you to set some properties of the view but you can't use this
to set the projection. I'll put it on the todo list.

> 4) Is there any way I could create a macro or bundle to load a
> pre-defined set of data into each of the panels in the new skin? I'd
> like to load 6 different fields from the same dataset into it, but don't
> really want to have to load each field in separately.
> 

Right now no. We have never thought about the skins in this way. We've used 
them more
to define the user interface separate from any displays.  
Can you come up with a couple of use cases for this so I can get my head around 
the
idea? (by the way - I'm out tomorrow for a full week and will be away
from email so, unless Don picks up this thread you won't hear back from me 
for a week). 

One thing that sort of fits into how we've used skins that comes to
mind is that you can save the state of a single view (not its displays but
its projections, flags, viewpoint) as a bundle. The skin could have a reference
to that initalization bundle that when we construct the view we use the state 
in the bundle. I'm not too sure about how data/displays fits into this though.

-Jeff



Ticket Details
===================
Ticket ID: GFM-139212
Department: Support IDV
Priority: Normal
Status: Open

Attachment: skins.rbi
Description: Binary data