jQWidgets Forums
Forum Replies Created
-
Author
-
I was referring to jqxDataAdapter, which was the title of my post
thanks for the response. And yes, I got the file name wrong
July 11, 2016 at 5:22 pm in reply to: More than 2 properties in the Button settings object causes additional div More than 2 properties in the Button settings object causes additional div #85651Christopher,
Is there anyway that I can track the status of this work item and when a fix may be available?July 6, 2016 at 5:34 pm in reply to: More than 2 properties in the Button settings object causes additional div More than 2 properties in the Button settings object causes additional div #85588Sorry, I should have been more clear. The button renders without issue. The problem is that the extra DIV tag shows up an there are two “buttons”. The onclick event no longer works because of the duplication. This code will not work:
var demoApp = angular.module("demoApp", ["jqwidgets"]); demoApp.controller("demoController", function ($scope) { $scope.settings = { template: 'primary', disabled: false, imgWidth: 16, imgSrc: 'http://www.jqwidgets.com/jquery-widgets-demo/images/facebook.png', textPosition: 'center', imgPosition: "left", width: 150, height: 50 }; // event Handler $scope.eventHandler = function(event){ $log.info('eventHandler called'); }; });
I was able to resolve the issue by using ng-repeat-start and end
November 20, 2015 at 6:05 pm in reply to: calling methods on toggle button ignored calling methods on toggle button ignored #78400We resolved the issue. The problem was using a toggleButton within a button group. Once we switched to using a pure buttonGroup in radio mode, we were able to call from another button the “setSelection” method to select the appropriate button within the group. Once this was implemented, all worked as expected.
November 19, 2015 at 10:23 pm in reply to: calling methods on toggle button ignored calling methods on toggle button ignored #78356We are now on jQWidgets v3.9.1 (2015-Oct) and the same result. Any method we call seems to be ignored. When we set the toggled property to true on one of the buttons in a group, it does toggle the state but the other buttons do not change even though it is in radio mode. Further, all the styling seems to go away as well.
January 31, 2014 at 4:11 pm in reply to: DateTimeInput editor in a grid DateTimeInput editor in a grid #48737Peter,
I took a look at my references and the globalize reference had a typo. I corrected that and it now works. Seems odd to me that this script is required for this to work.Thanks for the help
January 31, 2014 at 3:57 pm in reply to: DateTimeInput editor in a grid DateTimeInput editor in a grid #48735There is a ref to globalize.js Not sure what that has to do with anything. As I only use this culture param when needed. I have removed all the code I showed in the initial post and the same problem remains. When I do the dateTimeInput on its own, everything works fine. The only issue is when I embed it in a table. Is there any other reason as to why hitting any key in a datetimeinput just sets it to 0? Again, the up/down arrows scrolls through as well
January 31, 2014 at 2:59 pm in reply to: DateTimeInput editor in a grid DateTimeInput editor in a grid #48732Dimitar,
Sorry for the confusion. We have a set of “wrapper” scripts that act as an abstraction layer between a custom designer we have to allow non-developers to design pages and interact with the underlying jqWidgets. The code I presented is how we determine what type of column it is and to setup the editors as needed.The code actually generates an object that contains the equivalent of what is sine in the Customized example:
createeditor: function (row, column, editor) { // assign a new data source to the combobox. var list = ['Stuttgart', 'Rio de Janeiro', 'Strasbourg']; editor.jqxComboBox({ autoDropDownHeight: true, source: list, promptText: "Please Choose:" });
However, if I remove the custom editors I still have the same issue of being unable to use the keyboard , other than the up and down arrows, to update the date and times.
thanks
January 22, 2014 at 6:23 pm in reply to: Grid disabled in Chrome (ver 32) Grid disabled in Chrome (ver 32) #48223I have now confirmed this in multiple installations of Chrome. Version 32.0.1700.77 does not allow me to select rows. Version 31 worked just fine
December 11, 2013 at 10:35 pm in reply to: cellsformatt with FireFox cellsformatt with FireFox #46363Peter,
I found the issue with the invalid dates. We are pulling data that is assigned to “source” from a database. There was a DATE_FORMAT function being used in the SQL query for one of the columns. Although the date format that was set seems to be a format that is ok for firefox it did not like it. We removed that function and stored just raw date/time data in the database and are now handling all date formatting via the widget. This resolved all the issues.thanks
December 10, 2013 at 7:14 pm in reply to: cellsformatt with FireFox cellsformatt with FireFox #46304Peter,
I have finally nailed down the issue. Not sure if this is a problem with the jqxGrid or not, but here is how to recreate the problem.set the datafield to a type of date
set the columntype to datetimeinput
set the celssformat to “F”Load the data adapter with date that have ‘-‘ in them like 2013-05-10. Firefox complains that this is an invalid date if you were to do something like the following in the initeditor function :
currDate = new Date(cellvalue); console.log(currDate.toDateString()); // this will print out Invalid Date
I did the following in the initeditor funciton:
this.currParams.columns[i]['initeditor'] = function (row, cellvalue, editor) { var editorParams = {}; var newDate; if(that.propTransforms.debugMode) { sendToLog('DEBUG',that.id,'cellvalue = ' + cellvalue,'initeditor'); sendToLog('DEBUG',that.id,'that.propTransforms.culture = ' + that.propTransforms.culture,'initeditor'); } // Set Params that should fire on every init // TODO: Make this configurable via JSON if( that.propTransforms.hasOwnProperty('culture') && that.propTransforms.culture !== '') { sendToLog('DEBUG',that.id,'setting culture param','initeditor'); editorParams['culture'] = that.propTransforms.culture; } editorParams['value'] = ""; // Create value param cellvalue = replaceAll(cellvalue,'-','/'); // Make sure we have '/' so Firefox is happy if(cellvalue === "" || cellvalue === undefined) editorParams.value = new Date(); else { newDate = new Date(cellvalue); if(newDate.toDateString() !== 'Invalid Date') editorParams.value = newDate; else { editorParams.value = new Date(); sendToLog('ERROR',that.id,'Invalid Date detected in cell in row number ' + row + ' with cellvalue = ' + cellvalue,'renderWidget.initeditor'); } } editor.jqxDateTimeInput(editorParams); };
thanks
Not sure how I missed this before but I just noticed this in the javascript console:
Uncaught TypeError: Cannot call method ‘toString’ of undefined jqxdata.js:7
not sure if it is related
And we are using 3.0.3
Looks like the link http://www.jqwidgets.com/jquery-widgets-demo/demos/jqxgrid/cellediting.htm?arctic
did not come through in last post -
AuthorPosts