[Closed] MAXScript dotNetController font help please
Your better then I thought Pete, you managed to answer three minutes before I asked:)
it’s weird, sometimes I get these flashes and I swear that I can see what is going on in your head. What those unicycling elephants and breakdancing monkeys are doing there I don’t know.
There ya go.
http://paulneale.com/tutorials/dotNet/button/button.htm#fontStyling
I’m not surprised that you can read my thoughts or that you saw the monkeys and elephants, I just surprised you thought they were more notable then the belly dancing pigmys wearing slippers, fez hats and nothing else.
i have to agree with marco in some sense
picking up dotNet… for me is not as simple as i thought it would be…
but its good to know that there is help here if i need it… thank you all again
It gets easier as you start to understand some of the logic behind it. It’s the same as everything, if you’ve grown accustomed to one kind of logic, it’s hard to get the hags of a different one. Happens to me every time I try to learn a new 3D app.
I have, humbly, to hop to the defense of Microsoft. (And that hasn’t always been my natural instinct).
.net is almost completely consistent, and rigorous. The seemingly convoluted and verbose ways of doing some things are there for good reasons, the result of careful design. On the whole, they are typical object-oriented strategies for avoiding code dependencies. They separate interface from implementation, facilitate re-use and economy with resources, and let you rewrite or extend sections of large applications with less chance of screwing up existing code, or introducing untraceable bugs.
Those strategies are, admittedly, a bit much for small programs, and scripting. And the bridge to MXS introduces some peculiarities. But they weren’t stoned when they wrote it!
The logic that makes it easier to get your head round it can be found in lots of references out there to OO design, or design patterns.