jQWidgets Forums

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Changing theme in parent Changing theme in parent #77536

    OrchidDeveloper
    Participant

    Thank you very much Ivailo.

    Your suggested workaround does the trick. I hope you address this bug in one of your future releases.

    Best regards.

    in reply to: Changing theme in parent Changing theme in parent #77467

    OrchidDeveloper
    Participant

    Hi Ivailo,

    Unfortunately, your suggestion doesn’t work. I have updated the original jsFiddle, so you can see it yourself.

    By the way, as I mentioned in my first post, the origin of this TypeError is in setTheme() function (file: jqxcore.js, line: 886). There you are trying to split className of DOM element.
    var classNames = element[0].className.split(' ')
    In case of jqxGauge (or jqxChart) widget, one of child elements has SVGAnimatedString object as className and it doesn’t have split() method.

    If you still think initialising jqxGauge in initContent callback will solve this problem, kindly provide a jsFiddle that demonstrates this.

    Regards.

    in reply to: Changing theme in parent Changing theme in parent #77418

    OrchidDeveloper
    Participant

    Hi there,

    Any chance to get some feedback on this any time soon?

    Thanks.

    in reply to: Changing theme in parent Changing theme in parent #77271

    OrchidDeveloper
    Participant

    Hello Ivailo,

    I was able to create a minimal html/javascript code to demonstrate the issue. Please refer to the following jsFiddle
    https://jsfiddle.net/ezbLccu0/2/

    The gauge is inside navigation bar, which is inside a splitter.

    Regards.

    in reply to: Changing theme in parent Changing theme in parent #77250

    OrchidDeveloper
    Participant

    Ivailo,
    Thank you for quick response.

    You are right, the demo sample you provided doesn’t throw any exception. The only thing is that your sample is using jQuery v1.10 and I am using v1.11.3, but I don’t see how this could break it.

    I’ll try to simplify the code here to see if it makes any difference. Will get back to this thread if I find the cause.

    Regards.

    PS
    Great stuff these widgets by the way.

Viewing 5 posts - 1 through 5 (of 5 total)