tagging SX accounts

[Derek Atkins]

Unfortunately I was specifically asking about "accounts", not
"transactions".  Your "fix" does not handle the specific case where
the user has a GL open and _then_ creates a new SX.  Transactions tied
to the new SX wont be tagged as "part of the excluded SX account
group) and as a result will show up in the (already opened) GL.

If there were an SX "account" marking, we could eliminate accounts
that have that marking, rather than elimitating accounts that already
exist....

-derek

Josh Sled <jsled@asynchronous.org> writes:

> On Fri, Oct 18, 2002 at 12:14:01AM -0400, Derek Atkins wrote:
> 
> | Is there some way that SX "accounts" are tagged, or is there some way
> | to specifically tag an SX account, such that it's easy to detect that
> | an account is an SX vs. regular account?  This would solve a
> | particular GL bug that would cause an SX to appear in a GL if the SX
> | is created after the GL is already opened.
> 
> The transactions created from SXes have a kvp slot ["from-sched-xaction"]
> filled with the SX from whence they came...
> 
> I had solved that same bug in the past by filtering out the AccountGroup
> which contains the template transactions
> [gnc_book_get_template_group( gnc_get_current_book() )].  Did that get
> undone?
> 
> ...jsled
> 
> -- 
> http://www.asynchronous.org - `a=jsled; b=asynchronous.org; echo ${a}@${b}`
> jabber:jsled@jabber.asynchronous.org, ICQ:4983267, {AIM,YIM}:joshsled

-- 
       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
       warlord@MIT.EDU                        PGP key available