SX oddity

[Fred Bone]

On 14 April 2013 at 10:56, David Carlson said:

> On 4/14/2013 9:34 AM, Fred Bone wrote:
> > I have just discovered that the Scheduled Transaction Editor allows one
> > to set a split's "R" flag to "c". I believe this has to be a mistake - I
> > cannot think of any scenario in which a future transaction can be known
> > to be cleared at the time it is scheduled. I note that if I invoke
> > "Schedule" against a transaction which has some splits already set to
> > "c", the resulting SX has them all (correctly?) set to "n".
> >
> > Is it worth reporting this as a bug, or am I the only one daft enough to
> > perpetrate such an error? Or am I overlooking a valid scenario?
> >
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
> I think that the 'c' status in the SX actually changes to 'n' in the
> created transactions.  Thus there is no 'c' status delivered to a new
> transaction.  Am I correct?

No. I found out because some splits in an Expenses account showed up as 
"cleared" when they obviously shouldn't have.