tauruslib-devel — taurus development mailing list

[tauruslib-devel] [PATCH] Fix-292

[cfalcon <cf...@ce...>]

ModelChooser is not Tango agnostic and raises an exception when
you access to the ModelChooser from a widget that has set an other
scheme model. e.g. eval

Do the validation only only for tango devices.
---
 lib/taurus/qt/qtgui/panel/taurusmodellist.py | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/lib/taurus/qt/qtgui/panel/taurusmodellist.py b/lib/taurus/qt/qtgui/panel/taurusmodellist.py
index a432a8c..214c291 100644
--- a/lib/taurus/qt/qtgui/panel/taurusmodellist.py
+++ b/lib/taurus/qt/qtgui/panel/taurusmodellist.py
@@ -33,6 +33,7 @@ import copy
 
 from taurus.external.qt import Qt
 import taurus
+from taurus.core.taurushelper import getSchemeFromName
 from taurus.core.taurusbasetypes import TaurusElementType
 from taurus.core.taurusexception import TaurusException
 from taurus.qt.qtcore.mimetypes import TAURUS_MODEL_LIST_MIME_TYPE, TAURUS_ATTR_MIME_TYPE, TAURUS_MODEL_MIME_TYPE
@@ -101,10 +102,11 @@ class TaurusModelItem(object):
                 self.display, self.icon, self.ok = src, getThemeIcon(
                     'network-error'), False
                 return
-            if dev.getDeviceProxy() is None:
-                self.display, self.icon, self.ok = src, getThemeIcon(
-                    'network-error'), False
-                return
+            if getSchemeFromName(attr.getFullName()) == "tango":
+                if dev.getDeviceProxy() is None:
+                    self.display, self.icon, self.ok = src, getThemeIcon(
+                        'network-error'), False
+                    return
             self.display, self.icon, self.ok = attr.getSimpleName(
             ), getElementTypeIcon(TaurusElementType.Attribute), True
 
-- 
2.4.0

[tauruslib-devel] [PATCH] Fix bug#293

[cfalcon <cf...@ce...>]

TaurusWheelEdit does not show the arrow icons. Fix it.
---
 lib/taurus/qt/qtgui/input/qwheel.py | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)
 mode change 100644 => 100755 lib/taurus/qt/qtgui/input/qwheel.py

diff --git a/lib/taurus/qt/qtgui/input/qwheel.py b/lib/taurus/qt/qtgui/input/qwheel.py
old mode 100644
new mode 100755
index 44985be..3e55052
--- a/lib/taurus/qt/qtgui/input/qwheel.py
+++ b/lib/taurus/qt/qtgui/input/qwheel.py
@@ -35,11 +35,10 @@ import numpy
 
 from taurus.external.qt import Qt
 
-
 class _ArrowButton(Qt.QPushButton):
     """Private class to be used by QWheelEdit for an arrow button"""
 
-    ArrowPixmapName = ":/arrow01.svg"
+    ArrowPixmapName = "extra_icons:arrow01.svg"
 
     ButtonSize = 14
     IconSize = ButtonSize - 2
@@ -71,7 +70,7 @@ class _UpArrowButton(_ArrowButton):
     def getPixmap(self):
         pm = Qt.QPixmapCache.find(_UpArrowButton.ArrowPixmapKey)
         if pm is None:
-            pm = Qt.QPixmap(_UpArrowButton.ArrowPixmapName)
+            pm = Qt.QPixmap(self.ArrowPixmapName)
             Qt.QPixmapCache.insert(_UpArrowButton.ArrowPixmapKey, pm)
         return pm
 
@@ -88,12 +87,11 @@ class _DownArrowButton(_ArrowButton):
     def getPixmap(self):
         pm = Qt.QPixmapCache.find(_DownArrowButton.ArrowPixmapKey)
         if pm is None:
-            pm = Qt.QPixmap(_DownArrowButton.ArrowPixmapName)
+            pm = Qt.QPixmap(self.ArrowPixmapName)
             pm = pm.transformed(Qt.QMatrix().rotate(180))
             Qt.QPixmapCache.insert(_DownArrowButton.ArrowPixmapKey, pm)
         return pm
 
-
 class _DigitLabel(Qt.QLabel):
     """A private single digit label to be used by QWheelEdit widget"""
 
-- 
2.4.0

[tauruslib-devel] [PATCH] Fix bug#285

[cfalcon <cf...@ce...>]

QWheelEdit setValue method expects to receive a float but a Quantity
is given.

Use the magnitude when works with Quantity.
---
 lib/taurus/qt/qtgui/input/qwheel.py | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/lib/taurus/qt/qtgui/input/qwheel.py b/lib/taurus/qt/qtgui/input/qwheel.py
index 44985be..d013fa2 100644
--- a/lib/taurus/qt/qtgui/input/qwheel.py
+++ b/lib/taurus/qt/qtgui/input/qwheel.py
@@ -34,6 +34,7 @@ import math
 import numpy
 
 from taurus.external.qt import Qt
+from taurus.external.pint import Q_
 
 
 class _ArrowButton(Qt.QPushButton):
@@ -612,8 +613,10 @@ class QWheelEdit(Qt.QFrame):
         Sets the value of this widget.
         Send a 'valueChanged(double)' Qt signal
 
-        @param[in] v (float) the value to be set
+        @param[in] v (float/Quantity) the value to be set
         """
+        if isinstance(v, Q_):
+            v = v.magnitude
         self._setValue(v)
         self._updateValue(trigValueEdited=False)
 
-- 
2.4.0

Re: [tauruslib-devel] [PATCH] fix bug-269

[Zbigniew R. <zre...@ce...>]

Hi Carlos,

I have reviewed the patches and tested them on the develop branch using 
"taurusgui example01".
For me they are ok.

Cheers,
Zibi

On 05/17/2016 01:49 PM, cpa...@ce... wrote:
> This series of 3 patches fixes bug-269.
> [PATCH 1/3] (m, PEP8) Fix long lines
> [PATCH 2/3] Fix bug-269: store Autoscroll tool state in config
> [PATCH 3/3] Fix scale problem when autoscroll is set before model
>
> The first is a minor, pep8 correction.
> The second is the bug fix proper.
> The third fixes a bug that was already there but which is now more evident
> because standard 2D trends may be initialized with autoscroll=true
> (before it only occurred in custom trend widgets)
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

[tauruslib-devel] [PATCH] Fix copy&paste errors in logging msgs

[Zbigniew R. <zre...@ce...>]

From: zreszela <zre...@ce...>

---
 lib/taurus/qt/qtgui/button/test/res/Timeout | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/taurus/qt/qtgui/button/test/res/Timeout b/lib/taurus/qt/qtgui/button/test/res/Timeout
index c6d33ec..a4a421c 100755
--- a/lib/taurus/qt/qtgui/button/test/res/Timeout
+++ b/lib/taurus/qt/qtgui/button/test/res/Timeout
@@ -106,13 +106,13 @@ class Timeout(PyTango.Device_4Impl):
 
     @PyTango.DebugIt()
     def read_Timeout_attr(self, the_att):
-        self.info_stream("read_Long_attr")
+        self.info_stream("read_Timeout_attr")
         time.sleep(self.attr_duration)
         the_att.set_value(self.attr_duration)
 
     @PyTango.DebugIt()
     def write_Timeout_attr(self, the_att):
-        self.info_stream("write_Short_attr_rw")
+        self.info_stream("write_Timeout_attr")
         self.attr_duration = the_att.get_write_value()
         time.sleep(self.attr_duration)
 
-- 
1.8.4.5

[tauruslib-devel] [PATCH] to accept RGB DevEncodeds.

[Sergi Blanch-T. <sb...@ce...>]

---
 lib/taurus/qt/qtgui/extra_guiqwt/builder.py | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/builder.py
b/lib/taurus/qt/qtgui/extra_guiqwt/builder.py
index de29019..495b01e 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/builder.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/builder.py
@@ -32,7 +32,7 @@ __docformat__ = 'restructuredtext'
 import guiqwt.builder

 from curve import TaurusCurveItem, TaurusTrendItem
-from image import TaurusImageItem, TaurusRGBImageItem,
TaurusEncodedImageItem, TaurusXYImageItem
+from image import TaurusImageItem, TaurusRGBImageItem,
TaurusEncodedImageItem, TaurusEncodedRGBImageItem, TaurusXYImageItem
 from guiqwt.curve import CurveParam
 from guiqwt.image import ImageParam, XYImageItem
 from guiqwt.styles import XYImageParam
@@ -137,11 +137,14 @@ class
TaurusPlotItemBuilder(guiqwt.builder.PlotItemBuilder):
                                  xmin=xmin, xmax=xmax, ymin=ymin,
ymax=ymax,
                                  xformat=xformat, yformat=yformat,
                                  zformat=zformat)
+            from taurus import Attribute
+            from taurus.core import DataType
             if forceRGB:
-                image = TaurusRGBImageItem(param)
+                if Attribute(taurusmodel).getType() == DataType.DevEncoded:
+                    image = TaurusEncodedRGBImageItem(param)
+                else:
+                    image = TaurusRGBImageItem(param)
             else:
-                from taurus import Attribute
-                from taurus.core import DataType
                 if Attribute(taurusmodel).getType() == DataType.DevEncoded:
                     image = TaurusEncodedImageItem(param)
                 else:
-- 
2.1.4

[tauruslib-devel] [PATCH] remove useless warning.

[Sergi Blanch-T. <sb...@ce...>]

---
 lib/taurus/core/util/codecs.py | 2 --
 1 file changed, 2 deletions(-)

diff --git a/lib/taurus/core/util/codecs.py b/lib/taurus/core/util/codecs.py
index 0fde2e0..d39701f 100644
--- a/lib/taurus/core/util/codecs.py
+++ b/lib/taurus/core/util/codecs.py
@@ -527,8 +527,6 @@ class VideoImageCodec(Codec):
         :return: (sequence[str, obj]) a sequence of two elements where
the first item is the encoding format of the second item object"""

         if data[0].startswith('VIDEO_IMAGE'):
