MDX Feature Requests

jimp · 04-16-2008, 04:29 PM

Just a thought that popped into my head while reading this thread,

Is it possible to have a call to a windows function, script, or other program within or as a result of the logic? I don't really have anything in mind for this but thought it might be handy to say if inputA =x and inputb=Y then run script.

2k1Toaster · 04-16-2008, 04:34 PM

Good idea. Never thought about that.

greenman100 · 04-17-2008, 02:55 AM

MDX Feature Requests

Is it possible to have a call to a windows function, script, or other program within or as a result of the logic? I don't really have anything in mind for this but thought it might be handy to say if inputA =x and inputb=Y then run script.
AutoSave/AutoRecover

h3rk · 04-22-2008, 09:30 PM

I would like to have it so that (in the 'then' portion of an if/then loop) the value of one variable can be assigned to another variable. i.e if x==y,then b=a. Currently it can only be if x==y, then b=4 (or some other numeric value). I hope that's not too hard to do.

I'm also wanting long term variable storage, for remembering variables calculated in runtime.

h3rk · 04-26-2008, 02:40 PM

I'd like to have an "order of processing" field for each of the root functions, to allow skin designers (me in this case

) to have the ability to decide in which order the loops would be processed, independendant of the order that they sit in the skin, where maybe they would be re-ordered when read in by the software at startup. No big hurry on this one, if you do decide to do it, because obviously, by rearranging the skin, I can get by.

2k1Toaster · 04-26-2008, 02:42 PM

Quote: Originally Posted by h3rk

I would like to have it so that (in the 'then' portion of an if/then loop) the value of one variable can be assigned to another variable. i.e if x==y,then b=a. Currently it can only be if x==y, then b=4 (or some other numeric value). I hope that's not too hard to do.

I'm also wanting long term variable storage, for remembering variables calculated in runtime.

Quote: Originally Posted by h3rk

I'd like to have an "order of processing" field for each of the root functions, to allow skin designers (me in this case

) to have the ability to decide in which order the loops would be processed, independendant of the order that they sit in the skin, where maybe they would be re-ordered when read in by the software at startup. No big hurry on this one, if you do decide to do it, because obviously, by rearranging the skin, I can get by.

Both very good. Both will be used. Thanks again h3rk!

User Name		Remember Me?
Password