SX oddity

[Geert Janssens]

On Sunday 14 April 2013 15:34:04 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.

This is a good question. I am inclined to agree that you can't have future cleared transactions.

Odds are though the moment we prevent this, a user will complain he/she relied on this very feature ;)

I would suggest to create a bugreport anyway. The register code is currently being rewritten (which includes 
the transaction editor of the sx editor). It's probably a small change while we're in this area.

Geert