Forum Replies Created
-
Author
-
Die Funktionen beeinflussen sich in verschiedenen Szenarien unkontrollierbar gegenseitig: unter anderem überschreiben sie Zeilen im Grid.
Ich habe keine Zeit für Sie weiter debugging zu betreiben. Die Fehler sind unerwünschte Seiteneffekte im Zusammenspiel von updaterow -> clearselection -> addrow
Wann wird das behoben?
Wenn Sie nicht wissen, um was es geht probieren Sie es mal mit einem komplexeren Beispiel aus.
I am a customer. I have written several mails ti your support without getting an answer.
I’m not your betatester. I have to spend several weeks in finding the bugs in your product. You don’t realy help. Only a quick answer – and forget the stupid customer. Why should I help you to improve your products?And by the way: I have already helped you with your illegal privacy policy – instead of reporting to the authorities.
Best Regards.
Done. DataAdapter is not programmed very properly. I now find a workaround.
Done. I have fixed the bug in your jqxgrid.filter.js.
Dear Mr. Stoev. Please answer my question. It’s your error message. What does the error message mean?
July 13, 2018 at 12:40 pm in reply to: DropDownList issuess in mobile DropDownList issuess in mobile #100999Ok,
I will monitor this.July 13, 2018 at 12:01 pm in reply to: DropDownList issuess in mobile DropDownList issuess in mobile #100993Hello,
I used an REAL Samsung Galaxy S8 with Chrome and get this error – not in the simulator.
The error also occurs with your own DEMO.
Set the alignment to bottom and use this with phone in landscape mode to provoke the error: https://www.jqwidgets.com/jquery-widgets-demo/demos/jqxdropdownlist/index.htm#demos/jqxdropdownlist/dropdownlist-open-direction.htmUpdate:
Same behaviour on an iPad, an Samsung Galaxy Tab 10, Lenovo Tablet and an Acer Convertible Tablet (Windows 10).
All devices tested with newest chrome 67.0.3396.99.July 13, 2018 at 9:10 am in reply to: DropDownList issuess in mobile DropDownList issuess in mobile #100989Hello,
I have the same error on Mobile when using your DropDownList AND also DateTimeInput.In a real application, there are several input helpers on one page. The error in your DropDownList control results when the control is not yet visible when the page is called because it only has to be scrolled down to show it. Then the offset is not correct. The same error occurs with the DateTimeInput for the calendar and the time pop-ups.
Unfortunately, I encounter errors in almost every one of your controls. Layout, DockingLayout, Menu, Splitter, Scrollbars and ResposePanel behave so buggy in a real application that I had to replace them already. Likewise, your theme builder produces broken code (eg: some color information will not). Some bugs may not be important to you, but I have very demanding customers who notice the difference in pixel height between DocumentPanel and tabbedGroup – not to mention the many others Deficiencies that I have already warned.
Please correct the errors in DropDownList and DateTimeInput in a timely manner, so that I can use at least some of the controls you’ve purchased.Let me remind you of your slogan “BETTER web, LESS time”. Since I had to develop all the above-mentioned controls from the ground up, having dealt with the many detail errors of your controls, MUCH MORE TIME is more likely to apply.
In einer echte Applikation sind mehrerer Eingabefelfer auf einer Seite. Der Fehler in Ihrem DropDownList-Control entsteht, wenn das Steuelementen beim Aufruf der Seite noch nicht sichtbar ist, weil erst herunter gescrollt werden muss, um es anzu zeigen. Dann stimmt der Offset nicht. Der gleiche Fehler trittt bei dem DateTimeInput für den Kalender und die Uhrzeit-Popups auf.
Leider stosse ich bei fast jedem Ihrer Controls auf Fehler. Layout, DockingLayout, Menü, Splitter, Scrollbars und ResposePanel verhalten sich in einer echten Applikation so buggy, dass ich diese bereits ersetzen musste. Ebenso Ihr Themebuilder produziert fehlerhaften Code (z.B: einige Farbangaben werden nicht ) Einige Fehler mögen für Sie vielleicht nicht wichtig sein, aber ich habe sehr anspruchsvolle Kunden, dennen auch der Unterschied in der Pixelhöhe zwischen DocumentPanel und tabbedGroup auffällt – ganz abgesehen von den vielen anderen Mängeln, die ich bereits angemahnt habe.
Bitte korrigieren Sie die Fehler in DropDownList und DateTimeInput zeitnah, damit ich wenigstens einen Teil der von Ihnen gekauften Steuerelemente verwenden kann.Ich erinnere Sie noch mal an Ihren Slogan “BETTER web, LESS time”. Da ich jetzt alle oben erwähnten Controls von Grund auf selber entwickeln musste, nachdem ich mich mit den vielen Detailfehlern Ihrer Controls herum geschlagen hatte, gilt wohl eher MUCH MORE TIME.
June 25, 2018 at 2:05 pm in reply to: Strange behavior of the elements in the jqxSplitter Strange behavior of the elements in the jqxSplitter #100715The error stil exists in chrome. Firefox & Edge seems to be fine with my solution.
The error also occurs with the treegrid.June 25, 2018 at 1:23 pm in reply to: Strange behavior of the elements in the jqxSplitter Strange behavior of the elements in the jqxSplitter #100712Hello Martin,
this only works with fixed height – not with a percentage height.
It also appears without using Splitter. I have already given up to use the splitter in my application because of couple of bugs I found in it(for example, the button is buggy).In my program I have to use an absolutely fixed menu line above an 3 or more Container side by side in the main-area. It only seems to work if you work with several nested DIV containers. All of them need height 100%. The most basic MUST encompass the entire page and may not have any absolute placement.
Here is my html:
<div class="Menu"> Here are the menu-elements... </div> <div class="MyMainArea"> <div class="Page"> <div class="MainPanel_CENTER"> <div class="MainPanelContent_CENTER"> <div class="ButtonArea" > some Controls... </div> <div style="clear:both;"></div> <div class="hevTable" ></div> </div> </div> <!--End MainPanelCenter --> </div> <!--End Page --> </div><!--End MyMainArea-->
And here the css:
.Menu{ top: 0px; position: absolute; width: 100%; height: 80px; background-color: #004a96; margin-bottom: 45px; z-index: 10000; } .MyMainArea{ overflow: hidden; height: 100%; width: 100%; box-sizing: border-box; margin: 0; } .Page{ height: 100%; width: 100%; top: 125px; position: absolute; background-color: #d3d3d3; } .MainPanel_CENTER{ position: absolute; left :350px; right: 500px; height : 100%; background-color: #ffffff; } .MainPanelContent_CENTER{ height: 100%; width: 100%; }
If you have some suggestions for a better way…
Best Regards
DirkJune 25, 2018 at 5:28 am in reply to: unable to convert saveLayout method returned result to string unable to convert saveLayout method returned result to string #100694Hello Dimitar,
this is very bad. The control is therefore useless for me.
I will write a mail to your support.with Regards
DirkJune 24, 2018 at 4:14 pm in reply to: Strange behavior of the elements in the jqxSplitter Strange behavior of the elements in the jqxSplitter #100689Hello Grigoriy,
I just came across the same problem. Seems to be a bug in the edit function of the grid. I found a simple but effective workaround: Wrap the Grid’s div with another div container. That works for me. Hope this helps you.<div> <div id="grid"></div> </div>
Best Regards
DirkJune 24, 2018 at 11:58 am in reply to: unable to convert saveLayout method returned result to string unable to convert saveLayout method returned result to string #100688Hello,
I try to get one of the mentioned solutions working: both throw an error if you for example rearange Document-Panel:
jqxlayout.js:7 Uncaught TypeError: c[A].appendTo is not a function
at b.(anonymous function)._createLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:17327)
at b.(anonymous function)._createLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:17435)
at b.(anonymous function)._createLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:17435)
at b.(anonymous function)._createLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:17435)
at b.(anonymous function)._createLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:17435)
at b.(anonymous function).render (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:2123)
at b.(anonymous function).loadLayout (https://ff.zzz.de/jqwidgets/jqxlayout.js:7:3167)
at b.(anonymous function).loadLayout (https://ff.zzz.de/jqwidgets/jqxdockinglayout.js:7:804)
at Object.a.jqx.invoke (jqxcore.js:14)
at Object.a.jqx.jqxWidgetProxy (jqxcore.js:14)How should it be possible to save the layout in a database without JSON?
Please help me with a working solution.
Best Regards
DirkJune 16, 2018 at 7:33 am in reply to: Edit-Dialog Focus only on subject Edit-Dialog Focus only on subject #100612Hello Martin, thank you. That works.
Best Regards
Dirk -
AuthorPosts