I don't think this is super important but if you attempt to input a combined emoji you'll get some control characters instead of the actual unicode values. This issue is because gtemp (the temp buffer used to hold both clipboard and unicode inputs) is a char_t[] and not an uint32_t[]. The best solution would be to covert the unicode characters into their char_t equivalents using something similar to char_to_unicode but reversed. Simply casting the uint32_t to a char_t doesn't work here.
I don't think this is super important but if you attempt to input a combined emoji you'll get some control characters instead of the actual unicode values. This issue is because `gtemp` (the temp buffer used to hold both clipboard and unicode inputs) is a `char_t[]` and not an `uint32_t[]`. The best solution would be to covert the unicode characters into their `char_t` equivalents using something similar to `char_to_unicode` but reversed. Simply casting the `uint32_t` to a `char_t` doesn't work here.
Thanks to dff57060c7, I think this will be easier to fix than expected. It's not working as of now but it may just need a small tweak to work.
Thanks to dff57060c76fad8caf7cb4b40e18e545ac58e161, I think this will be easier to fix than expected. It's not working as of now but it may just need a small tweak to work.
Kevin "The Nuclear" Bloom
I don't think this is super important but if you attempt to input a combined emoji you'll get some control characters instead of the actual unicode values. This issue is because
gtemp(the temp buffer used to hold both clipboard and unicode inputs) is achar_t[]and not anuint32_t[]. The best solution would be to covert the unicode characters into theirchar_tequivalents using something similar tochar_to_unicodebut reversed. Simply casting theuint32_tto achar_tdoesn't work here.Thanks to
dff57060c7, I think this will be easier to fix than expected. It's not working as of now but it may just need a small tweak to work.