03-13-2009 09:40 AM
A simple solution I do around code that I want to keep the user from interacting temporarly with the vi is to set the busy cursor and then unset it when done. You might even be able to load a null cursor but I have not tried this. I try to avoide low level windows dll calls because it can be a problem when MS releases new OS Versions.
03-15-2009 12:05 PM
@ smercurio_fc
Thanks for reply. I use the same function only "paste special" , but without enabling the 2 parameters which you have shown over there. I am able to handle unicode data in my application but problem arouse when i tried to dump in to excel. So my question, will ur code work without having a COPY (Simulate CTRL C in keybord) function before ? If CTRL C required then it will be same code what i have done. Just because I am using CTRL C , i wanted to disable the mouse. Else whatever user selects while application is running may be pasted in the excel ? Or is there anyway of dumping unicoded text in to excel . Its creating lots of headache 😞
03-15-2009 12:08 PM
@ Falkpl
My requirement is not just limited to that VI. Blockinput function (User32dll) will disable both mouse and keybord and i am simulating keybord in my application, so that dll wont work for me anyway
03-16-2009 09:42 AM