-            self.warning(('"VIDEO_IMAGE" format name is deprecated.' +
-                          'Use "videoimage" instead'))
             fixedformat = data[0].replace('VIDEO_IMAGE', 'videoimage')
             _, _, fmt = fixedformat.partition('_')
         elif data[0].startswith('videoimage'):
-- 
2.1.4

[tauruslib-devel] [PATCH] Generalize the LimaCCDs code to the ImageCounterDevice.

[Sergi Blanch-T. <sb...@ce...>]

I've been reported, when the model is an ImgGrabber or an
ImgBeamAnalyzer the image is not refresh with the events emitted by the
ImageCounter.

I've seen that LimaCCDs works and move it to the superclass to make it
work for all of them. Tested with an ImgGrabber, an ImgBeamAnalyser and
a LimaCCDs.

---
 lib/taurus/core/tango/img/img.py | 69
+++++++++++++++++++++++-----------------
 1 file changed, 40 insertions(+), 29 deletions(-)

diff --git a/lib/taurus/core/tango/img/img.py
b/lib/taurus/core/tango/img/img.py
index a152ce8..1f2b6e8 100644
--- a/lib/taurus/core/tango/img/img.py
+++ b/lib/taurus/core/tango/img/img.py
@@ -35,7 +35,6 @@ __docformat__ = 'restructuredtext'
 from taurus.core.taurusbasetypes import TaurusEventType
 from taurus.core.tango import TangoDevice
 from taurus.core.util.containers import CaselessDict, CaselessList
-from threading import RLock


 class ImageDevice(TangoDevice):
@@ -65,10 +64,13 @@ class ImageCounterDevice(ImageDevice):
     """A class encapsulating a generic image device that has an image
counter
     attribute"""

-    def __init__(self, name, image_name='image', **kw):
+    def __init__(self, name, image_name='image', image_ct='imagecounter',
+                 **kw):
         self._image_data = CaselessDict()
-        self.call__init__(ImageDevice, name, **kw)
-        self._image_id_attr = self.getAttribute(self.getImageIDAttrName())
+        self.call__init__(ImageDevice, name, image_name, **kw)
+        self._image_id_attr_name = image_ct
+        self._busy = False
+        self._image_id_attr = self.getAttribute(self._image_id_attr_name)
         self._image_id_attr.addListener(self)

     def _setDirty(self, names=None):
@@ -82,21 +84,46 @@ class ImageCounterDevice(ImageDevice):
         dirty = []
         for name in names:
             d = self._image_data.get(name)
-            if d is None or d[0] == True:
+            if d is None or d[0]:
                 dirty.append(name)
         return names

     def getImageIDAttrName(self):
-        return 'imagecounter'
+        return self._image_id_attr_name

     def eventReceived(self, evt_src, evt_type, evt_value):
         if evt_src == self._image_id_attr:
             if evt_type == TaurusEventType.Change:
-                self._setDirty()
-                self.fireEvent(evt_type, evt_value)
+                if not self._busy:
+                    self.debug("Processing image %d" % evt_value.value)
+                    # discared events if there is one being processed
+                    self._busy = True
+                    # read the related Image attributes
+                    # (asap and in one action)
+                    images = self.getImageData()
+                    self._setDirty()
+                    self.fireEvent(evt_type, evt_value)
+                    # maintain this fireEvent for backwards compatibility
+                    # with Qub widget
+                    self._emitImageEvents(evt_type, images)
+                    self._busy = False
+                else:
+                    self.debug("Discard image %d" % evt_value.value)
         else:
             ImageDevice.eventReceived(self, evt_src, evt_type, evt_value)

+    def _emitImageEvents(self, evt_type, images):
+        for attr_image_name in images:
+            image_value = images[attr_image_name][1]
+            if hasattr(image_value, 'is_empty') and not
image_value.is_empty:
+                self.debug("fireEvent for %s attribute" % attr_image_name)
+                if not hasattr(image_value, 'rvalue'):
+                    image_value.rvalue = image_value.value
+                # Only emit to upper layers the events where
+                # something has been read.
+                attr_image = self.getAttribute(image_value.name)
+                attr_image.fireEvent(evt_type, image_value)
+
     def getImageData(self, names=None):
         if names is None:
             names = self.getImageAttrNames()
@@ -151,24 +178,8 @@ class ImgBeamAnalyzer(ImageCounterDevice):

 class LimaCCDs(ImageCounterDevice):

-    def __init__(self, name, image_name='video_last_image', **kw):
-        self.call__init__(ImageCounterDevice, name, image_name, **kw)
-        self.rlock = RLock()
-        self.processing = False
-
-    def getImageIDAttrName(self):
-        return 'video_last_image_counter'
-
-    def eventReceived(self, evt_src, evt_type, evt_value):
-        if evt_src == self._image_id_attr and self.processing == False:
-            if evt_type == TaurusEventType.Change:
-                with self.rlock:
-                    self.processing = True
-                    attr_image = self.getAttribute('video_last_image')
-                    evt_value = attr_image.read(False)
-                    attr_image.fireEvent(evt_type, evt_value)
-                    self.processing = False
-
-        else:
-            ImageCounterDevice.eventReceived(
-                self, evt_src, evt_type, evt_value)
+    def __init__(self, name, image_name='video_last_image',
+                 image_ct='video_last_image_counter', **kw):
+        self.call__init__(ImageCounterDevice, name, image_name,
image_ct, **kw)
+        self.debug("Prepared to listen image counter (%s) for the %s
images"
+                   % (self.getImageIDAttrName(), self.getImageAttrNames()))
-- 
2.1.4

[tauruslib-devel] [PATCH 2/3] Fix bug-269: store Autoscroll tool state in config

[<cpa...@ce...>]

From: cpascual <cpa...@ce...>

TaurusTrend2D does not "remember" the state of its AutoScroll setting.
Fix by making the AutoScrollTool object inherit from
BaseConfigurableClass, and registering its check state (and registering
the tool as a config delegate for the TaurusTrend2DDialog).

Also: register the tool as a config delegate for TaurusTrend1DDialog too
---
 lib/taurus/qt/qtgui/extra_guiqwt/plot.py          |  1 +
 lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py |  1 +
 lib/taurus/qt/qtgui/extra_guiqwt/tools.py         | 10 +++++++---
 3 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/plot.py b/lib/taurus/qt/qtgui/extra_guiqwt/plot.py
index 50ebf1b..dfbadc2 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/plot.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/plot.py
@@ -215,6 +215,7 @@ class TaurusTrendDialog(CurveDialog, TaurusBaseWidget):
             taurusparam = TaurusTrendParam()
         self.defaultTaurusparam = taurusparam
         self.setContextMenuPolicy(Qt.Qt.CustomContextMenu)
+        self.registerConfigDelegate(self.get_tool(AutoScrollTool))
 
     def keyPressEvent(self, event):
         if(event.key() == Qt.Qt.Key_Escape):
diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py b/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
index a941d91..fecd088 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
@@ -70,6 +70,7 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
         self.get_tool(TaurusModelChooserTool).singleModel = True
         self.setModifiableByUser(self._modifiableByUser)
         self.setContextMenuPolicy(Qt.Qt.CustomContextMenu)
+        self.registerConfigDelegate(self.get_tool(AutoScrollTool))
 
     def keyPressEvent(self, event):
         if(event.key() == Qt.Qt.Key_Escape):
diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
index 124f57a..ae03eb3 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
@@ -35,6 +35,7 @@ from guiqwt.tools import (CommandTool, ToggleTool, DefaultToolbarID,
 from guiqwt.signals import SIG_ITEMS_CHANGED
 
 from taurus.core.taurusbasetypes import TaurusElementType
+from taurus.qt.qtcore.configuration import BaseConfigurableClass
 from taurus.qt.qtgui.resource import getIcon
 from taurus.qt.qtgui.extra_guiqwt.builder import make
 from taurus.qt.qtgui.extra_guiqwt.curve import TaurusCurveItem, TaurusTrendItem
@@ -213,17 +214,20 @@ class TimeAxisTool(CommandTool):
         self._setPlotTimeScales(True, True)
 
 
-class AutoScrollTool(ToggleTool):
+class AutoScrollTool(ToggleTool, BaseConfigurableClass):
     """A tool that puts the plot in "AutoScroll" mode.
     This makes sense in trend plots where we want to keep the last value
     always visible"""
 
     def __init__(self, manager, scrollFactor=0.2, toolbar_id=None):
-        super(AutoScrollTool, self).__init__(
-                manager, title='Auto Scroll', icon=None,
+        ToggleTool.__init__(self, manager, title='Auto Scroll', icon=None,
                 tip='Force X scale to always show the last value',
                 toolbar_id=toolbar_id)
+        BaseConfigurableClass.__init__(self)
         self.scrollFactor = scrollFactor
+        self.registerConfigProperty(self.action.isChecked,
+                                    self.action.setChecked,
+                                    'actionChecked')
 
     def register_plot(self, baseplot):
         ToggleTool.register_plot(self, baseplot)
-- 
2.8.1

[tauruslib-devel] [PATCH 3/3] Fix scale problem when autoscroll is set before model

[<cpa...@ce...>]

From: cpascual <cpa...@ce...>

In TaurusTrend2D, setting the autoscroll before the model triggers a bug
that permanently sets the scale range to min,max = 0,0, preventing
correct display of the data. Fix it by ignoring scroll requests before
the axis is properly set.
---
 lib/taurus/qt/qtgui/extra_guiqwt/tools.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
index ae03eb3..4521312 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
@@ -251,6 +251,9 @@ class AutoScrollTool(ToggleTool, BaseConfigurableClass):
     def onScrollRequested(self, plot, axis, value):
         scalemin, scalemax = plot.get_axis_limits(axis)
         scaleRange = abs(scalemax - scalemin)
+        # ignore requests that imply setting a null range
+        if scaleRange == 0:
+            return
         xmin = value - scaleRange * (1. - self.scrollFactor)
         xmax = value + scaleRange * self.scrollFactor
         plot.set_axis_limits(axis, xmin, xmax)
-- 
2.8.1

[tauruslib-devel] [PATCH 1/3] (m, PEP8) Fix long lines

[<cpa...@ce...>]

From: cpascual <cpa...@ce...>

---
 lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py | 87 +++++++++++++----------
 lib/taurus/qt/qtgui/extra_guiqwt/tools.py         | 58 +++++++++------
 2 files changed, 85 insertions(+), 60 deletions(-)

diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py b/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
index f767fa2..a941d91 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/taurustrend2d.py
@@ -33,28 +33,30 @@ from taurus.external.qt import Qt
 import taurus.core
 from taurus.qt.qtgui.base import TaurusBaseWidget
 from taurus.qt.qtgui.extra_guiqwt.image import TaurusTrend2DItem
-from taurus.qt.qtgui.extra_guiqwt.tools import TaurusModelChooserTool, TimeAxisTool, AutoScrollTool
+from taurus.qt.qtgui.extra_guiqwt.tools import (TaurusModelChooserTool,
+                                                TimeAxisTool, AutoScrollTool)
 
 
 class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
-    '''
+    """
     This is a widget for displaying trends from 1D Taurus attributes (i.e.,
     representing the variation over time of a 1D array). Sometimes this kind of
     plots are also known as "spectrograms".
 
     The widget shows a 3D plot (Z represented with colors) where the values in
     the 1D array are plotted in the Y-Z plane and are stacked along the X axis.
-    '''
+    """
     _modifiableByUser = True
 
     def __init__(self, parent=None, designMode=False, toolbar=True,
                  stackMode='deltatime', buffersize=512, options=None, **kwargs):
-        '''see :class:`guiqwt.plot.ImageDialog` for other valid initialization parameters'''
+        """see :class:`guiqwt.plot.ImageDialog` for other valid initialization
+        parameters"""
         defaultOptions = dict(lock_aspect_ratio=False)
         if options is not None:
             defaultOptions.update(options)
-        ImageDialog.__init__(self, parent=parent,
-                             toolbar=toolbar, options=defaultOptions, **kwargs)
+        ImageDialog.__init__(self, parent=parent, toolbar=toolbar,
+                             options=defaultOptions, **kwargs)
         TaurusBaseWidget.__init__(self, "TaurusTrend2DDialog")
         self.trendItem = None
         self.buffersize = buffersize
@@ -76,7 +78,7 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
             ImageDialog.keyPressEvent(self, event)
 
     def setStackMode(self, mode):
-        '''set the type of stack to be used. This determines how X values are
+        """set the type of stack to be used. This determines how X values are
         interpreted:
 
             - as timestamps ('datetime')
@@ -84,7 +86,7 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
             - as event numbers ('event')
 
         :param mode:(one of 'datetime', 'timedelta' or 'event')
-        '''
+        """
         mode = str(mode)
         if mode == 'datetime':
             self.add_tool(TimeAxisTool)
@@ -113,11 +115,11 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
         self.setStackMode('datetime')
 
     def getModelClass(self):
-        '''reimplemented from :class:`TaurusBaseWidget`'''
+        """reimplemented from :class:`TaurusBaseWidget`"""
         return taurus.core.taurusattribute.TaurusAttribute
 
     def setModel(self, model):
-        '''reimplemented from :class:`TaurusBaseWidget`'''
+        """reimplemented from :class:`TaurusBaseWidget`"""
         plot = self.get_plot()
         if self.trendItem is not None:
             plot.del_item(self.trendItem)
@@ -145,56 +147,57 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
             "dataChanged"), self.update_cross_sections)
 
     def getModel(self):
-        '''reimplemented from :class:`TaurusBaseWidget`'''
+        """reimplemented from :class:`TaurusBaseWidget`"""
         if self.trendItem is None:
             return None
         else:
             return self.trendItem.getModel()
 
     def setUseArchiving(self, enable):
-        '''enables/disables looking up in the archiver for data stored before
+        """enables/disables looking up in the archiver for data stored before
         the Trend was started
 
-        :param enable: (bool) if True, archiving values will be used if available
-        '''
+        :param enable: (bool) if True, archiving values will be used if
+                       available
+        """
         if not self._stackMode == 'datetime':
             self.info('ignoring setUseArchiving. Reason: not in X time scale')
         self._useArchiving = enable
 
     def getUseArchiving(self):
-        '''whether TaurusTrend is looking for data in the archiver when needed
+        """whether TaurusTrend is looking for data in the archiver when needed
 
         :return: (bool)
 
         .. seealso:: :meth:`setUseArchiving`
-        '''
+        """
         return self._useArchiving
 
     def resetUseArchiving(self):
-        '''Same as setUseArchiving(False)'''
+        """Same as setUseArchiving(False)"""
         self.setUseArchiving(False)
 
     def setMaxDataBufferSize(self, maxSize):
-        '''sets the maximum number of events that will be stacked
+        """sets the maximum number of events that will be stacked
 
         :param maxSize: (int) the maximum limit
 
         .. seealso:: :class:`TaurusTrendSet`
-        '''
+        """
         if self.trendItem is not None:
             self.trendItem.setBufferSize(maxSize)
 
         self.buffersize = maxSize
 
     def getMaxDataBufferSize(self):
-        '''returns the maximum number of events that can be plotted in the trend
+        """returns the maximum number of events that can be plotted in the trend
 
         :return: (int)
-        '''
+        """
         return self.buffersize
 
     def resetMaxDataBufferSize(self):
-        '''Same as setMaxDataBufferSize(512)  (i.e. 512 events)'''
+        """Same as setMaxDataBufferSize(512)  (i.e. 512 events)"""
         self.setMaxDataBufferSize(512)
 
     @classmethod
@@ -215,14 +218,17 @@ class TaurusTrend2DDialog(ImageDialog, TaurusBaseWidget):
     model = Qt.pyqtProperty("QString", getModel, setModel,
                             TaurusBaseWidget.resetModel)
     # @todo uncomment this when archiving is supported
-    useArchiving = Qt.pyqtProperty(
-        "bool", getUseArchiving, setUseArchiving, resetUseArchiving)
-    maxDataBufferSize = Qt.pyqtProperty(
-        "int", getMaxDataBufferSize, setMaxDataBufferSize, resetMaxDataBufferSize)
-    stackMode = Qt.pyqtProperty(
-        "QString", getStackMode, setStackMode, resetStackMode)
-    modifiableByUser = Qt.pyqtProperty(
-        "bool", TaurusBaseWidget.isModifiableByUser, setModifiableByUser, TaurusBaseWidget.resetModifiableByUser)
+    useArchiving = Qt.pyqtProperty("bool", getUseArchiving, setUseArchiving,
+                                   resetUseArchiving)
+    maxDataBufferSize = Qt.pyqtProperty("int", getMaxDataBufferSize,
+                                        setMaxDataBufferSize,
+                                        resetMaxDataBufferSize)
+    stackMode = Qt.pyqtProperty("QString", getStackMode, setStackMode,
+                                resetStackMode)
+    modifiableByUser = Qt.pyqtProperty("bool",
+                                       TaurusBaseWidget.isModifiableByUser,
+                                       setModifiableByUser,
+                                       TaurusBaseWidget.resetModifiableByUser)
 
 
 def taurusTrend2DMain():
@@ -233,12 +239,19 @@ def taurusTrend2DMain():
     # prepare options
     parser = taurus.core.util.argparse.get_taurus_parser()
     parser.set_usage("%prog [options] <model>")
-    parser.set_description(
-        'a Taurus application for plotting trends of arrays (aka "spectrograms")')
-    parser.add_option("-x", "--x-axis-mode", dest="x_axis_mode", default='d', metavar="t|d|e",
-                      help="interpret X values as timestamps (t), time deltas (d) or event numbers (e). Accepted values: t|d|e")
+    parser.set_description('a Taurus application for plotting trends of ' +
+                           'arrays (aka "spectrograms")')
+    parser.add_option("-x", "--x-axis-mode", dest="x_axis_mode", default='d',
+                      metavar="t|d|e",
+                      help=("interpret X values as timestamps (t), " +
+                            "time deltas (d) or event numbers (e). " +
+                            "Accepted values: t|d|e")
+                      )
     parser.add_option("-b", "--buffer", dest="max_buffer_size", default='512',
-                      help="maximum number of values to be stacked (when reached, the oldest values will be discarded)")
+                      help=("maximum number of values to be stacked " +
+                            "(when reached, the oldest values will be " +
+                            "discarded)")
+                      )
     parser.add_option("-a", "--use-archiving",
                       action="store_true", dest="use_archiving", default=False)
     parser.add_option("--demo", action="store_true", dest="demo",
@@ -246,8 +259,8 @@ def taurusTrend2DMain():
     parser.add_option("--window-name", dest="window_name",
                       default="Taurus Trend 2D", help="Name of the window")
 
-    app = TaurusApplication(
-        cmd_line_parser=parser, app_name="Taurus Trend 2D", app_version=taurus.Release.version)
+    app = TaurusApplication(cmd_line_parser=parser, app_name="Taurus Trend 2D",
+                            app_version=taurus.Release.version)
     args = app.get_command_line_args()
     options = app.get_command_line_options()
 
diff --git a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
index 5df5554..124f57a 100644
--- a/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
+++ b/lib/taurus/qt/qtgui/extra_guiqwt/tools.py
@@ -30,7 +30,8 @@ __docformat__ = 'restructuredtext'
 
 
 from taurus.external.qt import Qt
-from guiqwt.tools import CommandTool, ToggleTool, DefaultToolbarID, QActionGroup, add_actions
+from guiqwt.tools import (CommandTool, ToggleTool, DefaultToolbarID,
+                          QActionGroup, add_actions)
 from guiqwt.signals import SIG_ITEMS_CHANGED
 
 from taurus.core.taurusbasetypes import TaurusElementType
@@ -45,12 +46,14 @@ from taurus.qt.qtgui.plot import DateTimeScaleEngine
 
 class TaurusCurveChooserTool(CommandTool):
     """
-    A tool that shows the Taurus Model Chooser to create/edit the taurus curves of a plot
+    A tool that shows the Taurus Model Chooser to create/edit the taurus curves
+    of a plot
     """
 
     def __init__(self, manager, toolbar_id=DefaultToolbarID):
         super(TaurusCurveChooserTool, self).__init__(
-            manager, "Taurus Models...", getIcon(":/taurus.png"), toolbar_id=toolbar_id)
+                manager, "Taurus Models...", getIcon(":/taurus.png"),
+                toolbar_id=toolbar_id)
 
     def activate_command(self, plot, checked):
         """Activate tool"""
@@ -65,8 +68,8 @@ class TaurusCurveChooserTool(CommandTool):
             # create curve items and add them to the plot
             for c in confs:
                 if c.taurusparam.yModel:
-                    item = make.pcurve(
-                        c.taurusparam.xModel or None, c.taurusparam.yModel, c.curveparam)
+                    item = make.pcurve(c.taurusparam.xModel or None,
+                                       c.taurusparam.yModel, c.curveparam)
                     plot.add_item(item)
                     if c.axesparam is not None:
                         c.axesparam.update_axes(item)
@@ -74,12 +77,14 @@ class TaurusCurveChooserTool(CommandTool):
 
 class TaurusImageChooserTool(CommandTool):
     """
-    A tool that shows the Taurus Model Chooser and adds new taurus image items to a plot
+    A tool that shows the Taurus Model Chooser and adds new taurus image items
+    to a plot
     """
 
     def __init__(self, manager, toolbar_id=DefaultToolbarID):
         super(TaurusImageChooserTool, self).__init__(
-            manager, "Add Taurus images...", getIcon(":/taurus.png"), toolbar_id=toolbar_id)
+                manager, "Add Taurus images...", getIcon(":/taurus.png"),
+                toolbar_id=toolbar_id)
 
     def activate_command(self, plot, checked):
         """Activate tool"""
