03-08-2019 12:24 AM
No, the VI key events are registered only by the main FP containing the subpanels. However: after clicking into one of the string controls mentioned above one is able to tab through the subpanel then, but key events still registered only by the main panel, even then the tab events ...
11-22-2024 06:08 AM
As far as I can see this is *still* an issue with subpanes...nothing has changed since 2019, or? Not having keyboard navigation available just due to using subpanes seems quite silly 😮
11-22-2024 07:22 AM
This works.
11-22-2024 09:26 AM - edited 11-22-2024 09:27 AM
Not exactly a tab-navigational experience that...but yes, if you e.g. do a key detection detecting the tab key, then check if the last (or prior one to the subpane's first) in the key order on the main has focus, you can send a message e.g. to the subpane-VI to put focus on its first control, then tab onwards from there. Then you have to do the reverse when getting to the last control in the tabbing order in the subVI to get focus back up to the main... 🙄
LabVIEW should handle this automatically based on the key order of the given subpane and whatever VI is on display there.
11-25-2024 01:16 AM
Here is a demo of the method I described (without the tab-navigation back to the main panel, but that would just be the same logic but in reverse...). Messy.
11-25-2024 11:02 AM
To have tab navigation between panels, this might be a simple solution:
11-26-2024 02:09 AM
@Yamaeda: The subpane container itself does not need any key focus (in fact in most cases you do not want anyone to know about it anyway). But yes, the technique you show is the same as I posted, but with the exception that a notification is sent to the VI in the subpane to make it grab the key focus to its first control.