[StevenChapmanParticipant]

Here it is with jQWidgets 9.1.6. I think it is the same:

unreachable code after return statement
jqx-all.js:23:67450
unreachable code after return statement
jqx-all.js:57:6240
unreachable code after return statement
jqx-all.js:81:35261
unreachable code after return statement
jqx-all.js:111:21308
unreachable code after return statement
jqx-all.js:111:28195
unreachable code after return statement
jqx-all.js:115:15542

[StevenChapmanParticipant]

Yes here is an example. This is with jQWidgets 9.0.0. Thank you.

unreachable code after return statement
jqx-all.js:23:67450
unreachable code after return statement
jqx-all.js:57:6240
unreachable code after return statement
jqx-all.js:81:35261
unreachable code after return statement
jqx-all.js:111:21308
unreachable code after return statement
jqx-all.js:111:28195
unreachable code after return statement
jqx-all.js:115:15336
unreachable code after return statement
jqx-all.js:115:15336

[StevenChapmanParticipant]

Martin,

Thanks. I think I’ve narrowed it down. I only see this problem on my 4K monitor which I have running at 3840×2160. When I run it on my other monitor I don’t see the problem.

Thanks,
Steve

[StevenChapmanParticipant]

Thank you for the response. Can I submit an enhancement request for this? Might it be included in a future release?

[StevenChapmanParticipant]

Peter,

Yes I see the fix in the new version, thanks for letting me know. We’ll upgrade. While this comment was critical, we are big fans of your widgets here at Boeing. Very impressive visually and affordable.

Thanks,
Steve

[StevenChapmanParticipant]

I’m well aware of how to use the noConflict function of JQuery. That’s how we’re using Prototype and JQuery in the same web app. I’m just pointing out to you that there is a single widget in your code that uses the global $ variable instead of scoping it locally, and could be fixed with a single character change. From jqx-all.js (3.5):

(function(a){a.jqx.jqxWidget("jqxPasswordInput","",{});a.extend...

(function(a){a.jqx.jqxWidget("jqxRangeSelector","",{});a.extend...

(function(b){b.jqx.jqxWidget("jqxDataTable","",{});b.extend...

(function(a){a.jqx.jqxWidget("jqxTreeGrid","jqxDataTable",{});a.extend...

(function(a){a.jqx.jqxWidget("jqxBulletChart","",{});a.extend...

(function(c){$.jqx.jqxWidget("jqxEditor","",{});$.extend...

(function(a){a.jqx.jqxWidget("jqxNotification","",{});a.extend....

Notice anything different about that jqxEditor line? I do. It’s using the global $ instead of the local c. This resulted in a JavaScript error even though I was using noConflict, until I moved the noConflict call to be after the jqwidget include. So yes, there is a workaround. I was just trying to be helpful by pointing out that if changed that “c” argument to “$”, no one would ever see this problem.

Thanks,
Steve

[StevenChapmanParticipant]

Peter,

This is unfortunate. If this is the case then the following page should be amended:

http://www.jqwidgets.com/jquery-widget-ui-documentation/documentation/introduction/introduction.htm

“The framework core provides fundamental capabilities like support for widget extensions and inheritance…”

Steve

[Author]

Posts