Prev/Next Channel gives traceback when encountering workspace
See original GitHub issueWorkflow to reproduce this (either in Ginga 2.6.5 or dev):
- Start Ginga.
- Create a workspace.
- Press left or right arrow to cycle between channels. The workspace would still be in focus but I see the following traceback on the terminal.
Error making callback 'activated': 'ws1'
Traceback:
File ".../ginga/misc/Callback.py", line 123, in make_callback
res = method(*cb_args, **cb_kwdargs)
File ".../ginga/rv/plugins/Toolbar.py", line 79, in <lambda>
lambda w: self.fv.next_channel()),
File ".../ginga/rv/Control.py", line 793, in next_channel
self.next_channel_ws(ws)
File ".../ginga/rv/Control.py", line 785, in next_channel_ws
self.change_channel(chname, raisew=True)
File ".../ginga/rv/Control.py", line 958, in change_channel
channel = self.get_channel(name)
File ".../ginga/rv/Control.py", line 1003, in get_channel
return self.channel[name]
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Performing a Combination — pyhf Tutorial
To do so, we'll use a simple workspace to demonstrate functionality of combinations. import json import pyhf. with open("data/2-bin_1-channel.json") as ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry, please wait a little until I add a couple more commits!
Have to qualify this somewhat: when a workspace is added as a subworkspace, and the upper workspace is shown in “grid” mode, there appears to be a bug in how that is displayed. I’ll raise this as a separate issue.