[justin.mannParticipant]

apologizes,

Moments after I complained loudly I found the uncompressed code I was looking for.. Too many windows open and apparently too much coffee.. Please ignore .src contains appropriate versions of all scripts. anyone having issues of this nature and you are sure all your dependencies are in place correctly please do test with uncompressed code as it will help alleviate any environmental issues script staging or other complicated environmental enhancements may introduce to the mix.

Happy coding,
Justin

[justin.mannParticipant]

I am having a similar issue with jqxwindow.js lib actually.. Admittedly my environment is a little wonky as I am working with a Domino server on the back end. I believe most of the issues I have are exclusively related to environment and script staging (I won’t even get into this bit), but what I have found is I have much greater success by simply avoiding the compressed versions of the scripts. (Hopefully this helps your situation san1646, if you have an older script loader or you are staging your scripts in a db this may help smooth things out, not really these folks issue if that is what is going on… just avoid minified scripts.) This is what brings me here today.. as I stated I am having issues with the compressed jqxwindow.js file… We have an enterprise license… we have bought one for the last couple years since I started working here (this is on my recommendation). So, in the past I have found little issue with getting dev or uncompressed code, I need this. Am I missing something? I have dug thru the src and public versions of the zips??? I was under the impression this is part of what we are paying for? Please advise. Where can I get these items, please don’t tell me you no longer make them available… I am worried this is the case and that will make no one happy here including me. I love your product and would continue to keep using it, but if it is consistently difficult to do simple update in this environment what are we paying for? Sorry to express concern before I have a resolution from you, just wanted to get it all out there, unrealistic concerns (I hope) and all…

I don’t want help troubleshooting, I want uncompressed code… that is all. please and thank you.

I will continue to look around, simple thing guys, I don’t think I should ‘still’ be looking, hope it is here and if it is not I hope you realize you are selling product to DEVELOPERS TOO, developers write and modify code, compressed code is not appropriate for us…

Justin Mann

[justin.mannParticipant]

Problem solved…

I invoked the render after changing the value of ‘columnsreorder’.

here is the fiddle illustrating the working behavior…
http://jsfiddle.net/justinmann_fiddle/Pr4Js/3/

I believe this was due to the fact that the columnsreorder functionality comes from an extension of the grid… I have no idea really, but I noticed that if I forced my condition where the columns were initialized to be reorderable, then I triggered my condition that should cause them to be UN-orderable (they were still reorderable at this point, which was my original problem), finally I triggered my condition in which they were supposed to be reorderable again (at this point they were UN-orderable). It was as if the grid was one step behind what I wanted it to do so first I tried to simply ‘refresh’ the grid, this did not work so I invoked the ‘render’ method immediately after changing the ‘columnsreorder’ property value and it works like a charm.

Thanks for any time you spent looking at this, and hopefully this is of use to someone down the line.

I don’t know if this is intended behavior, but from the documentation the need to invoke the ‘render’ method after changing this particular property was unclear to me. I have other properties I change on the fly conditionally in the same grid framework and they do not require this.

Not taking anything away from u folks, great product.

Appreciatively,
Justin Mann

[justin.mannParticipant]

In addition, I am using grouping in the grid solution so one work around I thought about and tested is out the window…

I thought it clever (but perhaps slower) to simply loop thru the current column datafields and pin the columns…
i.e. –

var columns = $(“#searchresults”).jqxGrid(‘columns’).records;
for(i=0;i<columns.length;i++){
$(‘#searchresults’).jqxGrid(‘pincolumn’,columns[i][‘datafield’]);
}

Apparently this is not a viable option due to the solution using grouping… I do find it odd that pinning the columns works fine in my solution, It is the unpinning of the columns that generates errors to the point that pinning of columns is not a viable option when using grouping…
i.e. –
var columns = $(“#searchresults”).jqxGrid(‘columns’).records;
for(i=0;i<columns.length;i++){
$(‘#searchresults’).jqxGrid(‘unpincolumn’,columns[i][‘datafield’]);
}

As stated this is just a work around I thought might get the job done, I’m not intending to confuse the issue.

Justin

[justin.mannParticipant]

Thanks for the attention Peter,

I am not sure what is going on here, I do have more input, but really at this point I think just sending u the full code segment makes more sense. Since I am translating XML via jQuery to feed this beasty I could easily provide that as well (thank goodness for the xml translation that takes place on the server as the datasource behind it is Domino and I have my doubts about u having a Domino instance at your disposal… lol).

I think before I bother you any more with this I am going to download the latest source for the newer version and test with it even tho I didn’t see any outstanding problems from the research I have done and no changes in the change log that would address any of this. I do appreciate your time and may very well be back on the forum in the near future either with a source to my mysterious issue or with full code so you can recreate the issue.

Thanks again Peter,
J

[Author]

Posts