Broken bridge communication under SU2014 #59

noelwarr · 2013-09-20T14:31:18Z

I have a window with a button with an on-click callback. The call back looks at the values of a few controls. It is uppon checking these values that an error is thrown:

Error: #<SKUI::Bridge::CommunicationError: Unknown error. Ensure DOM is ready.>

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

thomthom · 2013-09-20T16:01:43Z

Can you post the source for that dialog? You can use gist or something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call back looks at the values of a few controls. It is uppon checking these values that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

noelwarr · 2013-09-20T16:09:27Z

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a few
weeks behind yours and you had some problems with listbox.value() so I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call back
looks at the values of a few controls. It is uppon checking these values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is returning
false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24820933
.

thomthom · 2013-09-20T16:26:38Z

Yea. I recently pushed some code that affected the bridge. Pull the latest changes and see if it comes back.

See you in Lisbon! Awesome!

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a few
weeks behind yours and you had some problems with listbox.value() so I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call back
looks at the values of a few controls. It is uppon checking these values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is returning
false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24820933
.

—
Reply to this email directly or view it on GitHub.

noelwarr · 2013-09-20T16:35:15Z

https://gist.github.com/noelwarr/47c9d1df1064a1f60e5e

I'm pretty sure it must be a timing problem with ruby/js because the
following edit in bridge.js fixes the problem

 /* Returns the value for the given jQuery selector.
 */
get_value : function( selector ) {
  alert();//pausing here a second fixes problem
  return $(selector).val();
},

If it is a timing thing it'll be difficult to reporduce on another machine
as the differences if SketchUp and JSVM speed will either fix the problem
or make it worse.

2013/9/20 Noel Warren noelwarr@gmail.com

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a few
weeks behind yours and you had some problems with listbox.value() so I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call back
looks at the values of a few controls. It is uppon checking these values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is
returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24820933
.

thomthom · 2013-09-20T17:07:09Z

The bridge should take care of the async nature of js to ruby. There should be no need for timing.
Did you try with the latest SKUI?

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

https://gist.github.com/noelwarr/47c9d1df1064a1f60e5e

I'm pretty sure it must be a timing problem with ruby/js because the
following edit in bridge.js fixes the problem

/* Returns the value for the given jQuery selector.
*/
get_value : function( selector ) {
alert();//pausing here a second fixes problem
return $(selector).val();
},

If it is a timing thing it'll be difficult to reporduce on another machine
as the differences if SketchUp and JSVM speed will either fix the problem
or make it worse.

2013/9/20 Noel Warren noelwarr@gmail.com

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a few
weeks behind yours and you had some problems with listbox.value() so I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call back
looks at the values of a few controls. It is uppon checking these values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is
returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24820933
.

—
Reply to this email directly or view it on GitHub.

noelwarr · 2013-09-20T18:25:24Z

Yup
El 20/09/2013 19:07, "Thomas Thomassen" notifications@github.com escribió:

The bridge should take care of the async nature of js to ruby. There
should be no need for timing.
Did you try with the latest SKUI?

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

https://gist.github.com/noelwarr/47c9d1df1064a1f60e5e

I'm pretty sure it must be a timing problem with ruby/js because the
following edit in bridge.js fixes the problem

/* Returns the value for the given jQuery selector.
*/
get_value : function( selector ) {
alert();//pausing here a second fixes problem
return $(selector).val();
},

If it is a timing thing it'll be difficult to reporduce on another
machine
as the differences if SketchUp and JSVM speed will either fix the problem
or make it worse.

2013/9/20 Noel Warren noelwarr@gmail.com

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a
few
weeks behind yours and you had some problems with listbox.value() so
I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed
the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or
something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call
back
looks at the values of a few controls. It is uppon checking these
values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is
returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub<
https://github.com/thomthom/SKUI/issues/59#issuecomment-24820933>
.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24825382
.

thomthom · 2013-09-20T19:28:16Z

I'll look at it next week. I'm out travelling the whole weekend.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

Yup
El 20/09/2013 19:07, "Thomas Thomassen" notifications@github.com escribió:

The bridge should take care of the async nature of js to ruby. There
should be no need for timing.
Did you try with the latest SKUI?

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

https://gist.github.com/noelwarr/47c9d1df1064a1f60e5e

I'm pretty sure it must be a timing problem with ruby/js because the
following edit in bridge.js fixes the problem

/* Returns the value for the given jQuery selector.
*/
get_value : function( selector ) {
alert();//pausing here a second fixes problem
return $(selector).val();
},

