Again, I'm really appreciating this library, makes certain stuff a lot easier. However, when not registering custom events, the default events are lost after changing the cols with SetDisplayCols. So if you would set OnEnter and OnLeave but leave out OnClick, it will do the hovers like normal, but any click events stop working. But if you defined a custom OnClick, this event continues working after changing the cols.

  **What steps will reproduce the problem?**
+
  1. Make a scroll table such a the following;
  <<code lua>>
- 			local scrollTable = ScrollingTable:CreateST({}, 4, 15, nil, frame); -- inserting a dummy cols, real cols to be set in SetFrameSettings
+ local scrollTable = ScrollingTable:CreateST({}, 4, 15, nil, frame); -- inserting a dummy cols, real cols to be set later on
+ -- Register custom events
- 			scrollTable:RegisterEvents({
+ scrollTable:RegisterEvents({
- 				["OnEnter"] = function(rowFrame, cellFrame, data, cols, row, realrow, column, scrollingTable, ...) end,
+ 	["OnEnter"] = function(rowFrame, cellFrame, data, cols, row, realrow, column, scrollingTable, ...) end,
- 				["OnLeave"] = function(rowFrame, cellFrame, data, cols, row, realrow, column, scrollingTable, ...) end,
+ 	["OnLeave"] = function(rowFrame, cellFrame, data, cols, row, realrow, column, scrollingTable, ...) end,
- 			});
+ });
  <</code>>
- 2. Call SetDisplayCols on it with new headers.
+ 2. Set new display cols
+ <<code lua>>
+ scrollTable:SetDisplayCols({
+ 	{
+ 		["name"] = "Item",
+ 		["width"] = 100,
+ 	},
+ 	{
+ 		["name"] = "No",
+ 		["width"] = 50,
+ 	},
+ });
+ <</code>>
+ 3. Set some same data
+ <<code lua>>
+ scrollTable:SetData({
+     { "Sachmo", 12 },
+     { "Josua", 8 },
+ });
+ <</code>>
- 3. Click the sort headers.
+ 4. Click the sort headers.
  **What is the expected output? What do you see instead?**
+
  Continue using the default events.

  **What version of the product are you using?**
+
  r139

  **Please provide any additional information below.**
+
- I have fixed the issue for me for the time being by defining an empty OnClick event.
+ I have fixed the issue for me for the time being by defining an empty custom OnClick event.