@@ -95,19 +100,24 @@ class TaurusImageChooserTool(CommandTool):
 
 class TaurusModelChooserTool(CommandTool):
     """
-    A tool that shows the Taurus Model Chooser and sets the chosen model on the manager
+    A tool that shows the Taurus Model Chooser and sets the chosen model on
+    the manager
     """
 
     def __init__(self, manager, toolbar_id=DefaultToolbarID, singleModel=False):
         super(TaurusModelChooserTool, self).__init__(
-            manager, "Change Taurus Model...", getIcon(":/taurus.png"), toolbar_id=toolbar_id)
+                manager, "Change Taurus Model...", getIcon(":/taurus.png"),
+                toolbar_id=toolbar_id)
         self.singleModel = singleModel
 
     def activate_command(self, plot, checked):
         """Activate tool"""
         # show a dialog
-        models, ok = TaurusModelChooser.modelChooserDlg(parent=plot, selectables=[
-                                                        TaurusElementType.Attribute], singleModel=self.singleModel)
+        models, ok = TaurusModelChooser.modelChooserDlg(
+                parent=plot,
+                selectables=[TaurusElementType.Attribute],
+                singleModel=self.singleModel
+        )
         if ok:
             if self.singleModel:
                 if models:
@@ -124,10 +134,9 @@ class TimeAxisTool(CommandTool):
     """
 
     def __init__(self, manager):
-        super(TimeAxisTool, self).__init__(manager, "Time Scale",
-                                           icon=getIcon(
-                                               ":/status/awaiting.svg"),
-                                           tip=None, toolbar_id=None)
+        super(TimeAxisTool, self).__init__(
+                manager, "Time Scale", icon=getIcon(":/status/awaiting.svg"),
+                tip=None, toolbar_id=None)
         self.action.setEnabled(True)
 
     def create_action_menu(self, manager):
@@ -152,16 +161,17 @@ class TimeAxisTool(CommandTool):
 
     def _getAxesUseTime(self, plot):
         """
-        Returns a tuple (xIsTime, yIsTime) where xIsTime is True if the plot's active x
-        axis uses a TimeScale. yIsTime is True if plot's active y axis uses a Time
+        Returns a tuple (xIsTime, yIsTime) where xIsTime is True if the plot's
+        active x axis uses a TimeScale. yIsTime is True if plot's active y axis
         Scale. Otherwise they are False.
         """
         if plot is None:
-            return (False, False)
+            return False, False
         xaxis, yaxis = plot.get_active_axes()
         xEngine = plot.axisScaleEngine(xaxis)
         yEngine = plot.axisScaleEngine(yaxis)
-        return isinstance(xEngine, DateTimeScaleEngine), isinstance(yEngine, DateTimeScaleEngine)
+        return (isinstance(xEngine, DateTimeScaleEngine),
+                isinstance(yEngine, DateTimeScaleEngine))
 
     def update_status(self, plot):
         active_scale = self._getAxesUseTime(plot)
@@ -209,8 +219,10 @@ class AutoScrollTool(ToggleTool):
     always visible"""
 
     def __init__(self, manager, scrollFactor=0.2, toolbar_id=None):
-        super(AutoScrollTool, self).__init__(manager, title='Auto Scroll', icon=None,
-                                             tip='Force X scale to always show the last value', toolbar_id=toolbar_id)
+        super(AutoScrollTool, self).__init__(
+                manager, title='Auto Scroll', icon=None,
+                tip='Force X scale to always show the last value',
+                toolbar_id=toolbar_id)
         self.scrollFactor = scrollFactor
 
     def register_plot(self, baseplot):
@@ -229,7 +241,8 @@ class AutoScrollTool(ToggleTool):
                     'scrollRequested'), self.onScrollRequested)
 
     def getScrollItems(self, plot):
