Possible bug in [chooser] object in Windows installation?
Hello Developers,
I might have found a bug in the coding for the [chooser] object in one of the recent releases for Max installed on Windows 11.
If I create a chooser object in a patcher and fill it with some values, clicking on an entry outputs the index number and entry value from outlets 1 and 2 as expected. However, double-clicking the same entry generates no output from outlets three and four as it is supposed to do:

An associate who tried this on his Mac installation appears to get the expected results by double-clicking, although I don't know which version of Max and MacOS he is using.
Interestingly, a project that I have previously built in to a Standalone generates the expected output when double-clicking [chooser] entries and if I build this patcher into an executable it also works correctly:

Is this a bug or is there something in my Windows installation that is preventing double-clicks from acting on the [chooser] in a normal patch window?
Here is the patcher code from this example:
and the same patch code built into an .mxf file:
Thanks, Andy.
My Max support data is as follows:
{
"version" : "Version 8.6.2 (d076223e34e) (x64 windows)",
"platform" : "windows",
"arch" : "x64",
"osversion" : "Microsoft Windows 11 Professional (build 22631), 64-bit",
"samplerate" : 44100,
"iovs" : 512,
"sigvs" : 64,
"scheduler_in_audio_interrupt" : "off",
"audio_drivername" : "ad_mme",
"audio_driver_subname" : "",
"license" : "pace",
"eventinterval" : 2,
"schedinterval" : 1.0,
"overdrive" : "off",
"pollthrottle" : 40,
"queuethrottle" : 100,
"sysqelemthrottle" : 1000,
"refreshrate" : 30.0,
"schedslop" : 25.0,
"eventprobing" : 1,
"mixerparallel" : "off",
"mixercrossfade" : 0,
"mixerlatency" : 30.0,
"mixerramptime" : 10.0,
"videoengine" : "viddll",
"gfxengine" : "glcore",
"packages" : {
"BEAP" : "1.0.4",
"CNMAT Externals" : "1.0.5",
"gl3" : "0.3.3",
"jasch_objects_0_8_3" : "",
"jit.mo" : "1.1.6",
"Jitter Tools" : "1.0.10",
"Max for Live" : "1.0.9",
"max-mxj" : "8.2.0",
"maxforlive-elements" : "1.0.10",
"Mira" : "1.2.1",
"Node for Max" : "2.1.3",
"odot" : "1.3.6",
"RNBO" : "1.2.6",
"Sadam Library" : "23.2.7",
"VIDDLL" : "1.2.8",
"Vizzie" : "2.2.2"
}
}
Hello Andy ...
"An associate who tried this on his Mac installation" just tried it on Windows 10/Max8.6.2
and doubleclick works as expected.