You top level component is a HalRemoteWindow right?
If this is the case you need to switch to ServceWindow and create
multiple HalRemoteComponents to create a working setup.
The HalRemoteComponent looks for pins in child items of the "container"
item. It may be the case that the Tabs aren't
> On 17 May 2017, at 12:04, Klemen Zhivko wrote:
>
> According to my experience I think for connecting remote components both
> components need to have same number (and same type) of pins.
> So if you adding pins in UI you should add them also in hal file.
> I am
According to my experience I think for connecting remote components both
components need to have same number (and same type) of pins.
So if you adding pins in UI you should add them also in hal file.
I am using hal file to create remote comp, but they can be also python
created and mk side.
I
On Thursday, May 11, 2017 at 2:40:36 PM UTC+2, Alexander Rössler wrote:
>
> Make sure your Tab is active: true
>
I've added that, but it doesn't fix the problem.
referring to the thread Marius linked to, do I need to change the
"servicewindow" (whatever that is)?
could you enlighten me a bit?
Hi,
I've been building single QtQuickVCP window UI's in the past, and today I
try to build some tabs into my UI.
I'd like to have a tab with buttons, and a tab with IO's for inspecting HAL
pins. So for this I looked into Machineface and I moved my buttons and hal
pins to a different file.