Forum Replies Created

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts

  • Gary
    Participant

    Thank you!


    Gary
    Participant

    Ok, I looked at the example you provided. It does not address the issue I raised.
    Specifically, if I change your example to included time in the min date and extend the overall date range, the same issue appears.
    http://jsfiddle.net/GaryGen/997wxkv7/2/


    Gary
    Participant

    Thank you for the workaround.

    I’m encountering this in 4.1.1 and I think I located actual problem.

    Walking the minified code, _showTooltip in jqxslider.js calls g.tooltipFormatFunction and stores the result.
    However, if g.toolTipCreated is true and g.rangeSlider is true, the result does not appear to ever be used.

    Offhand, if the user tooltipFormatFunction returns a result, that should be used rather than generating a tooltip internally.


    Gary
    Participant

    I’m encountering this in 4.1.1. It appears to be specific to the range slider.

    Walking the minified code, _showTooltip in jqxslider.js calls g.tooltipFormatFunction and stores the result.
    However, if g.toolTipCreated is true and g.rangeSlider is true, the result does not appear to ever be used.

    (Actually, I just realized this is a separate issue from the original Angular non-range report, will open a new item.)

    • This reply was modified 7 years, 4 months ago by  Gary.

    Gary
    Participant

    Thank you for providing a workaround. I will see if I can incorporate the concept in my code.


    Gary
    Participant

    I reported this in 2015. However, this appears to still be unchanged as of the November 2016 release.

    Unfortunately, this seems to make the RangeSelector ticks relatively unusable unless the min/max/interval is wrapped in logic to keep the proportions such that it does not happen.

    Here is another example:
    http://jsfiddle.net/GaryGen/Lf6AN/20/

    Are there any plans to fix this in the near future?

    -Gary


    Gary
    Participant

    Three months later and I was going to make the same comment. 🙂

    • This reply was modified 7 years, 6 months ago by  Gary.

    Gary
    Participant

    Hi Peter,
    My issue is that visually, this is what I’m seeing:

    [(Select All),alpha,beta,gamma,delta v]
    [x] (Select All)
    [x] alpha
    [x] beta
    [x] gamma
    [x] delta

    What I want to see on the top line is:
    [alpha,beta,gamma,delta v]

    Since the text of the DropDownList is auto-generated based on the checklist selection, I would like to override that auto-generated text to not include “(Select All),”. The setContent() method appears to correctly update the text, but the auto-generated text is overwriting my value in some cases. Setting it on a subsequent event (like on close) does not get overwritten.

    So I think my question is, can I turn off the auto-generation of the text, override the text generator, or be given a better idea of what specifically triggers the text to be updated so that I can try to ensure I call setContent() after it is called. I’ve tried updating at the end of the change, select, checkchange, and unselect events, but the auto-generate still occurs afterwards.

    Best Regards,
    -Gary Geniesse

    in reply to: Modifying Layout properties Modifying Layout properties #83298

    Gary
    Participant

    Hi Dimitar,

    Thanks for the quick reply.

    Just to verify I understand the approach: if I access the layout property of the jqxLayout, I’ll be working with a live reference. Therefore, any changes to that JSON object modify the internal representation of the object. ‘render’ can then be used to update the rendering of the object against the updated JSON.

    Also, one additional question. A few months ago, JQWidgets changed how examples are handled to no longer support the use of a fiddle platform. I imagine this was for copy protection, but it has made it difficult to “fiddle” with examples to fully explore the controls. Is it still possible to “fiddle” with the examples in some way? (We have purchased the software, but have the libraries on a private server.)

    Best Regards,
    -Gary Geniesse


    Gary
    Participant

    One additional note: I did look into using “box-sizing:border-box” to get around some of these issues, but the widget appears to be using “box-sizing: content-box !important;”.


    Gary
    Participant

    Hello Dimitar,

    Thank you for your quick reply. Unfortunately, I think you missed the entire point of my question.

    > I would like to have a RangeSelector that fills a div (with the markers and axis inside the containing div) and have the selection region contain a chart that fills the selection area.

    I need to SET the width and height of the RangeSelector so that it fills the containing div without going outside. I don’t need to know the width and height of it after it is created, I need to know how big to make it when I create it. To know this, I would need to know the sizes that padding:auto will select or approximate them reliably. Theoretically, I could approximate the padding for my initial size then see what the actual size is after creation and adjust appropriately. The problem with the approach is that I do not know if padding:auto will change further after I adjust the internal size.

    Furthermore, the chart example you referenced has a fixed size. My second fiddle highlights that it does not appear to be possible to simply use 100% width/height to size the background contents.

    This is why I am asking what the recommended approach to this would be since there is no obvious solution.


    Gary
    Participant

    Is there a definitive answer on this? If it is not supported now, is it planned to be supported and if so, when?

    I had planned to create tabs with images and preferred the functionality of jqxRibbon over jqxTabs.


    Gary
    Participant

    Hi Peter,

    Thank you for showing me a working example by adjusting the fiddle.

    With all due respect, I was not reporting this as an error in your software. I reported that I was trying to do something and that the way I expected it to work did not. Thank you for showing me where the problem might be.

    Note that I have encountered several different behaviors to height and width setting from your widgets when using them in my application divs (which are all sized the same way). Some widgets fill the parent divs completely without height/width setting, others require height/width 100%, and others require specific pixel sizing to fill the divs. Based on your response, I will take a closer look the parent div definitions to see if they can be tweaked in order to make your widgets behave consistently. However, please rest assured that while I did not spend extensive time debugging my fiddle, I have spent several hours trying to debug and address these inconsistencies in my own applications before deciding to ask about this behavior.

    Regards,
    -Gary Geniesse


    Gary
    Participant

    (For some reason, my fiddle did not take, here is the code:)

    <div id='jqxTabs'>
        <ul >
            <li>Tab 1</li>
            <li>Tab 2</li>
            <li>Tab 3</li>
        </ul>
        <div>
            <div id='jqxSplitter'>
        <div style="background-color: #97FFAF; height="100%""></div>
        <div style="background-color: #E8C0AF"></div>
    </div>
        </div>
        <div>Content 2</div>
        <div>Content 3</div>
    </div>
     $('#jqxTabs').jqxTabs({
       height: '100%'
     });
    $("#jqxSplitter").jqxSplitter({
       height: '100%'
    });

    https://jsfiddle.net/GaryGen/HpGSK/126/

    in reply to: linear gauge pointer linear gauge pointer #68914

    Gary
    Participant

    Hello Peter, it appears the example referenced from the documentation is now working in the fiddle.

    Here is what I am observing:
    – For the default pointer type, if I set the ‘value’ parameter, the value remains correct.
    – For the arrow pointer type, if I set the ‘value’ parameter, the value initially sets, but then resets to 0. To display a value, I need to explicitly call val() after initialization.

    Why is this?

Viewing 15 posts - 1 through 15 (of 16 total)