From 2d08f259934df056404ae6889f466fe6ffc76df2 Mon Sep 17 00:00:00 2001
From: Alexander Zaft <a.zaft@fz-juelich.de>
Date: Wed, 5 Jun 2024 12:44:48 +0200
Subject: [PATCH] mlz: derive Digitaloutput from Drivable

as the underlying entangle *DigitalOutput may be BUSY and frappy.Writable
disallows this.

Change-Id: I6e4861c6d014f59ad4cc2355a438130173bf6569
Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/33849
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>
Reviewed-by: Bjoern Pedersen <bjoern.pedersen@frm2.tum.de>
---
 frappy_mlz/entangle.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frappy_mlz/entangle.py b/frappy_mlz/entangle.py
index 62925af..31f5956 100644
--- a/frappy_mlz/entangle.py
+++ b/frappy_mlz/entangle.py
@@ -909,7 +909,7 @@ class PartialDigitalInput(NamedDigitalInput):
         return value  # mapping is done by datatype upon export()
 
 
-class DigitalOutput(PyTangoDevice, Writable):
+class DigitalOutput(PyTangoDevice, Drivable):
     """A device that can set and read a digital value corresponding to a
     bitfield.
     """