-        return [item for item in plot.get_items() if isinstance(item, (TaurusTrendItem, TaurusTrend2DItem))]
+        return [item for item in plot.get_items()
+                if isinstance(item, (TaurusTrendItem, TaurusTrend2DItem))]
 
     def onScrollRequested(self, plot, axis, value):
         scalemin, scalemax = plot.get_axis_limits(axis)
@@ -245,7 +258,6 @@ class AutoScrollTool(ToggleTool):
 def testTool(tool):
     from taurus.qt.qtgui.application import TaurusApplication
     from guiqwt.plot import CurveDialog
-    import sys
 
     app = TaurusApplication()
     win = CurveDialog(edit=False, toolbar=True)
-- 
2.8.1

[tauruslib-devel] [PATCH] fix bug-269

[<cpa...@ce...>]

This series of 3 patches fixes bug-269.
[PATCH 1/3] (m, PEP8) Fix long lines
[PATCH 2/3] Fix bug-269: store Autoscroll tool state in config
[PATCH 3/3] Fix scale problem when autoscroll is set before model

The first is a minor, pep8 correction.
The second is the bug fix proper.
The third fixes a bug that was already there but which is now more evident
because standard 2D trends may be initialized with autoscroll=true
(before it only occurred in custom trend widgets)

Re: [tauruslib-devel] Problems with macrogui

[Teresa N. <mar...@de...>]

Hi Zibi,
             we have just now figured out that if I login in one 
computer via ssh
  everything works perfectly and that the problem is not in taurus/sardana
  but in Qt, and it is related with the gnome settings ... We have to 
find the
  right settings for making taurus and also some other qt applications we
  have work properly. Sorry for the e-mails and many thanks.

                              Regards,
                                                Teresa

On 05/03/16 13:22, Zbigniew Reszela wrote:
> Hi Teresa,
>
> Then could you please create a ticket in Sardana indicating the 
> easiest way to reproduce it and the exact environment?
> We will try to rerproduce it at Alba.
>
> Cheers,
> Zibi
>
>
> On 05/03/2016 01:09 PM, Teresa Nunez wrote:
>> Hi Carlos,
>>                   then yes, I have tested it with the last develop version of
>>    Sardana and the problem with the sequencer gui is there, well, in
>>    our computers. Also for the 'Macros' tab in the macrogui.
>>    It was not there with debian 7 or scientific linux.
>>
>>                        Regards,
>>                                             Teresa
>>
>>
>> On 05/03/16 09:31, Carlos Pascual wrote:
>>> On Thu 28 April 2016 15:42:41 Teresa Nunez wrote:
>>>> Hi Carlos,
>>>>                   many thanks for the reply, and don't worry, do not
>>>> reply today, we can wait.
>>>>     At the beamlines we don't have the last version in develop. I have
>>>>     tried to check it with this version in my computer (before writing
>>>>     the e-mail) but I got another problem ... so I could not. But if
>>>>     it is solved I will tell them, and they will have to work with this
>>>> until we can update taurus.
>>> Note that in this case I meant the latest develop version of **sardana**
>>> (now you can just use the 2.0.0 release). The macroexecutor and
>>> sequencer widgets are provided by sardana, not Taurus.
>>>
>>> Our tests for sardana 2.0.0 were done with taurus 3.7.0 (sardana is not
>>> yet compatible with the latest taurus=4.0.0)
>>>
>>>> The second point, I will tell the people to test it in the beamline.
>>>>
>>>>                       Regards,
>>>>                                        Teresa
>>>>
>>>> On 04/28/16 14:55, Carlos Pascual wrote:
>>>>> In a hurry,
>>>>> very quick....
>>>>>
>>>>> On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
>>>>>> Hello,
>>>>>>
>>>>>>                  we have some problems running the macrogui in our
>>>>>>
>>>>>> experiments. The users complains about these two facts and I can
>>>>>> confirm that this is the behaviour we get:
>>>>>>
>>>>>> - when we introduce the values of the parameteres of the selected
>>>>>> macro in the 'Macros'
>>>>>>
>>>>>>      or 'Sequences' tabs, the old value stays always there while we
>>>>>>      right
>>>>>>
>>>>>> the new one (in background,
>>>>>>
>>>>>>      behind the new one that is being typed) only when ones pulse
>>>>>>      enter
>>>>>>
>>>>>> the old value dissapears and only
>>>>>>
>>>>>>      the new one is visible. This happens since we change from debian
>>>>>>      7
>>>>>>
>>>>>> to debian 8
>>>>> What you describe sounds familiar... but I thought it was solved.
>>>>> Does it happen with the latest develop code?
>>>>>
>>>>> We didn't notice it last week while doing release tests on debian8
>>>>> for the coming release....
>>>>>
>>>>>> - the macrogui get slower with time, the users don't know what
>>>>>> produces this. I have seen for
>>>>>>
>>>>>>      example that introducing the parameters of the macros in the
>>>>>>
>>>>>> sequencer can increases the
>>>>>>
>>>>>>      CPU consumption of taurusgui up to 100% and the macrogui gets
>>>>>>      then
>>>>>>
>>>>>> very slow, it recovers
>>>>>>
>>>>>>      when the values are introduced. Have you seen something similar.
>>>>> Check if manually removing the history and favourites (maybe using
>>>>> taurusconfigbrowser) helps.
>>>>>
>>>>>>      Many thanks.
>>>>>>      
>>>>>>                                               Regards,
>>>>>>                                               
>>>>>>                                                           Teresa
>>>>>>
>>>>>> -------------------------------------------------------------------
>>>>>> --- -------- Find and fix application performance issues faster
>>>>>> with Applications Manager Applications Manager provides deep
>>>>>> performance insights into multiple tiers of your business
>>>>>> applications. It resolves application problems quickly and reduces
>>>>>> your MTTR. Get your free trial!
>>>>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>>>> _______________________________________________
>>>>>> Tauruslib-devel mailing list
>>>>>> Tau...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications Manager
>> Applications Manager provides deep performance insights into multiple tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> Tauruslib-devel mailing list
>> Tau...@li...
>> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Controls Section - Computing Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.albasynchrotron.es/AboutUs/Access>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>
>
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

Re: [tauruslib-devel] Problems with macrogui

[Zbigniew R. <zre...@ce...>]

Hi Teresa,

Then could you please create a ticket in Sardana indicating the easiest 
way to reproduce it and the exact environment?
We will try to rerproduce it at Alba.

Cheers,
Zibi


On 05/03/2016 01:09 PM, Teresa Nunez wrote:
> Hi Carlos,
>                   then yes, I have tested it with the last develop version of
>    Sardana and the problem with the sequencer gui is there, well, in
>    our computers. Also for the 'Macros' tab in the macrogui.
>    It was not there with debian 7 or scientific linux.
>
>                        Regards,
>                                             Teresa
>
>
> On 05/03/16 09:31, Carlos Pascual wrote:
>> On Thu 28 April 2016 15:42:41 Teresa Nunez wrote:
>>> Hi Carlos,
>>>                   many thanks for the reply, and don't worry, do not
>>> reply today, we can wait.
>>>     At the beamlines we don't have the last version in develop. I have
>>>     tried to check it with this version in my computer (before writing
>>>     the e-mail) but I got another problem ... so I could not. But if
>>>     it is solved I will tell them, and they will have to work with this
>>> until we can update taurus.
>> Note that in this case I meant the latest develop version of **sardana**
>> (now you can just use the 2.0.0 release). The macroexecutor and
>> sequencer widgets are provided by sardana, not Taurus.
>>
>> Our tests for sardana 2.0.0 were done with taurus 3.7.0 (sardana is not
>> yet compatible with the latest taurus=4.0.0)
>>
>>> The second point, I will tell the people to test it in the beamline.
>>>
>>>                       Regards,
>>>                                        Teresa
>>>
>>> On 04/28/16 14:55, Carlos Pascual wrote:
>>>> In a hurry,
>>>> very quick....
>>>>
>>>> On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
>>>>> Hello,
>>>>>
>>>>>                  we have some problems running the macrogui in our
>>>>>
>>>>> experiments. The users complains about these two facts and I can
>>>>> confirm that this is the behaviour we get:
>>>>>
>>>>> - when we introduce the values of the parameteres of the selected
>>>>> macro in the 'Macros'
>>>>>
>>>>>      or 'Sequences' tabs, the old value stays always there while we
>>>>>      right
>>>>>
>>>>> the new one (in background,
>>>>>
>>>>>      behind the new one that is being typed) only when ones pulse
>>>>>      enter
>>>>>
>>>>> the old value dissapears and only
>>>>>
>>>>>      the new one is visible. This happens since we change from debian
>>>>>      7
>>>>>
>>>>> to debian 8
>>>> What you describe sounds familiar... but I thought it was solved.
>>>> Does it happen with the latest develop code?
>>>>
>>>> We didn't notice it last week while doing release tests on debian8
>>>> for the coming release....
>>>>
>>>>> - the macrogui get slower with time, the users don't know what
>>>>> produces this. I have seen for
>>>>>
>>>>>      example that introducing the parameters of the macros in the
>>>>>
>>>>> sequencer can increases the
>>>>>
>>>>>      CPU consumption of taurusgui up to 100% and the macrogui gets
>>>>>      then
>>>>>
>>>>> very slow, it recovers
>>>>>
>>>>>      when the values are introduced. Have you seen something similar.
>>>> Check if manually removing the history and favourites (maybe using
>>>> taurusconfigbrowser) helps.
>>>>
>>>>>      Many thanks.
>>>>>      
>>>>>                                               Regards,
>>>>>                                               
>>>>>                                                           Teresa
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --- -------- Find and fix application performance issues faster
>>>>> with Applications Manager Applications Manager provides deep
>>>>> performance insights into multiple tiers of your business
>>>>> applications. It resolves application problems quickly and reduces
>>>>> your MTTR. Get your free trial!
>>>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>>> _______________________________________________
>>>>> Tauruslib-devel mailing list
>>>>> Tau...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.albasynchrotron.es/AboutUs/Access>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

