[JazzParticipant]

Haha. Actually, I just looked at the release date in the jqWidgets 3.2.1 source and it’s the 5th of Feb, which is the same date I posted my question.

You guys are sneaky. 😉

[JazzParticipant]

And so it is. I swear I checked the download section before posting this to make sure I was on the latest version and it was still 3.1.0 at the time.

All working again now on 3.2.1 though. Thanks.

[JazzParticipant]

Hi jqWidgeters.

How do I make an official support request for this problem?

I have an existing web app that uses the jqxSwitchButton quite extensively. Ironically it’s used a few times in my online support request form that my users can use to submit support requests, which is why no one has been able to report this issue to me until now.

I kinda need this fixed ASAP. I don’t like sounding needy and all that, but to implement your “workaround” would be a massive (and I mean MASSIVE) pain in the tookus.

Pweeaaassee!!?!?! 🙂

Jamie

[JazzParticipant]

Any updates on this at all? I’ve just hit the same problem again and need to know if there’s a workaround.

Thanks.

Jamie

[JazzParticipant]

Ah, of course. I should use the ‘change’ event. I just got a little lost in the demo documentation and didn’t see that. Thanks Peter.

[JazzParticipant]

Peter, yeah, the ‘tt’ shouldn’t be there. However using just ‘F’ I still get the same problem. Pasting your above code in worked for me so I found the problem.

Turns out my helper function, which generates the Javascript code for me, was adding “{ value : null }” to the parameters passed to the jqxDateTimeInput function and that is what was messing things up.

So, THIS is bad:

$("#jqxWidget").jqxDateTimeInput({ width: '250px', height: '25px', formatString: 'F', value: null });

Guess I had just been staring at it too long yesterday. All sorted now.

Thanks,

Jamie

[JazzParticipant]

This is what it looks like for me:

https://www.dropbox.com/s/6cgay88fwdsi82d/Screenshot%20from%202013-10-15%2009%3A51%3A31.png

So it’s supposed to look like that? Just seems strange that it shows as 3 individual buttons instead of, you know, a button group like all the other themes do…

But, if that’s what it’s meant to look like, then ok then…

J

[JazzParticipant]

Um, that’s not exactly the behaviour I’m seeing. The dynamic elements are definitely appended to the end of the document. I have also found in the JavaScript source references to $.appendTo(document.body), which is why I created this thread because I can see this as the cause of my problems.

And yeah, they may be destroyed if I call the ‘destroy’ method on the widget itself, but if I call clear() on the containing DIV (for example), or in my specific case I call load() to load new content, the elements are NOT destroyed.

I suppose my work-around would be to call ‘destroy’ on all widgets BEFORE calling clear() or load() but that’s going to be a stack of code. In my opinion it would just be better if the widgets didn’t blindly append stuff to the end of the document and kept their dynamic elements either inside the host element or at least at the same level on the DOM so that if I call clear(), everything is just dealt with.

[JazzParticipant]

Ah ha! Didn’t realise I was still on 2.8.3 on this system.

Yes, 2.9.2 does not have this problem. Simply updating the jqWidgets libs fixed my problem.

Thanks Peter.

[JazzParticipant]

I can confirm this as well as I just hit this exact same problem.

I have a tree list that gets updated with new items and has items removed. I also have a ‘counter’ that displays the number of items in the tree. (we’re processing inbound document queues).

I get the number of items like so:

var itemCount = $('#doclist').jqxTree('getItems').length;

After removing an item from the tree and executing the above line of code again, the value does not change. Further investigation shows that the array of items returned by getItems() still contains the items that I removed with removeItem() even though the items are removed from the list correctly.

Jamie

[JazzParticipant]

Well…

I’m done. 🙂

Peter, if you want to check out the widget and make sure it’s working for you as well, that would be great. Demo page is now at http://www.hazaarmvc.com/test (there’s a redirect on the old URL anyway).

I have tested in IE7/8/9/10, Firefox, Chrome, Opera and Safari and all seem to be working consistently.

I’ve also knocked up some demos and I’ve just finished putting together an API page right now. It gives a general idea of what parameters, methods and events are available.

I’m not sure how to handle the logistics of the widget from here though. Meaning whether I host and maintain or you integrate it into the main library. Happy to discuss. 🙂

[JazzParticipant]

Almost done! Notable changes since last update:

* jqxEditor is now theme happy! 🙂
* Finished the image browser.
* Changed the color picker tool buttons to something a lot neater/fancier (removed the hex display).
* Added a modechange event for when the edit mode changes. This has allowed me to send a server request to ‘tidy’ the HTML before displaying it.
* Bit of code clean up

All that’s left, really, is some IE fix-ups, testing and then writing up some documentation for it and adding a couple more demos. Stay tuned. 🙂

[JazzParticipant]

Nevermind. I dove into the jqxbuttons.js source and found that jqxToggleButton has ‘check’ and ‘unCheck’ methods available. They really should be in the API docs as they are incredibly useful. Solved my problem.

Still wouldn’t mind there being a way to get the current state though. Maybe an ‘isChecked’ or ‘isToggled’ method can be added. Looking at it all that needs is a method to return the value of ‘this.toggled’. Essentially one line of code. Feature request? 😉

[JazzParticipant]

It doesn’t, really.

What I was talking about was having something like this as the data source:

localdata = {
    "h1" : "Header 1",
    "h2" : "Header 2",
    "h3" : "Header 3",
    "h4" : "Header 4",
    "h5" : "Header 5",
    "h6" : "Header 6",
    "p" : "Paragraph",
    "pre" : "Preformatted"
};

It appears that there’s no mechanism to handle this type of data source.

I have, however, figured out a relatively simple solution. For those looking for how to do the same:

$('#list').jqxDropDownList( {
    source : $.map(localdata, function(val, key){ return { label : val, value : key }; });
    displayMember : 'label',
    valueMember : 'value'
}

I believe the displayMember and valueMember parameters aren’t actually required as it seems that if they are ‘label’ and ‘value’ respectively, then they “just work”.

[JazzParticipant]

Major update today. I decided to build in a cool little image browser. The simple image dialog is still available, but if you supply the imageBrowser parameter with a dataAdapter object, you can use the built-in browser.

Still needs some work, but I wanted to show it off. Check it out: http://www.hazaarmvc.com/site/test

Just click in the text somewhere and insert an image. A window will pop up with a bunch of images to choose from that are loaded via the dataAdapter.

No support for folders or uploads yet, but that’s coming. I also have no idea how it will go in IE just yet.

[Author]

Posts