Sure enough. "loadbang" is complicated because you should allow abstractions to field their loadbangs before everyone else, and once that is done, subpatches before the "main" patch. (Or perhaps I'm overdoing it...)
Krzysztof's fix would give the right number (one a piece) of bangs, but I found that getting the order right as well took a bit more work (to appear in next test version...)
cheers Miller
On Sat, May 11, 2002 at 01:16:10PM +0200, Krzysztof Czaja wrote:
hi Marius, hi Miller,
right, there is a bug in canvas_loadbang()/canvas_loadbangabstractions() combo. It appears to be easy to fix in g_canvas.c: either delete lines 968 and 972, or delete lines 959-960 (test23). But I am somewhat baffled -- actually I do not see any reason why abstractions are handled separately in canvas_loadbang(). Maybe a new feature is going to bang in that requires such differentiation?
Krzysztof
sme wrote: ...
it is a patch with a subpatch, and in the subpatch i have an abstraction that contains a loadbang.