Re: [tauruslib-devel] Problems with macrogui

[Teresa N. <mar...@de...>]

Hi Carlos,
                 then yes, I have tested it with the last develop version of
  Sardana and the problem with the sequencer gui is there, well, in
  our computers. Also for the 'Macros' tab in the macrogui.
  It was not there with debian 7 or scientific linux.

                      Regards,
                                           Teresa


On 05/03/16 09:31, Carlos Pascual wrote:
> On Thu 28 April 2016 15:42:41 Teresa Nunez wrote:
>> Hi Carlos,
>>                  many thanks for the reply, and don't worry, do not
>> reply today, we can wait.
>>    At the beamlines we don't have the last version in develop. I have
>>    tried to check it with this version in my computer (before writing
>>    the e-mail) but I got another problem ... so I could not. But if
>>    it is solved I will tell them, and they will have to work with this
>> until we can update taurus.
> Note that in this case I meant the latest develop version of **sardana**
> (now you can just use the 2.0.0 release). The macroexecutor and
> sequencer widgets are provided by sardana, not Taurus.
>
> Our tests for sardana 2.0.0 were done with taurus 3.7.0 (sardana is not
> yet compatible with the latest taurus=4.0.0)
>
>> The second point, I will tell the people to test it in the beamline.
>>
>>                      Regards,
>>                                       Teresa
>>
>> On 04/28/16 14:55, Carlos Pascual wrote:
>>> In a hurry,
>>> very quick....
>>>
>>> On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
>>>> Hello,
>>>>
>>>>                 we have some problems running the macrogui in our
>>>>
>>>> experiments. The users complains about these two facts and I can
>>>> confirm that this is the behaviour we get:
>>>>
>>>> - when we introduce the values of the parameteres of the selected
>>>> macro in the 'Macros'
>>>>
>>>>     or 'Sequences' tabs, the old value stays always there while we
>>>>     right
>>>>
>>>> the new one (in background,
>>>>
>>>>     behind the new one that is being typed) only when ones pulse
>>>>     enter
>>>>
>>>> the old value dissapears and only
>>>>
>>>>     the new one is visible. This happens since we change from debian
>>>>     7
>>>>
>>>> to debian 8
>>> What you describe sounds familiar... but I thought it was solved.
>>> Does it happen with the latest develop code?
>>>
>>> We didn't notice it last week while doing release tests on debian8
>>> for the coming release....
>>>
>>>> - the macrogui get slower with time, the users don't know what
>>>> produces this. I have seen for
>>>>
>>>>     example that introducing the parameters of the macros in the
>>>>
>>>> sequencer can increases the
>>>>
>>>>     CPU consumption of taurusgui up to 100% and the macrogui gets
>>>>     then
>>>>
>>>> very slow, it recovers
>>>>
>>>>     when the values are introduced. Have you seen something similar.
>>> Check if manually removing the history and favourites (maybe using
>>> taurusconfigbrowser) helps.
>>>
>>>>     Many thanks.
>>>>     
>>>>                                              Regards,
>>>>                                              
>>>>                                                          Teresa
>>>>
>>>> -------------------------------------------------------------------
>>>> --- -------- Find and fix application performance issues faster
>>>> with Applications Manager Applications Manager provides deep
>>>> performance insights into multiple tiers of your business
>>>> applications. It resolves application problems quickly and reduces
>>>> your MTTR. Get your free trial!
>>>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>>> _______________________________________________
>>>> Tauruslib-devel mailing list
>>>> Tau...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

Re: [tauruslib-devel] Problems with macrogui

[Carlos P. <cpa...@ce...>]

On Thu 28 April 2016 15:42:41 Teresa Nunez wrote:
> Hi Carlos,
>                 many thanks for the reply, and don't worry, do not
> reply today, we can wait.
>   At the beamlines we don't have the last version in develop. I have
>   tried to check it with this version in my computer (before writing
>   the e-mail) but I got another problem ... so I could not. But if
>   it is solved I will tell them, and they will have to work with this
> until we can update taurus.

Note that in this case I meant the latest develop version of **sardana** 
(now you can just use the 2.0.0 release). The macroexecutor and 
sequencer widgets are provided by sardana, not Taurus.

Our tests for sardana 2.0.0 were done with taurus 3.7.0 (sardana is not 
yet compatible with the latest taurus=4.0.0)

> The second point, I will tell the people to test it in the beamline.
> 
>                     Regards,
>                                      Teresa
> 
> On 04/28/16 14:55, Carlos Pascual wrote:
> > In a hurry,
> > very quick....
> > 
> > On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
> >> Hello,
> >> 
> >>                we have some problems running the macrogui in our
> >> 
> >> experiments. The users complains about these two facts and I can
> >> confirm that this is the behaviour we get:
> >> 
> >> - when we introduce the values of the parameteres of the selected
> >> macro in the 'Macros'
> >> 
> >>    or 'Sequences' tabs, the old value stays always there while we
> >>    right
> >> 
> >> the new one (in background,
> >> 
> >>    behind the new one that is being typed) only when ones pulse
> >>    enter
> >> 
> >> the old value dissapears and only
> >> 
> >>    the new one is visible. This happens since we change from debian
> >>    7
> >> 
> >> to debian 8
> > 
> > What you describe sounds familiar... but I thought it was solved.
> > Does it happen with the latest develop code?
> > 
> > We didn't notice it last week while doing release tests on debian8
> > for the coming release....
> > 
> >> - the macrogui get slower with time, the users don't know what
> >> produces this. I have seen for
> >> 
> >>    example that introducing the parameters of the macros in the
> >> 
> >> sequencer can increases the
> >> 
> >>    CPU consumption of taurusgui up to 100% and the macrogui gets
> >>    then
> >> 
> >> very slow, it recovers
> >> 
> >>    when the values are introduced. Have you seen something similar.
> > 
> > Check if manually removing the history and favourites (maybe using
> > taurusconfigbrowser) helps.
> > 
> >>    Many thanks.
> >>    
> >>                                             Regards,
> >>                                             
> >>                                                         Teresa
> >> 
> >> -------------------------------------------------------------------
> >> --- -------- Find and fix application performance issues faster
> >> with Applications Manager Applications Manager provides deep
> >> performance insights into multiple tiers of your business
> >> applications. It resolves application problems quickly and reduces
> >> your MTTR. Get your free trial!
> >> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> >> _______________________________________________
> >> Tauruslib-devel mailing list
> >> Tau...@li...
> >> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] Problems with macrogui

[Teresa N. <mar...@de...>]

Hi Carlos,
                many thanks for the reply, and don't worry, do not reply
  today, we can wait.
  At the beamlines we don't have the last version in develop. I have
  tried to check it with this version in my computer (before writing
  the e-mail) but I got another problem ... so I could not. But if
  it is solved I will tell them, and they will have to work with this until
  we can update taurus.
The second point, I will tell the people to test it in the beamline.

                    Regards,
                                     Teresa

On 04/28/16 14:55, Carlos Pascual wrote:
> In a hurry,
> very quick....
>
>
> On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
>> Hello,
>>                we have some problems running the macrogui in our
>> experiments. The users complains about these two facts and I can
>> confirm that this is the behaviour we get:
>>
>> - when we introduce the values of the parameteres of the selected
>> macro in the 'Macros'
>>    or 'Sequences' tabs, the old value stays always there while we right
>> the new one (in background,
>>    behind the new one that is being typed) only when ones pulse enter
>> the old value dissapears and only
>>    the new one is visible. This happens since we change from debian 7
>> to debian 8
>>
> What you describe sounds familiar... but I thought it was solved. Does
> it happen with the latest develop code?
>
> We didn't notice it last week while doing release tests on debian8 for
> the coming release....
>
>
>> - the macrogui get slower with time, the users don't know what
>> produces this. I have seen for
>>    example that introducing the parameters of the macros in the
>> sequencer can increases the
>>    CPU consumption of taurusgui up to 100% and the macrogui gets then
>> very slow, it recovers
>>    when the values are introduced. Have you seen something similar.
> Check if manually removing the history and favourites (maybe using
> taurusconfigbrowser) helps.
>
>>    Many thanks.
>>
>>                                             Regards,
>>                                                         Teresa
>>
>>
>> ----------------------------------------------------------------------
>> -------- Find and fix application performance issues faster with
>> Applications Manager Applications Manager provides deep performance
>> insights into multiple tiers of your business applications. It
>> resolves application problems quickly and reduces your MTTR. Get your
>> free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>> _______________________________________________
>> Tauruslib-devel mailing list
>> Tau...@li...
>> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

