|
|
|
[
Permlink
| « Hide
]
Lex Neva added a comment - 06/May/07 08:21 AM
I'd use this a lot. Currently I keep my ti-86 close to hand whenever building.
YES YES YES YES YEEEEEEEEEEESSSSS! I have been longing for this feature for AGES!
Ditto on the calculator. Lightwave, and I guess many other 3D applications use this technique a lot and it's an absolute blessing. Another YES from this quarter
I'd like it if starting the field with an operator assumed that you wanted to apply the operator to the existing value.
Example: 1. Click the X position field. The math system assumes you mean to add 0.625 to the existing value. I guess this might collide with entering a negative value in the rotation boxes, though, won't it? :/ Could use X Y Z as shorthand for the existing values?
That way you could type X+0.625 in the X position field for example, or do things like typing X*1.5 in the Y scale box, to make it 1.5 times the current X dimension. I'm working on this and expect to have a patch "soon".
Have had this working nicely for a while now, just need to find time to clean it up and make the patch, RL keeps getting in the way :S
Thanks for the effort, Aimee, I hope you find time to make the patch.
One could use "=" at the start to mean take the current value and perform the rest of the expression to it. current value: 5.6 =+2 value changes to 7.6 This would allow the same character to work for all fields, such as hole size, twist, etc., not just x, y, and z. It would also resemble the syntax used for assignment operators in some programming and scripting languages. OK, I'm attaching a patch of it in its current state I know some people are eager to play with it
It's working great, though I think there are a few things left to do to get the best out of it, and it still needs some tidying up, but I'm just not getting the time to work on it at the moment and it would be good to get it out there at let people beat on it a bit and see what breaks. The main things still to do are: 1) Adding support for user variables, not a large amount of work, though needs a little UI consideration in how to manage them. 2) Right now the values for the system variables are pulled out from the build window when it updates, and the calculator is just active in any spin control. While this works well, I wasn't altogether comfortable with this hard coded approach as I was writing it, for log term manageability, and versatility in using it in other parts of the client. Soft Linden suggested managing it using the XUI to choose which input fields have the maths parser enabled, and also for labelling them with variable names, using callbacks to update the values when they change. That seems a much better approach than how I'm doing it at the moment (and a really obvious way of doing it now I thing about it If SL would support Mac OS X's Services API we'd get this for free on OS X.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Normal
Ability to do simple math in numeric edit fields
