jQWidgets Forums
Forum Replies Created
-
Author
-
April 13, 2022 at 3:37 pm in reply to: JqxMaskedInput doesn't work with caps lock JqxMaskedInput doesn't work with caps lock #121634
We use jqxMaskedInput for postal codes and users are complaining about the same issue with CapsLock in v12.2.0
February 17, 2022 at 5:07 pm in reply to: Grid Chart – Height and Width? Grid Chart – Height and Width? #121545Thank you, Peter. Works great!
December 16, 2021 at 10:53 pm in reply to: Columntype rating not displaying partial stars Columntype rating not displaying partial stars #121238Thank you, Ivan. That’s a clever workaround.
September 9, 2021 at 5:04 pm in reply to: jqxValidator not working with jqxDateTimeInput jqxValidator not working with jqxDateTimeInput #120744This still appears to be an issue. The above-referenced demo did not include the date widget. This example illustrates our issue, where date is nullable: http://jsfiddle.net/pauldare1/a2t64xsv/4/
Note: we tried changing the input reference to “inputjqxDate” but that resulted in an error (Uncaught TypeError: Cannot read property ‘nodeType’ of undefined) and the widget did not render
August 12, 2020 at 3:15 pm in reply to: How to exclude columns from exportdata? How to exclude columns from exportdata? #112657Thank you, Peter. We were unaware of that feature and will give it a try.
Hi, Peter
Thanks for your quick response. Today, we’ve found that the issue for the user in question seems to be site specific. E.g., everything works as expected when he tests the app in our SAAS environment, but it does not work as expected when accessing it in a client’s on-premise environment. Now we are wondering if the client’s Tomcat configuration may be messing with the http headers — if you have any suggestions on what to look for, that would be very helpful.
Thanks!
Hi,
We have a user who is using IE11 and is also having a problem with widgets not rendering. There are no errors in the console and other IE11 users do not have the same issue. IE11 reports that it’s in Edge mode, yet it’s behaving as if it’s in an older mode — e.g. I can recreate the symptoms if I manually toggle the mode to 10 or lower.
Meanwhile, we noticed that the online demos (e.g., tabs demo) now have the following tag:
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
Is that now necessary under certain conditions?Thanks
July 30, 2019 at 9:23 pm in reply to: 2-digit year for jqxdatetimeinput 2-digit year for jqxdatetimeinput #106316Any chance that we’ll see this in an upcoming 8.x release?
Thanks
April 19, 2019 at 4:59 pm in reply to: 2-digit year for jqxdatetimeinput 2-digit year for jqxdatetimeinput #104861Hi, Peter
Can we expect to see support for 2-digit year in an upcoming release? We’d like to be able to communicate at least a rough time frame to our clients.
Thanks
August 1, 2018 at 4:16 pm in reply to: 2-digit year for jqxdatetimeinput 2-digit year for jqxdatetimeinput #101335Hi, Martin
Thanks for the response. We understand how the current functionality works, but our users find it quite inefficient to have to input a 4-digit year — and they have a hard time remembering this because most other apps (e.g. MS Outlook, Excel, etc.) understand 2-digits and automatically convert it to 4-digits. The results of keying in a 2-digit year lead to all kinds of data quality issues. E.g,. in your fiddle example, if you key “01/01/13”, the results are quite unexpected (from an end-user’s perspective) — it starts 01/01/1300 and then when it loses focus, it changes to 01/01/00 (01/01/1900) based on the “min” property. For users who do heads-down data entry, this is a big usability challenge
Is there a way to add support for 2-digit input currently? If not, is it on the roadmap?
Thanks!
October 5, 2017 at 4:12 pm in reply to: Is there any support for X-WR-CALNAME property? Is there any support for X-WR-CALNAME property? #96529Thanks, Peter. I think this would be a great feature for the roadmap.
Best Regards
July 7, 2017 at 12:36 am in reply to: enableBrowserBoundsDetection For Menu and Context Menu enableBrowserBoundsDetection For Menu and Context Menu #94754Hi, Dimitar
Is enableBrowserBoundsDetection on the roadmap for jqxmenu? We are using it as a context menu for jqxgrid and the menu opens outside the browser bounds when the user is clicking on one of the lower rows in the grid. If we change the direction to ‘up’, then the user will have a similar problem when clicking on one of the upper rows in the grid. Is there a technique for setting the direction dynamically?
Thanks,
Paul
March 20, 2017 at 10:21 pm in reply to: help me my upgrade issue.(ver4.2.1) help me my upgrade issue.(ver4.2.1) #92338We are running into similar issues when upgrading from 4.1 to 4.5. We noticed that in the Release History, support for jQuery 3.1.0 was added in version 4.2. Does 4.5 require a jQuery upgrade 3.1 or above?
Thanks
March 20, 2015 at 3:52 pm in reply to: Is it possible to set Pageable based on the row count? Is it possible to set Pageable based on the row count? #68909Thank you for pointing me in the right direction. This is going to be easier than I thought. I think I may be able to leverage the getpaginginformation method as well.
Hi,
Is autoresizecolumn and/or autoresizecolumns being considered as an enhancement for jqxTreeGrid. It would be very helpful to have this method available for all grids.
Thanks
-
AuthorPosts