ActiveWidgets 1.0.1 bug fix released

In case someone missed this - ActiveWidgets 1.0.1 bug fix version released:

http://www.activewidgets.com/general.faq.releases/1-0-1.html

Changes since version 1.0.0 (18 May 2004):

Firefox 1.0.3 is now fully supported (workaround for Mozilla bug 290777 - regression in defining getters on prototypes in content script).
New 'stable' sorting algorithm.
Fixed loading XML from string bug.
Fixed a bug where data display was broken on adding more columns if the first row was also selected.
Fixed bugs in Active.Formats.Date module - months offset by 1 and ignored error value.
Fixed bug related to slow select/deselect when many rows are selected.
Fixed various minor CSS bugs.

Hi Alex,

Thanks for the bug fix.

I currently have a commercial licence. Will you be releasing a "Commercial Edition" version of the bug fix? I know the code is the same as the GPL version, but the licence comments differ. Or do you want us to just copy across the licence comments from our old files?

Also, can you confirm the files that have changed? I know grid.js has changed. What about grid.css? Anything else?

Justin (and all commercial license holders),

please contact me over e-mail and I will send you updated commercial package directly. I was not sure if I should just mail it to everyone - looks like spam :-)

Alex, I see the following patch posted by you is missing from bug-fix release. Did you do it intentionally?

Sudhaker Raj
http://TheJ2EE.com

Ref: http://www.activewidgets.com/javascript.forum.1788.0/bug-caused-by-sorting.html

Alex wrote:

Guys, sorry for this bug - here is a workaround (for XML model)

table.response = function(xml){
this.setXML(xml);
this.$owner.setRowProperty("value", function(i){return i});
this.$owner.setRowProperty("order", function(i){return i});
this.$owner.setRowProperty("count", this.getCount());
// this.$owner.setSortProperty("index", null);
this.$owner.setSortProperty("index", -1);
this.$owner.refresh();
}

Yes, I need more time to find better solution here.

People will be finding same bug again and again. Once a bug is known (with their work around), its patch should immediately roll out. You can always improve on the workable solution. Isn't it?

You are re-initializing value, order, count and (select) index, which is exactly we wanted. This doesn't looks like a dirty patch to me.

Thanks,

Many people use XML data model not to retrive new data but to re-request the same data for possible updates (for example stock market display). In this case the row model (sorting) should not be re-initialized.

I agree that the grid does not have nice way to re-initialize row model, but this has nothing to do with the XML data and the above code breaks existing behavior where someone requests the same dataset.