RE: [flexcoders] RemoteObject source="" bug?

[Matt Chotin]

Yeah, RemoteObject requires the classname to be set at compile-time in the tag, no binding allowed.  That’s a bug that it didn’t raise a compiler error.  In 2.0 we’re trying to allow a lot more runtime tweaking of all of our services including RemoteObject to allow things like this.   Matt   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Scott Barnes Sent: Monday, May 16, 2005 10:50 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] RemoteObject source="" bug?   Indy @ Straker noticed today that you can't use source="{binding.to.a.obj.value}" in mx:RemoteObject? In that it appears it ignores the fact that the curly braces are there and simply takes it as string value .. ie: call "{binding.to.a.obj.value}.doMethod()"  is the invocation attempt via Debug. I did find a a work-around in that you could do: function initRemoteObjectService() { // tricks the flex compiler. serviceID['__serviceName'] = binding.to.a.obj.value; } but seems dodge ? is it a bug or was that meant to be the case in terms of assigning dynamic values to the source attribute. -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com (Coming Soon) Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/   To unsubscribe from this group, send an email to: [EMAIL PROTECTED]   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.