You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you for the efforts you put into this. I am trying to write an application that will send a key sequence when the F2key is pressed. However this string is not known during compile time and I generate it at run time. For this I am using the lazy_static macro to initialize the string during run time. Here's what my code looks like:
The println line works fine for this, but the KeySequence line does not. I have verified that the binding works well if I just pass it a string literal, however I do not get any output when I pass the static MY_STRING in this way.
The binding is probably working fine, as the program stops and wait instead of just exiting. Other bindings also function. However, it seems that nothing is getting passed to the send() method when ran this way. Any ideas why this might be happening? Thank you.
Edit: I'm running this on a RHEL-8 machine.
The text was updated successfully, but these errors were encountered:
First of all thank you for the efforts you put into this. I am trying to write an application that will send a key sequence when the
F2key
is pressed. However this string is not known during compile time and I generate it at run time. For this I am using thelazy_static
macro to initialize the string during run time. Here's what my code looks like:The
println
line works fine for this, but theKeySequence
line does not. I have verified that the binding works well if I just pass it a string literal, however I do not get any output when I pass the staticMY_STRING
in this way.The binding is probably working fine, as the program stops and wait instead of just exiting. Other bindings also function. However, it seems that nothing is getting passed to the
send()
method when ran this way. Any ideas why this might be happening? Thank you.Edit: I'm running this on a RHEL-8 machine.
The text was updated successfully, but these errors were encountered: