<GitHub135>
[artiq] sbourdeauducq commented on issue #760: We could dodge this problem by using a tabbed view instead of multiple sub-windows for the experiments. But then you would only be able to display one experiment at a time in the main window (and switch between the open ones using the tab bar). As far as I know, it is desirable to support displaying multiple experiments side-by-side. Is this still true? https://github.com/m-labs/artiq/issues/760#
<GitHub191>
[artiq] sbourdeauducq commented on issue #760: We could dodge this problem by using a tabbed view instead of multiple sub-windows for the experiments. But then you would only be able to display one experiment at a time in the main window (and switch between the open ones using the tab bar). As another advantage, the GUI becomes easier to use on small monitors. But as far as I know, it is desirable to support displaying multiple experiments side-b
sb0 has quit [Quit: Leaving]
mumptai has quit [Remote host closed the connection]
sb0 has joined #m-labs
<GitHub188>
[artiq] jordens commented on issue #807: That property holds for all orders. Once the interpolators start wrapping really fast then there will be aliasing but that's generally present in visible in other circumstances as well.... https://github.com/m-labs/artiq/issues/807#issuecomment-319322743
<key2>
rjo: when you say "passing through attributes of mem element" you mean it's already implemented or has to be done ?
<key2>
when using Memory() do I have to go through the get_port() ? or can I directly read/write into it from migen without the we/re... signals
<GitHub76>
[artiq] jbqubit commented on issue #767: The current practice for the ARTIQ community is to use github Issues for bug reporting and discussing new futures. Please use the ARTIQ mailing list for general Q&A. ... https://github.com/m-labs/artiq/issues/767#issuecomment-319448048