Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 6295] default optional_depends answers

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 6295] default optional_depends answers
  • Date: Tue, 7 Sep 2004 22:17:33 -0400

http://bugs.sourcemage.org/show_bug.cgi?id=6295





------- Additional Comments From acedit AT armory.com 2004-09-07 22:17 -------
how about gettext? i want to phase out things that dont need to use it
without having to think too hard about always answering no to that question.

Its mostly just a convenience, single spell depends are admitedly
a bit trivial, providers can be more interesting though.

Theres also a bit more to this than just the user definable default
answers, with the commit-depends-on-success code if the user bails
out of depends inquisition they lose all the answers they gave and
have to re-enter them. Which I think is inconvenient. In the old
scheme we inserted the answer straight into DEPENDS_STATUS, so they
didnt lose the answers, but the database became inaccurate. So in
a way this feature could fix that interface regression.

It would be nice to pull out the default answers with a little more
intelligence. We could for example check if a spell is going to be
cast, a provider has already been selected, if theres an existing answer,
if theres a left over answer, or a default choice. We could also have a
threshold of when to query the user.

Theres a fairly large number of directions one can go for this and
I havent figured out the best way to do it, but i think it would be
nice to have a way to lower the number of questions a user can get
(if they want). It makes the system more powerful and less cumbersome
IMO.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page