Changeset 1225 for trunk

Timestamp:

Nov 20, 2008 5:17:50 AM (15 years ago)

Author:

dkearney

Message:

adjusting loader so users can say where they want to load the elements of the example xml try. this is done using the <copy> stanza. you can <copy> the data from the <from> location in the example directory's xml file being loaded to the <to> position in the main xml file. this feature is used in some of the photonicsdb applications where there are multiple layers of materials, you need each layer to have access to the whole list of materials, but you dont want to create a specific material example xml file for each layer. instead you can use use one example xml file and copy it to different locations in the tree.

in a loader it looks like this:

<loader>

<about>

<label>Material</label>
<description>Choose the material for layer 1.</description>

</about>
<example>*.xml</example>
<copy>

<from>input.note</from>
<to>input.group(tabs).group(layer1).note</to>

</copy>

</loader>

this may break the loader for some applications, i'm not sure how yet.

Location:

trunk/gui/scripts

Files:

• controlOwner.tcl (modified) (1 diff)
• loader.tcl (modified) (4 diffs)

trunk/gui/scripts/controlOwner.tcl

@@ -270 +270 @@
             set currentpath $path.$_type2curpath($type)
         } else {
-            # default incase i forgot an inpuit type in _type2curpath
+            # default incase i forgot an input type in _type2curpath
             set currentpath $path.current
         }
 
         # copy new value to the XML tree
-        [tool] xml copy $currentpath from $newobj $currentpath
+        # we only copy the values if they existed in newobj
+        # so we don't overwrite values that were set in previous loads.
+        # this is needed for when the users specify copy.from and copy.to
+        # in a loader. in this case, _path2widget holds a list of all
+        # widgets. if there are two loaders loading two different widgets,
+        # and each loader uses the copy from/to functionality,
+        # the second load could wipe out the values set in the first load
+        # because on the second load, the copied paths from the first load no
+        # longer exist in newobj and blanks are copied to the paths
+        # in [tool] xml set by the first loader. the solution is to check
+        # newobj and see if the path exists. if the path exists, then we copy
+        # it over to [tool] xml, otherwise we ignore it.
+        if {"" != [$newobj element -as component $currentpath]} {
+            [tool] xml copy $currentpath from $newobj $currentpath
+        }
 
         # also copy to the widget associated with the tree

trunk/gui/scripts/loader.tcl

@@ -42 +42 @@
     private variable _dnpaths ""  ;# list of download element paths
     private common _dnpath2state  ;# maps download path => yes/no state
+    private variable _copyfrom "" ;# copy xml objects from here in example lib
+    private variable _copyto ""   ;# copy xml objects here in example lib
+    private variable _label2file  ;# maps combobox labels to filenames
 }
 
@@ -199 +202 @@
                     if {![info exists entries($label)]} {
                         set entries($label) $obj
+                        set _label2file($label) [file tail $fname]
                     }
 
@@ -215 +219 @@
     }
 
+    set _copyfrom [$_owner xml get $path.copy.from]
+    set _copyto [$_owner xml get $path.copy.to]
+
     #
     # Assign the default value to this widget, if there is one.
@@ -336 +343 @@
         $itk_component(combo) component entry configure -state disabled
     } elseif {$obj != "" && $itk_option(-tool) != ""} {
+        if {("" != $_copyfrom) && ("" != $_copyto)} {
+            $obj copy $_copyto from $_copyfrom
+        }
+        $_owner xml put $_path.file $_label2file($newval)
         $itk_option(-tool) load $obj
         set _lastlabel $newval