Re^3: Any event modules that support STDIN polling for Windows?

It sounds like you have a version mismatch between the glib dll you have, and the Perl module.... its a common problem installing c-based modules on win32. If you want an easy way to get it going, put in Camelbox: A build of Gtk2-Perl for Windows , although that will give you a full Gtk2 install, in addition to the Glib base object library.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

Comment on Re^3: Any event modules that support STDIN polling for Windows?

Replies are listed 'Best First'.
Re^4: Any event modules that support STDIN polling for Windows? by KHLeow (Novice) on Aug 30, 2010 at 18:11 UTC
I just found out that I've already had Gtk2 DLLs installed and listed in the Path environment variable. Hence Perl attempted to use those DLLs instead of the ones I've fetched on recommendation by the Perl Package Manager. Since then, I've resolved the conflict and was able to run the piece of code you showed me. However just like most of the other modules that I've tried, it didn't respond to my keypresses.	[reply]
Re^5: Any event modules that support STDIN polling for Windows? by zentara (Cardinal) on Aug 30, 2010 at 18:19 UTC
However just like most of the other modules that I've tried, it didn't respond to my keypresses. I think you have a low level software problem, ( maybe the win32 keystroke recorders are grabbing the keyboard, bwahaha :-)) Seriously, if multiple modules are ALL not responding to keyboard events, it may be a defective operating system. Maybe you need a few of the System patches provided by Microsoft? I'm not really a human, but I play one on earth. Old Perl Programmer Haiku ................... flash japh	[reply]
Re^6: Any event modules that support STDIN polling for Windows? by KHLeow (Novice) on Aug 30, 2010 at 19:03 UTC
My colleagues' are facing the same problem too. I wished MS would release a patch to fix this. I also wished that Perl module creators would not deliberately overlook the compatibility of their works in Windows because I know at least one module that really admitted so in its in-code comments. It doesn't necessarily have to be a downloadable module. It could be a hack as long as it works and doesn't consume noticeable CPU and memory.	[reply]