[sirstruckParticipant]

Thanks, Dimitar, this does indeed work. And, in case anyone comes across this code, I wanted to clarify what you’re doing. To prevent the keyboard press from initiating a cell edit, we have to return true in handlekeyboardnavigation. The keys that initiate grid edits are the number keys (48-57) and the letter keys (65-90). For completeness’s sake, the Enter key (13) and the F2 key (113) will also start editing a cell if people also want to check for those. So, the full description is, if the grid is focused but the user is not editing a cell and the user presses a number key or a letter key, return true (i.e. don’t put a grid cell in editing mode). Thanks again!

[sirstruckParticipant]

Hi Hristo, it seems to be inconsistent though. This JSFiddle is identical to the previous one except I changed the editmode to “selectedcell”. Now when I click on another cell, the edit completes. It sounds like ultimately though I’m going to need some sort of custom solution.

Thanks,

David

[sirstruckParticipant]

Oops, I spoke too soon. We noticed a couple of issues with this code change. First, it prevents the user from editing grid cell values using the keyboard. Not only that, it also prevents edits to other fields in the same webpage, e.g. text fields. Dimitar, is there another way to do this?

Thanks,

David

[sirstruckParticipant]

This works great — thanks, Dimitar!

[sirstruckParticipant]

Yeah, I’m seeing the same thing (although intermittently) in v3.0.4. Thanks for posting the workaround, jqWizard! Although, I decided to use window.innerWidth and window.innerHeight.

[sirstruckParticipant]

Dimitar, thanks for the suggestion! I think this works pretty well although if the user happens to click on a day that matches the old date’s day, it won’t work. For example, click on the month-year at top, select a different month, then click on the same day in that month.
http://jsfiddle.net/FrNWD/39/

In the meantime, I’ve managed a workaround with my older version of jqwidgets. (It takes advantage of the fact that there was a previously existing bug in the calendar widget where clicking on a year or month would fire two change events while clicking on a day would fire only one.)

Is it possible for a future release to provide a context object with the event so the developer can see what the user clicked on that led to the change event?

Thanks,

David

[sirstruckParticipant]

Makla, I think a way around this would be to set the attributes in jQuery before initializing the dock panel. So, change the HTML to something like this:

<div id='jqxDockPanelLivingRoom'>
	<div id='left'></div>
	<div id='top1'></div>
	<div id='top2'></div>
</div>

Then, use jQuery code like this:

$('#left').attr('dock', 'left');
$('#top1').attr('dock', 'top');
$('#top2').attr('dock', 'top');
$("#jqxDockPanelLivingRoom").jqxDockPanel();

[sirstruckParticipant]

Oh cool, that’s very good news. Thanks for the update!

[sirstruckParticipant]

I’d like to echo jimg’s comments. The inability to import an existing theme into the theme builder severely limits its usefulness. Also, displaying the editor and the preview at the same time would be very helpful.

[Author]

Posts