Yeah, I've played around with that one a little, also. I read in an interview with the founder of OSH Park that more than 50% of the boards the produce are designed using KiCad. That's a pretty solid endorsement.
Hmm... That'll probably work well after I've converted my code to a state machine since the bounce would be sorted out before the dwell time is up anyway. Thanks.Try doing trigger debounce only on the release. You want your firing sequence to begin as soon as the first trigger signal is available and debouncing it on the pull will add an unnecessary delay.
The debounce code I'm using doesn't seem to waste a lot of time, though. Instead of delaying, it waits for a certain number of consistent, sequential reads. That's configurable, now, but I'm playing around with the idea of making it automatically debounce itself without having to set anything, by tracking the number of bounce signals there are per shot. I haven't written any code to that effect yet, but I'll probably get to it within the next week or so.