setCellValue(value,col) possible bug

Using beta 4 >>
I think there is a bug in this function:

obj.setCellValue(value,col);

If you call it ~without~ providing row as the third param (just like above) it will not fire

obj.onCellValueChanged()

But if you provide the third param (row), it works fine.
Please correct me if Im wrong.

that might be because a cell is defined as the intersection of a row and a column. If you have an event that fires on cell content changing and you change the value of every cell in a column (not providing a row parameter), then your event is going to fire multiple times. This could get ugly. If you do want that to occur, then I suggest a loop and set the values of the column cells one at a time using the row parameter. This will give you a more controlled way to handle the cellValueChanged function. So I'm not sure if Alex would call it a bug or not. That's his call. But to me, I would think it was done intentionally,