Interestingly enough, this sample.pl does not work as advertised on my Windows 10 machine.
When it starts, "TEST SUITE" is flashing. It says, "Press any key or mouse button to proceed". However, no mouse click will work, although pressing any other key will work.

I believe that the 1 second sleep idea is a "red herring" -> doesn't matter. All that means is that it will take at most one second for the keyboard event to be seen. A normal assumption would be that if you don't poll fast enough, you miss a character because apparently (not sure) that the event stack is only one character deep?

I did play around with the Properties of my standard command window. I turned off any of the normal fancy CTL-V or CTL-C off. But I haven't found the "magic formula" yet. In my testing with short programs, I am seeing that a right click causes the following program to "hang". When the program starts, hitting a normal key produces expected results, but a mouse click gets you nowhere!

I have seen other test programs fail to see the Right-Click. When the test program exits, I get the normal CTL-V behavior. Somehow the Mouse Click is not getting to the running test program and is buffered and presented to the command shell when the test program exits. The correct voo-doo for Console should be able to get this character (mouse click).

I am curious as to what others find. The sample code is complex and I am just trying to find a simple subset that works. This does not. 

# https://docs.microsoft.com/en-us/windows/console/reading-input-buffe
+r-events\
# reference Perl Monks: https://www.perlmonks.org/?node_id=1212227

use strict;
use warnings;

use Win32::Console; 

my $OUT = new Win32::Console(STD_OUTPUT_HANDLE);
my $IN  = new Win32::Console(STD_INPUT_HANDLE);

$OUT->Write("Perl version $^V \n");
$OUT->Write("more text could go here\n\n");
my $n_buttons = $IN->MouseButtons();
$OUT->Write("Your mouse has $n_buttons buttons\n");
$IN->Mode(ENABLE_MOUSE_INPUT);

my $counter = 0;

while ($counter++ < 5) #5x time out for testing...
{
    if (my @console_events = $IN -> Input ())
    {
       $OUT->Write ("calling input method!\n");
       # my @console_events = $IN -> Input ();  ##not needed goof (COR
+RECTION)
       $OUT->Write ("An Event was detected! number= ".@console_events.
+"\n");
       
       foreach my $event (@console_events)
       {
           $OUT->Write("event: $event\n");
       }

       exit;   #   exit the program, do not fall through to that final
+ print instruction
     }
     else
     {
       sleep 1;  #should be fine to poll 1x per second for testing...
     }
}
$OUT->Write("Timed out! Bummer!\n");

[download]

In reply to Re^2: Unable to capture mouse events in Win32::Console by Marshall
in thread Unable to capture mouse events in Win32::Console by fireblood

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.