This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. create a optiontable with a validate function set2. add the optiontable to the blizzard addon options via LibStub("AceConfigDialog-3.0"):AddToBlizOptions()3. fail the validation and you will get no feedback
What is the expected output?some sort of error message
What version of the product are you using?trunk
Yeah .. hmm .. validation feedback is usually placed in the statusbar, which the blizzard frame doesn't have.
Guess we'll have to think of some way to display it alternatively. Ideas are welcome.
Why not displaying an error dialog ?
On the top line to the right of the addon's name is usually some unused free space. With some red/orange/yellow background this message would definitely be seen and the scrollpane does not include this space either, so it would always be seen
Um, in the meantime, how about DEFAULT_CHAT_FRAME:AddMessage()?
Right now, you're discarding information that the addon author is trying to present to the user, and that's a cardinal sin for a third-party library. Get something in place to at least pass along the errors, then get fancy later.
Error dialog makes sense to me, even in own-frame mode. The status bar is a bit "invisible" yaknow.
Ugh - why is there still no built-in solution for this?
This bug makes the pattern/usage fields of the input widget completely useless, and the validate field of all controls awkward (forcing each author to roll his own error report mechanism).
https://gist.github.com/Rainrider/62d56e0d1c40a4311c130fbc3aa89650
This adds a validation error popup to AceConfigDialog-3.0
Could I please get some feedback on the patch?
I applied the patch with some simplifications, thank you!
To post a comment, please login or register a new account.