SX event handler behaviour (was SX Projection Report/SX enable/disable)

[Josh Sled]

On Mon, 2007-02-05 at 01:42 -0500, Peter McAlpine wrote:
> Please find the attached patch:
> 
> - SX instance models properly handle SX update/add/remove events with/ 
> without enabled transactions
> - New SX editors now show non-enabled transactions

Looks good; r15510.  It'd be great if you could add some unit tests for
disabled SX handling in the instance model, and the {en,dis}abled
transitions, but whatever.  I've made a note in sx.rst about the tests.



On Mon, 2007-02-05 at 14:46 -0500, Peter McAlpine wrote: 
> - add a check-box to the SX list tree-view to show the SX enabled  
> status.

On Mon, 2007-02-05 at 17:14 -0500, Peter McAlpine wrote:
> - don't show non-enabled SX's on the SX dense calendar

I combined these two; r15511.   There's a nasty flicker on the dense-cal
as OK is clicked, but I doubt that's related to this patch.


Thanks...
-- 
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20070205/f7aae36e/attachment.bin