Re: [tauruslib-devel] Problems with macrogui

[Carlos P. <cpa...@ce...>]

In a hurry, 
very quick....


On Thu 28 April 2016 11:49:19 Teresa Nunez wrote:
> Hello,
>               we have some problems running the macrogui in our
> experiments. The users complains about these two facts and I can
> confirm that this is the behaviour we get:
> 
> - when we introduce the values of the parameteres of the selected
> macro in the 'Macros'
>   or 'Sequences' tabs, the old value stays always there while we right
> the new one (in background,
>   behind the new one that is being typed) only when ones pulse enter
> the old value dissapears and only
>   the new one is visible. This happens since we change from debian 7
> to debian 8
> 
What you describe sounds familiar... but I thought it was solved. Does 
it happen with the latest develop code?

We didn't notice it last week while doing release tests on debian8 for 
the coming release....


> - the macrogui get slower with time, the users don't know what
> produces this. I have seen for
>   example that introducing the parameters of the macros in the
> sequencer can increases the
>   CPU consumption of taurusgui up to 100% and the macrogui gets then
> very slow, it recovers
>   when the values are introduced. Have you seen something similar.

Check if manually removing the history and favourites (maybe using 
taurusconfigbrowser) helps. 

> 
>   Many thanks.
> 
>                                            Regards,
>                                                        Teresa
> 
> 
> ----------------------------------------------------------------------
> -------- Find and fix application performance issues faster with
> Applications Manager Applications Manager provides deep performance
> insights into multiple tiers of your business applications. It
> resolves application problems quickly and reduces your MTTR. Get your
> free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] Problems with macrogui

[Teresa N. <mar...@de...>]

Hello,
              we have some problems running the macrogui in our experiments.
The users complains about these two facts and I can confirm that this
is the behaviour we get:

- when we introduce the values of the parameteres of the selected macro 
in the 'Macros'
  or 'Sequences' tabs, the old value stays always there while we right 
the new one (in background,
  behind the new one that is being typed) only when ones pulse enter the 
old value dissapears and only
  the new one is visible. This happens since we change from debian 7 to 
debian 8

- the macrogui get slower with time, the users don't know what produces 
this. I have seen for
  example that introducing the parameters of the macros in the sequencer 
can increases the
  CPU consumption of taurusgui up to 100% and the macrogui gets then 
very slow, it recovers
  when the values are introduced. Have you seen something similar.

  Many thanks.

                                           Regards,
                                                       Teresa

[tauruslib-devel] [PATCH] Avoid frozen values during a TaurusEventType.error

[cfalcon <cf...@ce...>]

Set  the last_value to None in TaurusBaseController.handleEvent
method if during an error its value could not be read from the modelObj.
---
 lib/taurus/qt/qtgui/base/tauruscontroller.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/taurus/qt/qtgui/base/tauruscontroller.py b/lib/taurus/qt/qtgui/base/tauruscontroller.py
index 8a86d88..e7bcff6 100644
--- a/lib/taurus/qt/qtgui/base/tauruscontroller.py
+++ b/lib/taurus/qt/qtgui/base/tauruscontroller.py
@@ -108,7 +108,7 @@ class TaurusBaseController(object):
                 try:
                     self._last_value = self.modelObj().getValueObj()
                 except:
-                    pass
+                    self._last_value = None
         self.update()
 
     def eventReceived(self, evt_src, evt_type, evt_value):
-- 
2.4.0

[tauruslib-devel] SEP0 and TEP0 Voting for CANDITATE-->ACCEPTED

[Carlos P. <cpa...@ce...>]

Hi all,

You may not remember it, but our "foundational" enhancement proposals 
for sardana [1] and taurus [2] were left in "CANDIDATE" state in order 
to test them in practice [3].

I think the time has come to formally declare them as ACCEPTED since 
many enhancement proposals have been ACCEPTED following the workflow from 
SEP0 and TEP0


So this is a call for official voting. The representatives from the 
various labs, please reply to this email with your answer to:

- should TEP0 be ACCEPTED"?
- should SEP0 be "ACCEPTED"?

Cheers,


Links:
[1] http://sf.net/p/sardana/wiki/SEP0/
[2] http://sf.net/p/tauruslib/wiki/TEP0/
[3] http://sf.net/p/sardana/mailman/message/31310881/

Carlos
-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] [PATCH] Enables custom split character for pipelined codecs

[<ja...@ce...>]

From: Jordi Andreu <ja...@ce...>

The character used as separator to generate the format names of pipelined
codecs now can be customized. The new split caracter can be set by
using the tauruscustomsettings module. The harcoded "_" character has been
taken as the default value. Feature related to ticket #276.
---
 lib/taurus/core/util/codecs.py     | 41 ++++++++++++++++++++------------------
 lib/taurus/tauruscustomsettings.py |  4 ++++
 2 files changed, 26 insertions(+), 19 deletions(-)

diff --git a/lib/taurus/core/util/codecs.py b/lib/taurus/core/util/codecs.py
index 0fde2e0..9dceb1b 100644
--- a/lib/taurus/core/util/codecs.py
+++ b/lib/taurus/core/util/codecs.py
@@ -78,6 +78,9 @@ from singleton import Singleton
 from log import Logger
 from containers import CaselessDict
 
+import taurus.tauruscustomsettings as tcs
+SEP = getattr(tcs, 'CODEC_PIPELINE_SEP', '_')
+
 
 class Codec(Logger):
     """The base class for all codecs"""
