- Posts: 128
- Thank you received: 0
QtDragon startup issues if limit/home switch tripped
5 years 6 months ago #204394
by turbostew
Replied by turbostew on topic QtDragon startup issues if limit/home switch tripped
One thing, the only way I can override limits is with the button on the floating msg box. I cannot check the override check box, won't allow it. I fixed it by changing this line in the init_widgets function. (I have actually used this mod for weeks)
self.w.chk_override_limits.setEnabled(True) ##DKS: was False
Kent
self.w.chk_override_limits.setEnabled(True) ##DKS: was False
Kent
Please Log in to join the conversation.
5 years 6 months ago #204396
by cmorley
Replied by cmorley on topic QtDragon startup issues if limit/home switch tripped
can you post the handler file you are using?
Please Log in to join the conversation.
5 years 6 months ago #204397
by cmorley
Replied by cmorley on topic QtDragon startup issues if limit/home switch tripped
also can you see the check marks of the other options? IIRC one style has missing checkmark images
Please Log in to join the conversation.
5 years 6 months ago #204416
by turbostew
Replied by turbostew on topic QtDragon startup issues if limit/home switch tripped
Here you go.... My qss works great.
Please Log in to join the conversation.
5 years 6 months ago #204436
by cmorley
Replied by cmorley on topic QtDragon startup issues if limit/home switch tripped
Ok I think I understand why.
With my testing i always had the screen running before tripping the limit.
I think if the limit is set before the screen starts, it would not send the proper gobject message to catch it.
I added a change so it always forces the message on start up - I bet it works properly now.
With my testing i always had the screen running before tripping the limit.
I think if the limit is set before the screen starts, it would not send the proper gobject message to catch it.
I added a change so it always forces the message on start up - I bet it works properly now.
Please Log in to join the conversation.
Time to create page: 0.042 seconds
