[BUG] 2.3 - SetMinMaxValues -> OnValueChanged
by Grayhoof | 13/10/2007 16:50:27 Updated from original post. Calling a sliders SetMinMaxValues is now triggering the SetValue method or OnValueChanged event and setting the value to whatever you set the Min value to be. This was not the case prior to 2.3 and is causing most all sliders to be updated multiple times when initially setting them up. This becomes a real problem when you are executing other code off of the SetValue method. Original post below: Having an issue with WoW on the 2.3 test server and my mod SCT. Using the code that has worked from 2.1 and currently works on 2.2.3, WoW is crashing in 2.3 when trying to set certain values inside a nested table. I've isolated the crash down to one line of code that updates a saved variable table when a slider value changes. When putting if statements to check that the table value is valid and printing out the values it is attempting to set, everything is printed to the console fine. It is only when trying to set the value to the table that WoW crashes. Granted there could be any a number of other things causing it, but this is at least the area I track it down to. I can provide detailed code and the WoW crash dumps if needed. Here is the error itself: This application has encountered a critical error: [ Post edited by Grayhoof ] http://grayhoof.wowinterface.com/ |
by Slouken | 17/10/2007 03:17:52 Q/A is checking this out, thanks! |
| by Slouken | 20/10/2007 03:24:04 You're welcome! |
| by Slouken | 07/11/2007 06:06:58 It is a bug that will be fixed soon, hopefully in time for 2.3 release. |
News
Spam
Hot: Upcoming Alterac Valley Improvements in Patch 2.4
Most Viewed 
Recent Blizzard Announcements
