[1.5.1] Condition-Editor missing 2 SQL output options: NegativeCondition & ErrorType

[1.5.1] Condition-Editor missing 2 SQL output options: NegativeCondition & ErrorType

[JasperAppec]

Thanks for the report.

Please let me know if it's working now. I don't have a proper environment setup at this moment so can't test it thoroughly.

Tested it now and it outputs both values and column names as expected. Thanks! 👍

---

I should probably mention that there is no button or menu to set the NegativeCondition value in the GUI. Do you prefer to have that reported in a new issue, so you can close this one? :)

[JasperAppec]

Great to hear! 😄
My last commit (8a052f1) just fixed a minor mistake in the last commit.

As for the NegativeCondition, from what I remember this was more like an optional condition value rather than a new field or am I wrong? What I mean is that it was only used for a handful of condition types.

Would it be a good idea to put NegativeCondition input field right below the ConditionValue3 field?

It looks like there is space to put the GUI NegativeCondition selector above [Error type:] and [Error text id:] so those 2 controls get pushed down 1 place. I also think it is logical to find the NegativeCondition selector just behind the ConditionValue1 selector. I hope this makes sense. Image:

---

edit: Maybe you are right about the NegativeCondition being just an optional condition value, but I have found it very useful in some of my recent Pull Requests to TrinityCore, like in
[3.3.5] Core/Scripts: move druid FP NPC scripts to DB/SAI #17134

If you look in [the conditions section] of my SQL in https://github.com/TrinityCore/TrinityCore/pull/17134/files , you will see that I found it more practical to use it those 2 times to make the conditions coherent, even if I could have chosen the opposite faction in ConditionValue1.

[JasperAppec]

How is this?

Will do a new pull and check. Reporting back after testing. :)

Hmm... I can't seem to open Condition-Editor after compiling the new version. Do I need to downgrade or upgrade my Visual Studio 2013 update 5 (or use VS2015) to make the current build work as .EXE ?

Full output text: http://pastebin.com/bUuFXzgm (Condition-Editor Unhandled Exception)

[JasperAppec]

Oops, try now.

(Sorry for the delayed reply, I had a busy day driving around on Crete with my parents. :) )
Yes, it works now. The placing is good, I approve of your changes. :)

Never mind, I think my latest suggestions are way outside of this issue. I will remove this extra text in https://github.com/Discover-/SAI-Editor/issues/42#issuecomment-220045853 and move it to a new issue. Thanks a lot for keeping up your work on this. 👍

New issue based on the content I moved: [Condition-Editor] : GUI + functionality changes wanted #44