When I deleted a row from the SmartTableModel I used this code to do it:
deleteRow : function (uniqueId) {
var rowId =
this.__getTableModel().getRowById(this.__getTableModel().getView(),uniqueId);
this.__getTableModel().removeReferencedRows([rowId], false);
this.__getTableModel()
If you could post an example of code that replicates this error I may
be able to help you more. It's hard to pinpoint the source of the
problem with just this error because it could point to many different
issues
-deech
On Tue, Aug 2, 2011 at 2:52 PM, jhwrightiii wrote:
> Thanks for taking the ti
Thanks for taking the time to make your suggestion. I still get the same
error.
Of note, using the code in original post, if I click 3 times and ignore
errors, all the rows that were deleted by those clicks soon disappear and
then the delete works on each click thereafter.
I feel that it has som
I wrote SmartTable, as a modification of the previous Smart table model,
under contract a year ago. Since then, my client has greatly modified it in
a fashion that is tightly integrated with their application. I have had
little to do with this contrib in a year, and there are a few reported
issues
This may have changed but when I used SmartTableModel the row id's
started with '1', so row id '1' corresponds to index '0' in the row
array. So maybe you are having the issue because you are trying to use
the row id as an an index in the row array.
I had to add a function to get the rowindex from
Hi Fons,
the new IO stack includes a debugging mode that might be of help here. Can you
set the debug flag and paste the results? Here is how [1, 2].
Also, in your success handler, what is:
var nativeXhr = request.getTransport().getRequest();
console.log(nativeXhr);
console.log(nativeXhr.respon
Hi Martin,
Thank you for your fast response.
My qooxdoo app starts by displaying a login window, and then does a request
to a server-side django app.
As follows:
_doAuthenticate : function()
{
...
var url = "http://"; + this.host + ":" + this.http_port +
"/dsc/qx/login";
Hi, thanks for taking time to answer.
Looking at the implementation seems that qx.lang.Json.stringify uses
native JSON if available, while qx.util.Serializer.toJson not. So the
second option can be faster, especially with big object graph.
Gian Marco Gherardi
http://gianmarco.gherardi.me
On Tu
Hey,
is there already a bug report for that in the qooxdoo bugzilla? Seems like this
is a table bug which should be fixed in the framework instead of worked around
as a app developer. Don't see a reason why an user of qooxdoo should bother
with such bugs. :)
Regards,
Martin
Am 02.08.2011 um 09:
Hello,
In general, the new IO layer you use now should work in every browser we
support which includes the IEs you mentioned. If thats not the case, it's a bug
in the framework and should be fixed (if possible). Could you maybe go into
detail what does not work in your use case in IE? Maybe it i
Hi,
I have been using qx.io.remote.Request for a long time, and it always worked
with Firefox, Opera, ...
But never with InternetExplorer.
Recently I switched to qx.io.request.Xhr of the new qooxdoo version, also
with the hope that that
would solve my IE problem. Nope.
I did solve part of the pro
Hi,
I have exactly the same problem as Kenneth. After editing a cell the drag
and drop doesn't work any more. Only after some double clicks. I have it in
my source code, but it's the same in the demo browser. You find it in demo
browser under "Table Drag_And_Drop".
(http://demo.qooxdoo.org/curre
12 matches
Mail list logo
