For example:
findString “Thanks for all the fish!” “all” – returns 12
Found this in the string values help file – I guess this is a reference to “so long and thanks for all the fish” from The Hitchhiker’s Guide to the Galaxy, and not a reference to the unique remuneration methods used at Autodesk.
I think that this would be Bobo humour.
I think it was there before I started editing the docs. Which means that one of the previous editors, most probably John Wainwright himself, must have been a fan, too.
This of course does not mean that I am not one of the biggest fans of The Guide – I can quote it in 3 different languages!
I really do appreciate the subtle humour all the way through the maxscript doc.
Maxscript isn’t exactly a roller-coaster ride of fun, so you need to inject humour into it somehow.
Mind you, I recall doing a COBOL programming course when I was a teenager – first bit of programming me or my buddy learned. The teacher told us we could name our variables anything – so we used “batman” and “superman”, it was our second lesson after all.
“BULLSHIT! this is BULLSHIT!” he comletely lost it. Clearly he wanted us to give them meaningful names. I swear all the program did was add two numbers together.
To this day whenever I call a temporary variable “arse” I feel I am striking a blow for freedom.
It’s all in the name of fun:
filterString "MAX Script, is-dead-funky" ", -"
[left]would return
[color=blue]#("MAX","Script","is","dead","funky")
[/color]
[/left]
and a old time favorite:
[b][b][color=white][b]He is dead, Jim[/b][/color][/b][/b][left]polyOp.[b][b]isFaceDead[/b][/b] <Poly poly> <int face>
Returns true if the specified face is dead.
polyOp.[b][b]isEdgeDead[/b][/b] <Poly poly> <int edge>
Returns [b][b]true[/b][/b] if the specified edge is dead.
[/left]
Keep up the good work Jim, er Bobo
J.And Bobo please don’t try and blame this on on poor John as well!
theHuman = Bulgarian() [color=green]--create an instance of the class Bulgarian[/color]
[left]theHuman.name = [color=maroon]"Bobo"[/color][color=green]--[/color][color=green]give it a funny name[/color]
print (superclassof theHuman)[color=blue]
--[/color][color=blue]> HumanBeing[/color]
if theHuman.location == [color=maroon]"Winnipeg" [/color][color=blue]do[/color]
theHuman.isFrozen = true[color=green]--[/color][color=green]set some properties based on object's location[/color][color=green]
--[/color][color=green]Now you have a single instance you can call a method [/color][color=green]
--[/color][color=green]that expects an object of the superclass HumanBeing:[/color]
Kiss theHuman
[/left]
My class has changed. My constructor is now Austrian().
Still in Winnipeg though…
Oh, and that was pseudo-code I originally posted to the Max Support Forum
I am currently working the Maxscript mother of all loops, estimated to take seven and a half million years of serious cogitation and arrive at 42
and we wonder why 3dsmax so often crashes…