|
|
Post by emagein on Jan 28, 2020 18:15:06 GMT
Hi, I've been experimenting with LEA for a bit and was wondering if it can run without being tied to a particular program. For example, I have created a simple numpad that augments my current keyboard. I'd like to be able to use the numpad in various programs, but there seems to be a limitation in that I have to choose an active program to tie the project to. Is there any way around this?
Also, as part of the virtual numpad, I have placed a NumLock key I have figured out how to use the toggle button to switch it on and off, but every time I start the project, there is a single uncalled activation of the NumLock key. I have traced it to the release trigger for the macro, but I'm not sure if there is a way to avoid that activation. Note that NumLock is not the only key affected; any key I place into trigger:released will have the same issue. Is this a bug in LEA?
|
|
psyral
New Member
Love this app
Posts: 45 
|
Post by psyral on Jan 28, 2020 18:58:44 GMT
Hi, I've been experimenting with LEA for a bit and was wondering if it can run without being tied to a particular program. For example, I have created a simple numpad that augments my current keyboard. I'd like to be able to use the numpad in various programs, but there seems to be a limitation in that I have to choose an active program to tie the project to. Is there any way around this? Also, as part of the virtual numpad, I have placed a NumLock key I have figured out how to use the toggle button to switch it on and off, but every time I start the project, there is a single uncalled activation of the NumLock key. I have traced it to the release trigger for the macro, but I'm not sure if there is a way to avoid that activation. Note that NumLock is not the only key affected; any key I place into trigger:released will have the same issue. Is this a bug in LEA? I don't have mine attached to any program (because I run tests into a test program I wrote to make sure I have everything correct). If you rightclick on the LEA System Tray Launcher and then click on Enable Remote Mode. - Note: I have mine running as Admin - Not sure if that matters. This will allow your LEA to work under any program. |
|
|
|
Post by emagein on Jan 28, 2020 20:00:27 GMT
Beautiful! That's exactly what I was looking for. Thanks psyral! That's solved one problem.
I'm still scratching my head on the second problem. I'm probably doing something wrong due to ignorance. Looking at the macro code, when the trigger is released, it should send a 'send pressed' key followed by a 'send released' key. That should toggle NumLock off. In practice, it works correctly, but when starting for the first time, this code will trigger the NumLock once. I've tried loading a few projects that were bundled with LEA, and it appears to occur on other projects as well. I guess this is probably a bug or the way that LEA operates.
|
|
psyral
New Member
Love this app
Posts: 45
|
Post by psyral on Jan 28, 2020 23:19:16 GMT
Beautiful! That's exactly what I was looking for. Thanks psyral! That's solved one problem. I'm still scratching my head on the second problem. I'm probably doing something wrong due to ignorance. Looking at the macro code, when the trigger is released, it should send a 'send pressed' key followed by a 'send released' key. That should toggle NumLock off. In practice, it works correctly, but when starting for the first time, this code will trigger the NumLock once. I've tried loading a few projects that were bundled with LEA, and it appears to occur on other projects as well. I guess this is probably a bug or the way that LEA operates. That's probably related to this issue that another user was having: leaextendedinput.freeforums.net/post/160/threadI don't think we came up with an acceptable solution to this yet. Maybe post in the suggestions for the LEA developers to add an option to the toggle button on whether to autofire on startup or not. I think it may come down to a change that LEA has to make. I personally think an option setting on the toggle buttons is the best way and will provide backwards comparability so that previous setups don't break in a new version. |
|
|
|
Post by emagein on Jan 29, 2020 4:22:09 GMT
Yup, looks like the thread was discussing a similar issue that I'm facing. I skipped reading it earlier as it appeared to deal with multiple macros. In hindsight, the problem that rekrapt mentioned describes my issue as well. I guess one possible 'fix' would be to have a dedicated initialise button to reset all the 'accidentally' triggered macros so that the interface starts in a pristine state.
|
|
psyral
New Member
Love this app
Posts: 45
|
Post by psyral on Jan 31, 2020 0:11:59 GMT
Yup, looks like the thread was discussing a similar issue that I'm facing. I skipped reading it earlier as it appeared to deal with multiple macros. In hindsight, the problem that rekrapt mentioned describes my issue as well. I guess one possible 'fix' would be to have a dedicated initialise button to reset all the 'accidentally' triggered macros so that the interface starts in a pristine state. Looks like a solution may be coming in the next update. leaextendedinput.freeforums.net/post/196/thread |
|
