Something has been bothering me for quite a while. My software (of course) isn't perfect and every now and then an error occurs. Since pVoice is a GUI application, I let Wx::Perl::Carp (by DH) handle the errors and warnings so a nice dialogbox appears when an error occurs. Depending on the severity of the error it may just be a warning, or it lets die application die.
But what good does such a warning do when you can't click the 'OK' button? pVoice is aimed at exactly those people. I've had multiple occasions when my daughter was confronted with an errormessage that prevented her from continuing working with pVoice. She then has to shout to us, we take a look at her screen, press OK and let her continue. That's not really functional.
So I've started working on AAC::Pvoice-based Dialog windows. With those you can just pop up a window that the user can confirm with a single switch. It has proven to be harder than I thought. Suddenly you no longer have one AAC::Pvoice::Panel that takes control of the input, but multiple of those. However, I'm pretty close to the solution, so another AAC::Pvoice class, 'AAC::Pvoice::Dialog' will be included in the next CPAN release of this module. And then there will also be a AAC::Pvoice::MessageBox, functionally equal to Wx::MessageBox, only with included Accessibility. The next step after that is AAC::Pvoice::Carp so I can catch warnings and errors, display them to the user, and let the same user close the window.
All of this started by creating a first pVoice plugin that needed to inform the user that an action had been taken. I didn't want a short one-line message to appear on a full pVoice window, so I needed a Dialog window....sometimes I make too much out of one small issue....
