I've discovered a rather obscure issue with sensekey when run in Lettuce
executable format. Basically, sensekey returns different data when run from
the commandline vs. through Lettuce/API. (I say "Lettuce/API" as I've no
idea which may be responsible for the differences.)

The attached .csd demonstrates these differences. Run from the commandline,
sensekey is wonderful: shifted numerics give different ASCII values, as does
Caps Lock; the "format keys" (Insert/Delete, Home/End, Page Up/Down) and the
cursor keys all give appropriate ASCII output.

Not so with Lettuce/API. Though shift works appropriately with
non-alphabetic characters, Caps Lock does not; it gives the same ASCII
output as unshifted characters. More importantly, it does not output ASCII
for either the "format" or cursor keys. This is likely why on the extended
keypad, an *unlocked* Num Lock doesn't output any ASCII values for
keypresses either (the unlocked functions being those same "format" and
cursor keys).

The only reason why any of this is important to me is that I'm trying to do
versions of a few of my pieces with only an extended keypad as controller.
And I'm in need of some of these unlocked Num Lock functions (not enough
keys otherwise).

I'd appreciate Rory and others looking at this situation and trying to
determine the reason for the described differences in behavior. Anyone with
Lettuce and ASCII keyboard (with extended keypad) can run the attachment
both ways. When running the Lettuce executable, start Csound and open the
std output window, but *select* the main performance window. (Otherwise keys
pressed will appear as *text* in std out.)

Thanks very much.

Art Hunkins

Most likely this has nothing to do with the Csound API, but with the
GUI framework used by Lettuce. Because the command-line
uses the API as much as Lettuce (in fact all of Csound frontends
do).

Victor

At 05:42 03/09/2007, you wrote:
>I've discovered a rather obscure issue with sensekey when run in Lettuce
>executable format. Basically, sensekey returns different data when run from
>the commandline vs. through Lettuce/API. (I say "Lettuce/API" as I've no
>idea which may be responsible for the differences.)
>
>The attached .csd demonstrates these differences. Run from the commandline,
>sensekey is wonderful: shifted numerics give different ASCII values, as does
>Caps Lock; the "format keys" (Insert/Delete, Home/End, Page Up/Down) and the
>cursor keys all give appropriate ASCII output.
>
>Not so with Lettuce/API. Though shift works appropriately with
>non-alphabetic characters, Caps Lock does not; it gives the same ASCII
>output as unshifted characters. More importantly, it does not output ASCII
>for either the "format" or cursor keys. This is likely why on the extended
>keypad, an *unlocked* Num Lock doesn't output any ASCII values for
>keypresses either (the unlocked functions being those same "format" and
>cursor keys).
>
>The only reason why any of this is important to me is that I'm trying to do
>versions of a few of my pieces with only an extended keypad as controller.
>And I'm in need of some of these unlocked Num Lock functions (not enough
>keys otherwise).
>
>I'd appreciate Rory and others looking at this situation and trying to
>determine the reason for the described differences in behavior. Anyone with
>Lettuce and ASCII keyboard (with extended keypad) can run the attachment
>both ways. When running the Lettuce executable, start Csound and open the
>std output window, but *select* the main performance window. (Otherwise keys
>pressed will appear as *text* in std out.)
>
>Thanks very much.
>
>Art Hunkins
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Art, I'm currently holidaying in France for a few days, this issue 
has popped up before so I have a good idea of how to fix it. The waves 
haven't been great so the surf is poor here, who knows I may get a 
chance to fix it before I get back! Cheers,

Rory.


Art Hunkins wrote:
> I've discovered a rather obscure issue with sensekey when run in Lettuce
> executable format. Basically, sensekey returns different data when run from
> the commandline vs. through Lettuce/API. (I say "Lettuce/API" as I've no
> idea which may be responsible for the differences.)
> 
> The attached .csd demonstrates these differences. Run from the commandline,
> sensekey is wonderful: shifted numerics give different ASCII values, as does
> Caps Lock; the "format keys" (Insert/Delete, Home/End, Page Up/Down) and the
> cursor keys all give appropriate ASCII output.
> 
> Not so with Lettuce/API. Though shift works appropriately with
> non-alphabetic characters, Caps Lock does not; it gives the same ASCII
> output as unshifted characters. More importantly, it does not output ASCII
> for either the "format" or cursor keys. This is likely why on the extended
> keypad, an *unlocked* Num Lock doesn't output any ASCII values for
> keypresses either (the unlocked functions being those same "format" and
> cursor keys).
> 
> The only reason why any of this is important to me is that I'm trying to do
> versions of a few of my pieces with only an extended keypad as controller.
> And I'm in need of some of these unlocked Num Lock functions (not enough
> keys otherwise).
> 
> I'd appreciate Rory and others looking at this situation and trying to
> determine the reason for the described differences in behavior. Anyone with
> Lettuce and ASCII keyboard (with extended keypad) can run the attachment
> both ways. When running the Lettuce executable, start Csound and open the
> std output window, but *select* the main performance window. (Otherwise keys
> pressed will appear as *text* in std out.)
> 
> Thanks very much.
> 
> Art Hunkins
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net