Quantcast

The Trunk: ToolBuilder-Kernel-pre.110.mcz

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

The Trunk: ToolBuilder-Kernel-pre.110.mcz

commits-2
Patrick Rein uploaded a new version of ToolBuilder-Kernel to project The Trunk:
http://source.squeak.org/trunk/ToolBuilder-Kernel-pre.110.mcz

==================== Summary ====================

Name: ToolBuilder-Kernel-pre.110
Author: pre
Time: 15 May 2017, 9:34:18.749328 pm
UUID: 86628552-c37c-c34b-ba1d-f11ec0a31a35
Ancestors: ToolBuilder-Kernel-jr.109

Adds double click capabilities to PluggableTreeSpecs

=============== Diff against ToolBuilder-Kernel-jr.109 ===============

Item was changed:
  PluggableWidgetSpec subclass: #PluggableTreeSpec
+ instanceVariableNames: 'roots getSelectedPath setSelected getSelected setSelectedParent getChildren hasChildren label icon unusedVar menu keyPress doubleClick dropItem dropAccept autoDeselect dragItem nodeClass columns vScrollBarPolicy hScrollBarPolicy dragStarted'
- instanceVariableNames: 'roots getSelectedPath setSelected getSelected setSelectedParent getChildren hasChildren label icon unusedVar menu keyPress dropItem dropAccept autoDeselect dragItem nodeClass columns vScrollBarPolicy hScrollBarPolicy dragStarted'
  classVariableNames: ''
  poolDictionaries: ''
  category: 'ToolBuilder-Kernel'!
 
  !PluggableTreeSpec commentStamp: 'mvdg 3/21/2008 20:59' prior: 0!
  A pluggable tree widget. PluggableTrees are slightly different from lists in such that they ALWAYS store the actual objects and use the label selector to query for the label of the item. PluggableTrees also behave somewhat differently in such that they do not have a "getSelected" message but only a getSelectedPath message. The difference is that getSelectedPath is used to indicate by the model that the tree should select the appropriate path. This allows disambiguation of items. Because of this, implementations of PluggableTrees must always set their internal selection directly, e.g., rather than sending the model a setSelected message and wait for an update of the #getSelected the implementation must set the selection before sending the #setSelected message. If a client doesn't want this, it can always just signal a change of getSelectedPath to revert to whatever is needed.
 
  Instance variables:
  roots <Symbol> The message to retrieve the roots of the tree.
  getSelectedPath <Symbol> The message to retrieve the selected path in the tree.
  setSelected <Symbol> The message to set the selected item in the tree.
  getChildren <Symbol> The message to retrieve the children of an item
  hasChildren <Symbol> The message to query for children of an item
  label <Symbol> The message to query for the label of an item.
  icon <Symbol> The message to query for the icon of an item.
  help <Symbol> The message to query for the help of an item.
  menu <Symbol> The message to query for the tree's menu
  keyPress <Symbol> The message to process a keystroke.
  wantsDrop <Symbol> The message to query whether a drop might be accepted.
  dropItem <Symbol> The message to drop an item.
  enableDrag <Boolean> Enable dragging from this tree.
  autoDeselect <Boolean> Whether the tree should allow automatic deselection or not.
  unusedVar (unused) This variable is a placeholder to fix problems with loading packages in 3.10.!

Item was added:
+ ----- Method: PluggableTreeSpec>>doubleClick (in category 'accessing') -----
+ doubleClick
+ "Answer the selector for reacting to a double click"
+ ^ doubleClick!

Item was added:
+ ----- Method: PluggableTreeSpec>>doubleClick: (in category 'accessing') -----
+ doubleClick: selector
+ "Set the selector for reacting to a double click"
+ doubleClick := selector!


Loading...