If it is a timing thing it'll be difficult to reporduce on another
machine
as the differences if SketchUp and JSVM speed will either fix the problem
or make it worse.

2013/9/20 Noel Warren noelwarr@gmail.com

A few things: This problem is coming and going for me. Makes me think
it's a timing thing with the bridge. I just realised that my repo is a
few
weeks behind yours and you had some problems with listbox.value() so
I'll
update and experiment a little more.

I thought I had filed an issue with SKUI on github. Must have pressed
the
wrong button. I have my Lisboa ticket!

2013/9/20 Thomas Thomassen notifications@github.com

Can you post the source for that dialog? You can use gist or
something.

Sent from my Sony Xperia™ smartphone

Noel notifications@github.com wrote:

I have a window with a button with an on-click callback. The call
back
looks at the values of a few controls. It is uppon checking these
values
that an error is thrown:

Error: #

A little further investigation seems to indicate that

Bridge.execute("Bridge.get_value("#UI_81846250 select");") is
returning false, when it shouldn't. Any ideas?

This was working quite well under SU2013

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub<
https://github.com/thomthom/SKUI/issues/59#issuecomment-24820933>
.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24825382
.

—
Reply to this email directly or view it on GitHub.

thomthom · 2013-09-22T19:05:20Z

Can you supply a working self contained example?

When I try to load that gist I just get errors.

w = Vistii::GUI.initialize_main_window
Error: #<NameError: c:/gistfile1.rb:158:in `initialize_main_window': uninitialized constant Vistii::PATH>
c:/gistfile1.rb:158
(eval):46

thomthom · 2013-09-22T19:10:41Z

Ok, worked around it by commenting out the image. But I'm not seeing the same error as you. I find a different one.

Can you describe exactly the steps that lead up to that error?

noelwarr · 2013-09-23T07:08:33Z

Hi Thomas

Thanks for taking the time to look into this. I'm trying to put together a
working example but the problem with my working example is its working. So
it looks like I might have structured something badly in my project, though
I can't figure out what.

Anyway, just to let you know I'm working on it. I'll write back later.
Cheers

2013/9/22 Thomas Thomassen notifications@github.com

Can you supply a working self contained example?

When I try to load that gist I just get errors.

w = Vistii::GUI.initialize_main_window
Error: #<NameError: c:/gistfile1.rb:158:in `initialize_main_window': uninitialized constant Vistii::PATH>
c:/gistfile1.rb:158
(eval):46

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24888170
.

noelwarr · 2013-09-23T09:08:05Z

It seems I HADN'T correctly pulled from your repo. God damn it.[image:
Imatge en línia 1]

2013/9/23 Noel Warren noelwarr@gmail.com

Hi Thomas

Thanks for taking the time to look into this. I'm trying to put together
a working example but the problem with my working example is its working.
So it looks like I might have structured something badly in my project,
though I can't figure out what.

Anyway, just to let you know I'm working on it. I'll write back later.
Cheers

2013/9/22 Thomas Thomassen notifications@github.com

Can you supply a working self contained example?

When I try to load that gist I just get errors.

w = Vistii::GUI.initialize_main_window
Error: #<NameError: c:/gistfile1.rb:158:in `initialize_main_window': uninitialized constant Vistii::PATH>
c:/gistfile1.rb:158
(eval):46

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24888170
.

thomthom · 2013-09-23T10:28:08Z

Is it working ok now?

noelwarr · 2013-09-23T13:48:20Z

Yeah. Sorry for the bother. Everything is working a charm. Looks like
I'll have to brush up on my GIT skills.

2013/9/23 Thomas Thomassen notifications@github.com

Is it working ok now?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-24910602
.

thomthom · 2013-09-23T13:56:10Z

No worries. I did find some other bug that I fixed. :)

thomthom closed this as completed Sep 23, 2013

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Broken bridge communication under SU2014 #59

Broken bridge communication under SU2014 #59

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

thomthom commented Sep 22, 2013

thomthom commented Sep 22, 2013

noelwarr commented Sep 23, 2013

noelwarr commented Sep 23, 2013

thomthom commented Sep 23, 2013

noelwarr commented Sep 23, 2013

thomthom commented Sep 23, 2013

Broken bridge communication under SU2014 #59

Broken bridge communication under SU2014 #59

Comments

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

noelwarr commented Sep 20, 2013

thomthom commented Sep 20, 2013

thomthom commented Sep 22, 2013

thomthom commented Sep 22, 2013

noelwarr commented Sep 23, 2013

noelwarr commented Sep 23, 2013

thomthom commented Sep 23, 2013

noelwarr commented Sep 23, 2013

thomthom commented Sep 23, 2013