That all said, unless you plan to go into mass creation of multiple LabVIEW applications for touchpanel displays the effort to create such a library is definitely many times higher than to bite the apple and add the necessary events yourself to your frontpanel VI that needs to have touchpanel keyboard support. So if you use such a solution don't try to register in your own VI the same events again for some further control customization. It results in the situation that it is anyones guess who of the two will receive the actual event so that the behaviour gets erratic. One complication this can pose is that this registers certain events for a control and it is a very bad idea to have two event structures try to register the same event for the same control. Our variant doesn't actually use OSK but implements a control type sensitive LabVIEW popup panel with only a numeric keypad for numeric controls. It's a bit more work than a quick and dirty example VI and while we use such VIs in our company, they can not be distributed publically for copyright reasons.
The background VI can register an event structure for certain events and then perform something in there, such as checking if the OSK is already active and if not activate it and make sure that the original LabVIEW panel and control has still the Key Focus. Write another VI that creates an instance of the background VI and pass it an array of control refnums that you would want to have register for the OSK keyboard (or pass the VI refnum if you want to have all controls register although you don't really need the OSK for buttons for instance. It involves writing a VI library that creates a background task with a dynamically launched VI. It is however far beyond LabVIEW beginners level to make that work. Well there is of course a way to do this without actually having to create the neccessary event cases for mouse events everytime.
0 kommentar(er)
