jQWidgets Forums

Forum Replies Created

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

  • csoga
    Participant

    You can’t break the API from version to version. Not cool..

    I need a work-around.

    Thanks.


    csoga
    Participant

    Hi Histro,

    The ability to change the cursor to “pointer” on mouserover used to work. I had the it working in release 3.7. I just upgraded to release 4.2 and it doesn’t work anymore. See the event handling code I have for both versions below. What broke?

    My release 3.7 Event Handler (works):

    function eventHandler()
    {
    var groups = $(‘#chart’).jqxChart(‘seriesGroups’);
    if (groups.length > 0)
    {
    for (var i=0; i<groups.length; i++)
    {
    groups[i].mouseover = function(e)
    {
    var obj=document.getElementById(‘chart’);
    obj.style.cursor=”pointer”;
    };

    groups[i].mouseout = function(e)
    {
    var obj=document.getElementById(‘chart’);
    obj.style.cursor=”default”;
    };

    }
    }
    }

    My release 4.2 Event Handler (does not work):

    function eventHandler(event)
    {
    if (event.type == ‘mouseover’)
    {
    var obj=document.getElementById(‘chart’);
    obj.style.cursor=”pointer”;
    }

    if (event.type == ‘mouseout’)
    {
    var obj=document.getElementById(‘chart’);
    obj.style.cursor=”default”;
    }
    }


    csoga
    Participant

    Was there a response to this last comment?

    Why is it not possible to specify the x and y coordinates for browserBoundsOffset?

    Thanks,
    Cyril


    csoga
    Participant

    Thanks Peter. I decided to go with the grid destroy/recreate option and it’s working well. The data I’m dealing with is fairly small and well indexed so that’s probably the easiest route.

    Thanks again!
    Cyril


    csoga
    Participant

    Thanks Peter, however, my use case requires the various summary values I’m calculating and displaying on the Grid’s status bar to be updated as new transactions are submitted in a pop-up window.

    I assume there is no way to do that… besides destroying and recreating the grid after each transaction is submitted? Please confirm.

    Thanks,
    Cyril

    in reply to: Forcing Window to Invalidate Forcing Window to Invalidate #17582

    csoga
    Participant

    Thanks Dimitar! I tried it and it worked:-)

    Highly appreciate the insight and help!

    Cyril


    csoga
    Participant

    Thank you Dimitar. I have sent the screenshot and sample code.

    Cheers,
    Cyril


    csoga
    Participant

    HI,

    Unfortunately the images I’m attaching here don’t persist after I save. Is there another way I can send the image?

    I noticed that this issue only occurs when I used the DateTimeInput in a jqxWindow widget (regardless of whether it’s displayed as modal or non-modal).

    Look forward to hearing back from you.

    Thanks,
    Cyril

    in reply to: Splinearea Chart Events Splinearea Chart Events #10975

    csoga
    Participant

    Hi Dimitar,

    Thanks for getting back to me.

    Too bad you don’t have good news for me. I hope these issues are resolved soon. In the meantime I will try to find some alternatives…

    Thanks,
    Cyril

    in reply to: Disabling Top Level Menu Item Disabling Top Level Menu Item #6578

    csoga
    Participant

    Great, thanks Dimitar. It works!

    Cheers,
    Cyril


    csoga
    Participant

    Thanks Peter… for pointing out the typo I had in my code. Fixed it and it worked like a charm.

    I played around with defaulting the time a bit and got it working as well. In case there is anyone wondering how I fixed that, the following is what I did to set the default of the field to the value retrieved from the grid (which was in the format “HH:MM:SS”):

    //Object Definition
    $(“#startTime”).jqxDateTimeInput({ width: ‘100px’, height: ’23px’, formatString: ‘HH:mm’, showCalendarButton: false, theme: theme });

    Start_Time = “21:30:00”; // Initial value retrieved from the grid.
    sTime = ConvertToDate(Start_Time); // A function I wrote to convert the value of Start_Date to a valid date

    //Set the default of the field…
    $(‘#startTime’).jqxDateTimeInput(‘setDate’, new Date(sTime));

    // Custom function to return a valid date from a time.
    function ConvertToDate(stringTime)
    {
    var date = new Date();
    hours = stringTime.substr(0,2);
    minutes = stringTime.substr(3,2);
    date.setHours(parseInt(hours));
    date.setMinutes(parseInt(minutes));

    return date;
    }

    Cheers,
    Cyril


    csoga
    Participant

    Thanks for the feedback, Peter.

    What you mentioned is what \i thought I was doing in some of the options I tried (specifically option 2)… Or is it failing because it is being performed in-line?

    $(‘#startDate’).jqxDateTimeInput(‘SetDate’, new Date(new Date(Start_Date).getFullYear(), new Date(Start_Date).getMonth(), new Date(Start_Date).getDate()+1));

    I will try what you suggested later and see if it will work….

    Thanks,
    Cyril


    csoga
    Participant

    I have tried the following 3 variations and the dates are always set to the current date instead of the date I am extracting from the Grid (see above).

    $(‘#startDate’).jqxDateTimeInput(‘SetDate’, $.jqx.dataFormat.formatdate(new Date(new Date(Start_Date).getFullYear(), new Date(Start_Date).getMonth(), new Date(Start_Date).getDate()+1), ‘dd-MMM-yyyy’));

    $(‘#startDate’).jqxDateTimeInput(‘SetDate’, new Date(new Date(Start_Date).getFullYear(), new Date(Start_Date).getMonth(), new Date(Start_Date).getDate()+1));

    $(‘#startDate’).jqxDateTimeInput(‘SetDate’, new Date(Start_Date));

    I have also tried the following for the Time formatted input and it always defaults to the current time instead of the time extracted from the grid:

    $(‘#StartTime’).jqxDateTimeInput(‘SetDate’, $.jqx.dataFormat.formatdate(new Date(Start_Time), ‘HH:mm’));


    csoga
    Participant

    Excellent! Thanks Peter… this solved my problem.


    csoga
    Participant

    Thanks Peter, for the quick response.

    The only difference between the example you sent me and what I had was that I had virtual mode enabled on the detail grid. Once I turned virtual mode off, the quirky rendering issues went away.

    On the other hand, once I turned virtual mode on in the example you sent, it also started experiencing the same rendering issues I was previously experiencing.

    Unfortunately the type of application I’m looking to implement will require the detail grid to be implemented in virtual mode – since the volume of records will be quite large.

    Do you have any suggestions as to what I need to do to eliminate the virtual mode rendering issues?

    Thanks!

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