[emberqParticipant]

Today 4/1, my JQWidgets app is having a problem on Chrome. I’m still on JQWIdgets 5.4.0. I will try to upgrade. But can this deprecation (discussed above) possibly impact my 5.4.0 app?

[emberqParticipant]

Hi Hristo,

Thanks for your follow-up. This is important to me because it’s a key feature of my app that enables my clients to create e-mail lists of their own clients.

Anyway, I’m not using cellsrenderer for that column or any other column that is participating in this grid and this export. So I appreciate the hidden column idea and I do use hidden columns in other grids, but this is not that problem.

Is there some way you can check your logs on that export server to assist with this? For example, I’d like to know if the email addresses from that column are indeed being sent to your server. I know for a fact they’re not coming back.

[emberqParticipant]

Thanks but this is not a solution. It’s not centered absolutely on the screen and it really only seems left to right centered because your button is centered on the screen.

Is there a way to position the jqxpopover absolutely on any screen at the center, irregardless of where the trigger element is located?

[emberqParticipant]

I created this Fiddle: https://jsfiddle.net/emberq/p9bezk85/

I eliminated virtually all of my window properties but let’s see if you can run this using 5.5.0 and just click the dropdown. See if the window closes. If the window doesn’t close then there is some option I’m using on the window or the drop down that is causing this behavior. Again, this worked fine for all version of JQWidgets prior to 5.5.0. I really could use a public URL pointing to 5.5.0 so I can reproduce this myself using this widget rather than getting you involved because this is really a shot in the dark.

Thank you.

[emberqParticipant]

It’s not any fiddle that needs to be updated, or maybe it does. I was pointing out that this public URL: http://jqwidgets.com/public/jqwidgets/jqx-all.js is not on the latest version.

So I”m just asking for help in how to set up my new fiddle properly by pointing it to a public URL that contains 5.5.0? Not a download.

[emberqParticipant]

This should be easy to reproduce but I’m going to create a fiddle to show it. But where can I point to a public version of 5.5.0? The version at http://jqwidgets.com/public/jqwidgets/jqx-all.js is still on 5.4.0.

Has 5.5.0 actually been released to the public? If so why isn’t that public link updated?

[emberqParticipant]

Thank you. The solution I used is:

var index = $(“#grid).jqxGrid(‘hoveredrow’);
var rows = $(“#grid).jqxGrid(‘getdisplayrows’);
var rowData = rows[index];

The method ‘getdisplayrows’ was key to getting the right index that takes into account grid sorting of rows.

[emberqParticipant]

Sorry – my mistake it is working.

One question, however: My grid has an aggregate total in two columns but that does not appear in the PDF. Is there some way I can include that?

[emberqParticipant]

I’m using this: jquery-3.1.1.min.js

which I assume is OK, thanks.

[emberqParticipant]

Yes I have sortable true. That is my intent. When I hover over the column that small menu icon appears in from the right but clicking it doesn’t do anything. I just wanted to know what purpose the icon serves.

[emberqParticipant]

Solved.

My issue was that in my Node.js Express web app I wanted to pin the version of jqwidgets-scripts in package.json, and I wanted to access jqwidgets in the browser from node_modules on the server.

1. I pinned jqwidgets-scripts on 5.4.0 and ran npm update. That gave me node_modules/jqwidgets-scripts.
2. In app.js I added this line: app.use(‘/jqwidgets/’, express.static(path.join(__dirname + ‘/node_modules/jqwidgets-scripts/jqwidgets/’)));
So with the other dependencies in app.js, it looks like:
var express = require(‘express’);
var path = require(‘path’);
app.use(‘/jqwidgets/’, express.static(path.join(__dirname + ‘/node_modules/jqwidgets-scripts/jqwidgets/’)));
3. In my index.html where I load all js scripts, I have this:
<link rel=”stylesheet” href=”/jqwidgets/styles/jqx.base.css” type=”text/css” />
<script type=”text/javascript” src=”/jqwidgets/jqx-all.js”></script>

This works. Now I can deliberately upgrade my production app to a specific jqwidgets version by just changing the npm dependency.

Thanks for steering me in the right direction.

[emberqParticipant]

In Node.js I have publicly accessible resources like .js and .png in my public area and then node+modules which is not publicly accessible. SO I can’t just access the jqwidgets pacjage using a relative path. I’m a bit stuck. Do I need bower or browersfy or should I be able to do this with npm alone?

[emberqParticipant]

OK I’m getting there with your help but if I specify an npm release then yes the package will exist in node_modules but that will be server-side in my app. How do I then address jqx-all as a script in my html? Something comparable to this: http://jqwidgets.com/public/jqwidgets/jqx-all.js?

[emberqParticipant]

OK, thanks. Is there some way to iterate through jqx controls on a tab, or any container? This is because all my tabs are different and I don’t currently know the characteristics of any one that might be ‘x’d out. It’s also difficult because the the tab index of the current tab changes as other tabs are closed or re-positioned. It would be great to just be able to iterate the tab for which that event just fired, find jqx controls and destroy them.

[emberqParticipant]

I am using node.js so if I was to use npm to install a particular jqwidgets release, how would I address that library client side in my html – e.g. <script src=”https://code.jquery.com/jquery-3.1.1.min.js”></script>? Also, that would not be minified, right?

I’m trying to come up with a best practice for deploying my node.js, jqwidgets web app where I can pin a version and then if I want to upgrade I can test with a newer release before adopting it in production. If I just point to the public, minified jqx-all, my users are going to get every update you make automatically without my pre-testing.

Thank you.

[Author]

Posts