Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>> It looks like the symbols query-compare-equal and guid-match-any have
>> been turned into numeric parameters in the new query. (The GUIDs
>> changed since I probably selected a different account.) I don't know
>> whether the bug is in the processing of the query or the generation of
>> the query.
>
> Yeah, the swig wrappers wrap enums as numbers, while the g-wrap
> wrappers wrapped them as symbols. For that reason, and probably many
> more, in theory, saved reports from 2.0 (g-wrap) may be unreadable in
> 2.2. In practice, I think most reports will work fine, but saved
> queries won't.
This isn't a good idea.. It means that anytime you change the values
in an enum ALL your saved state goes bad!! What's the point of using
an enum if it's not stable?
Is there any way we can fix this -- at least in certain places where we
stringify the enums?
> -chris
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
