Setting scripting names with [thispatcher]

honeystick

When making new objects with [thispatcher] and message [script newobject (object name here) @varname $1], whenever I write in a UI object, this sets the scripting name correctly. But if it's not a UI object, the scripting name isn't set in the objects inspector. Does anyone know what's going on here? How can I set the scripting name for non-UI objects with [thispatcher]? Can I set the scripting name for abstractions generated by [thispatcher]?

[ezdac~] generated by [thispatcher] correctly has it's scripting name set in the inspector

[dac~] generated by [thispatcher] does not have it's scripting name set.

Roman Thilenius

>>Does anyone know what's going on here?

that comes from times when UI objects were the only ones you could script-create... that is also why you use different commands for them (newobject vs newdefault)

about the "argument not working", no idea. i personally would never use @attributes to objects in thispatcher scripting. giving the new obejct a scripting name is part of the scripting grammar already.

honeystick

thanks! that helps a ton, i didn't realize there was a difference between newobject and newdefault