Closed caius closed 15 years ago
culerity currently proxies almost all objects and then hands any method calls to the actual object sitting in the java process. you should be able to use the proxy object as if it was the actual array. if not then this really is a bug.
Pushed my fix http://github.com/caius/culerity/commit/ea713b8ee6cdea88e74b4597ba1c5282717602b9 which fixes it by returning the original array to start with.
the problem with your patch might be that when celerity returns an array of non primitive objects, then any method calls on those objects in the array would fail because they wouldn't be in the java process anymore. maybe checking recursively checking the contents of the array for their type would solve that.
fixed
I'm trying to get the list of
<option>
s in a<select>
. This is what currently happens:>> $browser.select_list(:id, "select_id").options => #<Culerity::RemoteObjectProxy:0x2158784 @remote_object_id=78, @io=#<IO:0x21a5fd4>
Testing using Celerity under
jirb
it should be returning an Array object.irb(main):020:0> b.select_list(:id, "select_id").options => ["One", "Two", "Three"]
What I expect is for Culerity to return the array Celerity is returning.