[aoverton07Participant]

So…can you tell me why the z-index is set to 99999 in the jsfiddle I created? This is the only time I’ve seen the z-index that high for a non-modal window it does not appear to be intended behavior.

[aoverton07Participant]

How come the z-index of the windows are 99999 in the above jsfiddle?

[aoverton07Participant]

I think I’ve narrowed the issue down to the jqxScheduler. When a window is invoked from the scheduler with a ‘bringToFront’ call the z-index is set to 99,999 thus causing all subsequent calls to ‘bringToFront’ (for any non-modal window) to set the z-index higher than the standard ~9000 for non-modal and ~18000 for modals.

You can see the issue here:

http://jsfiddle.net/6xyHE/39/

1.) Double click the appointment to open window 1, see that the z-index is 99999.
2.) Click the button on the bottom to open modal window 2, see that the z-index is 18001
3.) Click the button to open non-modal window 3, see that the z-index is 99999.

There is no way to bring the modal window to the front. Now any call to ‘bringToFront’ for any non-modal window will set the z-index higher than normal (~100,000) so now all my non-modal windows will be showing on top of all other widgets.

Why is the scheduler setting the z-index so high?

[aoverton07Participant]

Is it possible to get the ‘open’ and ‘close’ events to bubble up through the document?

Best Regards,

Alex Overton

[aoverton07Participant]

I am testing using the latest release of jqWidgets (3.9.1) and the latest versions of Chrome, Firefox and Android Native Browser on a brand new Galaxy S6 Edge+. I was unable to enter time manually on all three mobile browsers. Here is how I am initializing my time input:

$("#dayTime").jqxDateTimeInput({ width: '62px', height: '25px', formatString: 'hh:mm tt', showCalendarButton: false, theme: theme });

I have included globalize.js as well.

It appears to be the same issue highlighted here:

http://www.jqwidgets.com/community/topic/time-not-set-when-using-mobile-browser/

and here:

http://www.jqwidgets.com/community/topic/time-input-on-mobile-website/

[aoverton07Participant]

If I downgrade to a previous version I lose my jqxScheduler functionality :/

Is it possible for this error to be fixed in a future release?

[aoverton07Participant]

The thrown error does indeed cause issues, in the example below you will see the ‘rowclick’ event handler was never applied, due to the error being thrown in the grids ‘ready’ callback. I use the ‘ready’ callback to load the grids state, if the state contains a sort then I lose all event handlers on my grid. Should I resort to using something else besides ‘rowdetails’?

http://jsfiddle.net/A59WK/83/

[aoverton07Participant]

74 bit,

Thank you, for safe measure you can add the same code in the ‘editDialogOpen’ handler. The problem is I am working with a single page application where DOM nodes, and event listeners are at a premium. With this method, the dialog window is still added to the DOM and initialized (along with all of it’s inputs)…

[aoverton07Participant]

Would you consider adding this option in a future release? Not sure why we are forced to use the edit dialog in this manner, your toolbox provides all the means to create our own editing windows. And it causes problems when my users need to edit an event outside of the Scheduler and it has not yet been initialized. To me it doesn’t make sense to initialize the whole scheduler in order to edit just one event.

[aoverton07Participant]

I see there is an option to turn off the ‘contextMenu’ but I still can not find a way to turn off the default Edit Dialog…

I have tried returning true/false, preventDefault, and stopPropagation inside all of the editDialog callbacks to no avail…

[aoverton07Participant]

Surely this can be achieved through the ‘cellsrenderer’ function?

[aoverton07Participant]

I have been extremely pleased with the documentation, especially the recent addition of the jsfiddle links. Keep up the good work!

[aoverton07Participant]

I second this. Also, if you use the search function from the magnifying glass in the top right corner of the page (while you’re logged in) instead of the search box that appears on the forum home page, you get a much nicer set of results, i think the only difference is that you are searching the entire site rather than just the forum, could be a good thing though….

[aoverton07Participant]

Simple, because deleting a row directly affects the return value of getselectedrowindex.

If there are five rows total, and you have the last row selected, then the getselectedrowindex method would return a value of 4.

If you then delete that row, your grid will NOT have any rows selected, yet the getselectedrowindex method would still return a value of 4.

Gets the bound index of the selected row. Returns -1, if there’s no selection.

-it does not follow the above statement, taken from the grid documentation.

[aoverton07Participant]

Hmmm that’s strange because I copy and pasted that code into one of your jsfiddle pages, and the problem persists:

http://jsfiddle.net/35kU5/45/

[Author]

Posts