|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| − | | + | I would suggest ordering the kinds of requests that people have under a few subheadings. Any objections? [[User:Jgrellier|Jgrellier]] 05:46, 28 November 2007 (PST) |
| − | | |
| − | == * Spring loaded modules ==
| |
| − | | |
| − | Spring loaded modules are a user interface feature that would allow a modeler to grab an object(s) and hold it over a module. The module would respond by opening up the module window so that the selected objects could be placed immediately in the desired location. This would prevent having to open the module prior to dragging and dropping; or dropping the objects into the module, then opening the module to place the objects where I want them. The spring loaded modules simply save a few clicking and dragging steps.
| |
| − | | |
| − | Rob Brown
| |
| − | rbrown@decisionstrategies.com
| |
| − | | |
| − | == ** Index Derivation from Table ==
| |
| − | | |
| − | A function that found the unique elements of an n-dimensional table and then created an index from these elements. For example, let A be a 1D table of numbers such that
| |
| − | | |
| − | A := Table(someIndex)(4,1,4,2,6,6,13,2,5,)
| |
| − | | |
| − | Then thisIndexFunction(A) --> Index := [1,2,4,5,6,13]
| |
| − | | |
| − | Numerical elements should default to increasing value, and text elements should default to increasing alphabetical order, but an optional flag should be given to reverse the order.
| |
| − | | |
| − | This could potentially be a dynamically changing index. Proper alerts to this condition should be noted.
| |
| − | | |
| − | Rob Brown
| |
| − | rbrown@decisionstrategies.com
| |
Latest revision as of 13:46, 28 November 2007
I would suggest ordering the kinds of requests that people have under a few subheadings. Any objections? Jgrellier 05:46, 28 November 2007 (PST)
Enable comment auto-refresher