No validation feedback when using the config via the blizzard options #2


  • Defect
  • Replied
Closed
Assigned to nevcairiel
  • yssaril created this issue Oct 4, 2008

    What steps will reproduce the problem?
    1. create a optiontable with a validate function set
    2. 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

  • yssaril added the tags New Defect Oct 4, 2008
  • nevcairiel posted a comment Jan 4, 2009

    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.

  • nevcairiel removed a tag New Feb 14, 2009
  • nevcairiel added a tag Waiting Feb 14, 2009
  • Adirelle posted a comment Mar 26, 2009

    Why not displaying an error dialog ?

  • Adirelle removed a tag Waiting Mar 26, 2009
  • Adirelle added a tag Replied Mar 26, 2009
  • watchout_cf posted a comment Jul 20, 2009

    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

  • nevcairiel self-assigned this issue May 26, 2010
  • Farmbuyer posted a comment Sep 8, 2010

    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.

  • Forge_User_96189362 posted a comment Sep 9, 2010

    Error dialog makes sense to me, even in own-frame mode. The status bar is a bit "invisible" yaknow.

  • _ForgeUser405586 posted a comment Apr 4, 2016

    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).

  • rainrider posted a comment Jul 23, 2017

    https://gist.github.com/Rainrider/62d56e0d1c40a4311c130fbc3aa89650

     

    This adds a validation error popup to AceConfigDialog-3.0

  • rainrider posted a comment Aug 14, 2017

    Could I please get some feedback on the patch?

  • nevcairiel posted a comment Aug 14, 2017

    I applied the patch with some simplifications, thank you!

  • nevcairiel closed issue Aug 14, 2017

To post a comment, please login or register a new account.