@@ -127,7 +130,7 @@ class NullCodec(Codec):
         :return: (sequence[str, obj]) a sequence of two elements where the first item is the encoding format of the second item object"""
         format = 'null'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         return format, data[1]
 
     def decode(self, data, *args, **kwargs):
@@ -138,7 +141,7 @@ class NullCodec(Codec):
         :return: (sequence[str, obj]) a sequence of two elements where the first item is the encoding format of the second item object"""
         if not data[0].startswith('null'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
         return format, data[1]
 
 
@@ -169,7 +172,7 @@ class ZIPCodec(Codec):
         import zlib
         format = 'zip'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         return format, zlib.compress(data[1])
 
     def decode(self, data, *args, **kwargs):
@@ -181,7 +184,7 @@ class ZIPCodec(Codec):
         import zlib
         if not data[0].startswith('zip'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
         return format, zlib.decompress(data[1])
 
 
@@ -212,7 +215,7 @@ class BZ2Codec(Codec):
         import bz2
         format = 'bz2'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         return format, bz2.compress(data[1])
 
     def decode(self, data, *args, **kwargs):
@@ -224,7 +227,7 @@ class BZ2Codec(Codec):
         import bz2
         if not data[0].startswith('bz2'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
         return format, bz2.decompress(data[1])
 
 
@@ -260,7 +263,7 @@ class PickleCodec(Codec):
         import pickle
         format = 'pickle'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         # make it compact by default
         kwargs['protocol'] = kwargs.get('protocol', pickle.HIGHEST_PROTOCOL)
         return format, pickle.dumps(data[1], *args, **kwargs)
@@ -276,7 +279,7 @@ class PickleCodec(Codec):
         import pickle
         if not data[0].startswith('pickle'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
 
         if isinstance(data[1], buffer):
             data = data[0], str(data[1])
@@ -318,7 +321,7 @@ class JSONCodec(Codec):
         import json
         format = 'json'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         # make it compact by default
         kwargs['separators'] = kwargs.get('separators', (',', ':'))
         return format, json.dumps(data[1], *args, **kwargs)
@@ -334,7 +337,7 @@ class JSONCodec(Codec):
         import json
         if not data[0].startswith('json'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
 
         ensure_ascii = kwargs.pop('ensure_ascii', False)
 
@@ -400,7 +403,7 @@ class BSONCodec(Codec):
         import bson
         format = 'bson'
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         return format, bson.BSON.encode(data[1], *args, **kwargs)
 
     def decode(self, data, *args, **kwargs):
@@ -414,7 +417,7 @@ class BSONCodec(Codec):
         import bson
         if not data[0].startswith('bson'):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
         ensure_ascii = kwargs.pop('ensure_ascii', False)
 
         data = data[0], bson.BSON(data[1])
@@ -456,13 +459,13 @@ class FunctionCodec(Codec):
     def encode(self, data, *args, **kwargs):
         format = self._func_name
         if len(data[0]):
-            format += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         return format, {'type': self._func_name, 'data': data[1]}
 
     def decode(self, data, *args, **kwargs):
         if not data[0].startswith(self._func_name):
             return data
-        format = data[0].partition('_')[2]
+        format = data[0].partition(SEP)[2]
         return format, data[1]
 
 
@@ -510,7 +513,7 @@ class VideoImageCodec(Codec):
 
         fmt = 'videoimage'
         if len(data[0]):
-            fmt += '_%s' % data[0]
+            format += '%s%s' % (SEP, data[0])
         # imgMode depends on numpy.array dtype
         imgMode = self.__getModeId(str(data[1].dtype))
         # frameNumber, unknown then -1
@@ -530,9 +533,9 @@ class VideoImageCodec(Codec):
             self.warning(('"VIDEO_IMAGE" format name is deprecated.' +
                           'Use "videoimage" instead'))
             fixedformat = data[0].replace('VIDEO_IMAGE', 'videoimage')
-            _, _, fmt = fixedformat.partition('_')
+            _, _, fmt = fixedformat.partition(SEP)
         elif data[0].startswith('videoimage'):
-            _, _, fmt = data[0].partition('_')
+            _, _, fmt = data[0].partition(SEP)
         else:
             return data
         header = self.__unpackHeader(
@@ -748,7 +751,7 @@ class VideoImageCodec(Codec):
 class CodecPipeline(Codec, list):
     """The codec class used when encoding/decoding data with multiple encoders
 
-    Example usage::
+    Example usage (assuming "_" as separator SEP)::
 
         >>> from taurus.core.util.codecs import CodecPipeline
 
@@ -771,7 +774,7 @@ class CodecPipeline(Codec, list):
         list.__init__(self)
 
         f = CodecFactory()
-        for i in format.split('_'):
+        for i in format.split(SEP):
             codec = f.getCodec(i)
             self.debug("Appending %s => %s" % (i, codec))
             if codec is None:
diff --git a/lib/taurus/tauruscustomsettings.py b/lib/taurus/tauruscustomsettings.py
index 1835a20..3730a0e 100755
--- a/lib/taurus/tauruscustomsettings.py
+++ b/lib/taurus/tauruscustomsettings.py
@@ -76,6 +76,10 @@ DEFAULT_SCHEME = "tango"
 
 PLY_OPTIMIZE = 1
 
+# Setup the default split character used to separate the encoding names when
+# using pipeline encoding.
+CODEC_PIPELINE_SEP = '_'
+
 # ----------------------------------------------------------------------------
 # Taurus namespace
 # ----------------------------------------------------------------------------
-- 
2.1.4

[tauruslib-devel] [PATCH] Remove warning stream related to LIMA DevEncoded header keyword

[<ja...@ce...>]

From: Jordi Andreu <ja...@ce...>

Remove a warning stream related to the usage of the VIDEO_IMAGE
keyword instead of videoimage. Since VIDEO_IMAGE is imposed by
LimaCCDs DS from ESRF the depretaed notice is no longer valid.
We still tranlating the header keyword for taurus.
---
 lib/taurus/core/util/codecs.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/taurus/core/util/codecs.py b/lib/taurus/core/util/codecs.py
index 0fde2e0..755b1f8 100644
--- a/lib/taurus/core/util/codecs.py
+++ b/lib/taurus/core/util/codecs.py
@@ -527,8 +527,8 @@ class VideoImageCodec(Codec):
         :return: (sequence[str, obj]) a sequence of two elements where the first item is the encoding format of the second item object"""
 
         if data[0].startswith('VIDEO_IMAGE'):
-            self.warning(('"VIDEO_IMAGE" format name is deprecated.' +
-                          'Use "videoimage" instead'))
+#            self.warning(('"VIDEO_IMAGE" format name is deprecated.' +
+#                          'Use "videoimage" instead'))
             fixedformat = data[0].replace('VIDEO_IMAGE', 'videoimage')
             _, _, fmt = fixedformat.partition('_')
         elif data[0].startswith('videoimage'):
-- 
2.1.4

Re: [tauruslib-devel] TEP14 - Voting for CANDIDATE-->ACCEPTED (and TEP3 too!)

[Carlos P. <cpa...@ce...>]

...and ALBA votes Yes too (what a surprise!)

so I'll be passing TEP3 and TEP14 to ACCEPTED
and merging taurus4-preview into develop today

Cheers!


On Mon 14 March 2016 09:30:09 Antonio Milan Otero wrote:
> Hi everyone,
> 
> Add one more YES from Max IV
> 
> Regards,
> [cid:29447730-912D-48D6-B1E6-3D48DC89ACF9]
> 
> 
> Antonio Milán Otero
> Control Software Engineer
> 
> MAX IV Laboratory
> Lund University
> P.O. Box 118, SE-221 00 Lund, Sweden
> Visiting address: Fotongatan 2, 225 94 Lund
> Mobile: +46 72 712 45 90
> www.maxiv.se<http://www.maxiv.se/>
> 
> From: Lukasz Zytniak
> <luk...@uj...<mailto:luk...@uj...>>
 Date:
> Monday, March 14, 2016 at 10:06 AM
> To: Carlos Pascual <cpa...@ce...<mailto:cpa...@ce...>>,
> "tau...@li...<mailto:tauruslib-devel@lists.s
> ourceforge.net>"
> <tau...@li...<mailto:tauruslib-devel@lists.s
> ourceforge.net>>
 Subject: Re: [tauruslib-devel] TEP14 - Voting for
> CANDIDATE-->ACCEPTED (and TEP3 too!) 
> Hi Carlos,
> 
> Thanks for your great work.
> Solaris vote for yes.
> 
> Kind regards,
> Lukasz
> 
> 
> W dniu 2016-03-11 o 15:48, Carlos Pascual pisze:
> 
> Hi all,
> 
> Even if I just passed TEP14 from DRAFT to CANDIDATE, the proposed
> implementation was already published and open for inspection 3 months
> ago, and some institutes have already done their tests, so I think
> that we may directly go for the TEP14 acceptance voting.
> 
> Also, please note that accepting TEP14 implies first accepting TEP3.
> The
 vote for TEP3 acceptance was called months ago, but only Desy
> voted. 
> So please vote now for both TEP3 and TEP14, and If accepted I will
> proceed with merging the taurus4-preview branch into develop next
> week
 (and the new era of Taurus4 will begin!).
> 
> Cheers
> 
> Carlos
> 
> [1] https://sf.net/p/tauruslib/taurus-devel/message/34095067
> 
> 
> 
> --
> Kind Regards,
> Lukasz Zytniak
> 
> Control Software Engineer
> ---------------------------------------------------------------
> Synchrotron Radiation Centre "Solaris"
> Jagiellonian University
> 98 Czerwone Maki Street; 30-392 Krakow
> mobile: +48 519 307 972
> www.synchrotron.pl<http://www.synchrotron.pl>

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] TEP14 - Voting for CANDIDATE-->ACCEPTED (and TEP3 too!)

[Antonio M. O. <ant...@ma...>]

Hi everyone,

Add one more YES from Max IV

Regards,
[cid:29447730-912D-48D6-B1E6-3D48DC89ACF9]


Antonio Milán Otero
Control Software Engineer

MAX IV Laboratory
Lund University
P.O. Box 118, SE-221 00 Lund, Sweden
Visiting address: Fotongatan 2, 225 94 Lund
Mobile: +46 72 712 45 90
www.maxiv.se<http://www.maxiv.se/>

From: Lukasz Zytniak <luk...@uj...<mailto:luk...@uj...>>
Date: Monday, March 14, 2016 at 10:06 AM
To: Carlos Pascual <cpa...@ce...<mailto:cpa...@ce...>>, "tau...@li...<mailto:tau...@li...>" <tau...@li...<mailto:tau...@li...>>
Subject: Re: [tauruslib-devel] TEP14 - Voting for CANDIDATE-->ACCEPTED (and TEP3 too!)

Hi Carlos,

Thanks for your great work.
Solaris vote for yes.

Kind regards,
Lukasz


W dniu 2016-03-11 o 15:48, Carlos Pascual pisze:

Hi all,

Even if I just passed TEP14 from DRAFT to CANDIDATE, the proposed
implementation was already published and open for inspection 3 months
ago, and some institutes have already done their tests, so I think that
we may directly go for the TEP14 acceptance voting.

Also, please note that accepting TEP14 implies first accepting TEP3. The
vote for TEP3 acceptance was called months ago, but only Desy voted.

So please vote now for both TEP3 and TEP14, and If accepted I will
proceed with merging the taurus4-preview branch into develop next week
(and the new era of Taurus4 will begin!).

Cheers

Carlos

[1] https://sf.net/p/tauruslib/taurus-devel/message/34095067



--
Kind Regards,
Lukasz Zytniak

Control Software Engineer
---------------------------------------------------------------
Synchrotron Radiation Centre "Solaris"
Jagiellonian University
98 Czerwone Maki Street; 30-392 Krakow
mobile: +48 519 307 972
www.synchrotron.pl<http://www.synchrotron.pl>