<rjo>
cr1901_modern: what do you hope to gain from that other than confirming what i said earlier?
FabM has quit [Ping timeout: 248 seconds]
FabM has joined #m-labs
<sb0>
hm, programming a DDS is slow
<sb0>
122us...
FabM has quit [Quit: ChatZilla 0.9.92 [Iceweasel 38.7.0/20160308234001]]
<rjo>
sb0: yes.
<sb0>
whitequark, the compiler doesn't call at all the __exit__ of context managers on exception
<sb0>
is that intended?
FabM has joined #m-labs
<sb0>
at any rate, this screws up dds_batch when there is an underflow
key2 has joined #m-labs
<sb0>
ah well. it calls them unreliably. fun...
<sb0>
"The main reasons for changing from VMEbus to MicroTCA are that MicroTCA has implemented an extensive remote management that detects all possible faults on plug-in boards, in the power supply systems and in the ventilation system."
<sb0>
it's magic!
<cr1901_modern>
rjo: I want to confirm whether the order of events (widget being shown and parameters manually being set) are deterministic (i.e. not set by two separate coroutines).
<cr1901_modern>
rjo: Now that I think about it, you implied that order of events is not deterministic with your original explanation. So I might need to set sane default parameters since I don't know when they will become valid (Exception: If parameters are loaded from artiq.pyon, they will become valid before the widget is shown/resize).
ylamarre has joined #m-labs
<rjo>
cr1901_modern: i rewrote the eentire scanwidget.
<cr1901_modern>
rjo: Looks good
<rjo>
could you size the drawable area/geometry of the widget so that all the axis items are visible?
<cr1901_modern>
ok
ylamarre has quit [Quit: ylamarre]
<cr1901_modern>
rjo: Done
<sb0>
hm the sliders have mostly disappeared (with hidpi at least)
<sb0>
they're something like 1px high
FabM has quit [Remote host closed the connection]
<cr1901_modern>
sb0: Can you take a pic (I don't have a hidpi display)?