Forum Replies Created
It’s been 3 months since I reported the issue above, and the issue is still exist in jQWidgets ver.5.7.2.
Would you let me know which version will fix the issue and when it will be released in your plan?
Thanks in advance for your help.
klien54February 19, 2018 at 4:26 am in reply to: Pressing tab key causes checkbox selected in 'checkbox' selectionmode. Pressing tab key causes checkbox selected in 'checkbox' selectionmode. #98778
I’ve checked this issue with your new version 5.6.0, but it is still not working.
Would you let me know when it will be fixed in your plan?
Thank you for your prompt help.
I found my mistake in my sample since you adviced me to use the latest version.
The library that I imported was wrong.
klien54June 29, 2016 at 6:02 am in reply to: jqxInput width always has 8px more automatically. (width:200 -> 208px) jqxInput width always has 8px more automatically. (width:200 -> 208px) #85480
thank you for the kind instruction with a sample.
It is really helpful for handling our issue.
klien54June 28, 2016 at 7:46 am in reply to: jqxInput width always has 8px more automatically. (width:200 -> 208px) jqxInput width always has 8px more automatically. (width:200 -> 208px) #85466
Thank you for your prompt answer.
But the link you put on is not for a jqxInput example but for a jqxButton’s.
I guess the url is wrong 😉
By the way, what I pointed out in my example is that if the parent div width is 200px,
the child element, an input with width:100%, should be 200px not 208px. (talking about red dotted example in my sample)
In my expectation, no matter how the padding and border sizes are, the input width should be eventually same as the width property’s value which a user put in.
In Short, my question is why the jqxInput has 8px width more eventually unlike what other widgets do such as a jqxComboBox, jqxDropDownlist, and so on.
klien54May 25, 2016 at 12:25 am in reply to: jqxTextArea val method is not returning value after using displayMember once jqxTextArea val method is not returning value after using displayMember once #84634
Hi Peter Stoev,
Thanks for your prompt and positive reply.
Please let me know the result coming from your team discussion later.
I will keep an eye on this post.
klien54April 22, 2016 at 2:23 am in reply to: H-scrollbar overlaps last row little bit in autoheight mode. H-scrollbar overlaps last row little bit in autoheight mode. #83777
Thanks for your prompt reply.
I have tried to implement what you instructed to me, but I couldn’t make it.
Actually, I’m still confused how to avoid the 2px-overlaps by using cellsrenderer.
– make the last row’s height 2px higher with cellsrenderer?
– make the last button’s height 2px shorter with cellsrenderer?
Would you give me a sample or more specific instruction please?
Hi Peter Stoev,
Thank you for your prompt reply as always.
I asked the question because there is a ‘hasThreeStates’ property in your API.
I guess you will remove it from the Docs.
Hi Peter Stoev,
We have a good news regarding this issue.
Since Chrome has updated to the new version, 49.0.2623.75, last week, this problem is not occurring anymore.
It happened in the Chrome version 48.8.2564.109m until last week.
Thank you for your help anyway.
klien54March 7, 2016 at 6:41 am in reply to: Data is not displayed from exportdata to excel in Chrome only Data is not displayed from exportdata to excel in Chrome only #82135
Hi Ivailo Ivanov,
Any progress updated on this issue?
Would you let me know how it is going on and when I can use this function properly please?
I’m looking forward to your reply.
Thanks in advance as always.
Hello Hristo Hristov,
Thanks for your reply a month ago.
We found one condition to regenerate the problem as I described above.
If you enable the “Global accessibility mode” in chrome, it will make Chrome Browser hanged and killed.
1. go to “chrome:chrome://accessibility/”
2. toggle the “global accessibility mode: off” to “on” status.
3. go to the sample page in different tab, http://jsfiddle.net/jqwidgets/XvXyy/ (should be in different tab, otherwise the “global accessibility mode” will be off automatically)
4. type ‘test’ in the editor.
5. copy ‘test’ from it.
6. paste it to right after ‘test’ on the same line.
7. paste it again.
8. Chrome will die.
We are using the accessibility mode in Chrome for a certain reason, so we can’t turn it off.
Would you let me know how to use jqxEditor with accessibility mode please?
Thanks in advance for your support.
August 24, 2015 at 11:20 am in reply to: exposed scrollbar in jqxDropdownButton with jqxGrid issue exposed scrollbar in jqxDropdownButton with jqxGrid issue #75115
- This reply was modified 4 years, 3 months ago by klien54.
I’m really grateful for your prompt help.
The DropDown’s initContent API performs perfectly in my code.
I hope you will introduce this useful option on your API documentation in the near future.
klien54August 24, 2015 at 7:35 am in reply to: exposed scrollbar in jqxDropdownButton with jqxGrid issue exposed scrollbar in jqxDropdownButton with jqxGrid issue #75095
I think my sample made you confused.
What I want you to do in the sample is just click the button “Change Grid” without opening the dropdown at the beginning.
The button will change the source of grid.
At that moment, you will find scroll-bar appeared on the button.
1. Initialize Grid in dropdownbutton. (please don’t open the dropdown)
2. Change the source of grid. (click the button)
3. Only a scroll-bar has appeared, not grid.
For your better understanding, I changed my sample little bit without the button.
This sample automatically change the source of grid right after initializing grid.
The scroll-bar is shown at the beginning, and it will move to the right position after opening the dropdown.
Thank you for your quick reply!
Your advice is valuable for my code.
I also figured out that there was ‘jqxmenu.js’ was missing for the process.
For reconstructing the group header, ‘jqxmenu.js’ should be added.
Anyhow, I’ve solved the problem.
please get rid of the line, [enableHeaderTooltips: true,] when you test my code.