v1.0.38 released: Respond to signals from remote controls
Posted 03 September 2005 - 06:58 PM
Fixed the Input command to properly capture keystrokes sent by a hotkey or hotstring for which the user is physically holding down SHIFT, CTRL, ALT, or WIN. [thanks wildfire]
Changed "GuiControl, Text" to set the text of a ComboBox's Edit control rather than new choices for its drop-list. Please update your scripts accordingly.
Improved FileMoveDir with an option to unconditionally overwrite the target folder.
Added built-in function IsLabel(), which verifies that a label exists before you Gosub it. [thanks Tekl]
Added built-in function OnMessage(), which can receive custom messages and monitor system messages.
Added a WinLIRC client script that responds to signals from a hand-held remote control. WinLIRC is an open-source utility that captures infrared signals from virtually any brand of remote control.
Posted 03 September 2005 - 07:38 PM
I can think of many, many ways to use/abuse the OnMessage() function. Time to play...
Posted 03 September 2005 - 07:44 PM
The installer you are trying to use is corrupted or incomplete.
This could be the result of a damaged disk, a failed download or a virus.
You may want to contact the author of this installer to obtain a new copy.
It may be possible to skip this check using the /NCRC command line switch
I only get a 133kb file when downloading
Posted 03 September 2005 - 08:45 PM
I asked for GetMessage I have OnMessage... A dream come true !!!
I will try this feature.
Thanks a lot, Chris !!!
PS : who knows a freeware program to list the messages received by a window ? Witch it is ?
Posted 04 September 2005 - 04:32 AM
Posted 05 September 2005 - 07:41 AM
i can think of some really nice things to start with the new toys u've thrown in ... only if i'd been on my pc!
congratulations on another brilliant release!
Posted 05 September 2005 - 06:09 PM
Fixed GuiContextMenu's A_GuiControl to be non-blank when the user right-clicks a Text, Picture, or Tab control.
Changed OnMessage() to receive LPARAM as an unsigned vs. signed number. If an incoming WPARAM or LPARAM is intended to be a signed value, any negative numbers can be revealed by following this example:
if wParam > 0x7FFFFFFF wParam := -(0xFFFFFFFF - wParam + 1)
Posted 06 September 2005 - 11:10 AM
Currently that is what is stopping the conversion.
Posted 06 September 2005 - 12:12 PM
There might be a way to support your remote by reading from the serial port via DllCall. But unless there's an expert in the house, that would require some research at MSDN, etc. Alternatively, perhaps parts of the WinLIRC source could be adapted to handle more types of serial devices.
Posted 06 September 2005 - 01:26 PM
I assume not as this is an RF remote, not IR. With girder I was/am using a serial plugin with a special ini file configured for this remote. The remote in question is an X10 Mouse remote model MK19A. It has the largest range of any remote I've found. I can get nearly 200 foot range with this remote. As it is also RF, it doesn't require clear line of site.
Posted 06 September 2005 - 01:32 PM
I've been trying to decode AHK to merge the 2 for my own use, but as AHK was compiled in something greater than VC6, I have been stalled in my efforts.
Posted 07 September 2005 - 02:17 AM
You might also try web searches on the combination of "X10 Mouse WinLIRC". I did one on Google and one of the first links was a patch for LIRC (not WinLIRC, but maybe useful to you anyway). It says, "Attached is a diff against current (20030926) CVS which adds a complete driver for the X10 MouseRemote RF receiver (Model JR21A) and remote (Model JR20A)." http://sourceforge.n... ... um_id=5339
There might be better resources than the above, but maybe you've already been down that road.