Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status widget moved away #71

Closed
guenp opened this issue Apr 14, 2016 · 12 comments
Closed

Status widget moved away #71

guenp opened this issue Apr 14, 2016 · 12 comments

Comments

@guenp
Copy link
Contributor

guenp commented Apr 14, 2016

Sorry, I accidentally posted with Guens account, @MerlinSmiles is the author!

Not really sure how i did this, but i detached the status area, moved it about, and now I cannot move it anymore because the titlebar is behind the browser frame 😇 The only thing I can do is save the notebook 😂

image

@MerlinSmiles
Copy link
Contributor

Sorry, this was my post above 😇

@guenp
Copy link
Contributor Author

guenp commented Apr 14, 2016

@MerlinSmiles Haha no worries 😅 I should not forget to log out

@MerlinSmiles
Copy link
Contributor

@alexcjohnson actually it would be really nice if this widget could be resized, which is the reason that I detached it in the first place, when all those negative delays were flooding the screen...

@guenp
Copy link
Contributor Author

guenp commented Apr 14, 2016

Or maybe a clear button?

@MerlinSmiles
Copy link
Contributor

@guenp That one exists, but the Negative Delay QCoDeS/Qcodes_loop#13 issue floods the screen again right away as the measurement is running. Which also pops up the widget again when it minimized.

@guenp
Copy link
Contributor Author

guenp commented Apr 14, 2016

@MerlinSmiles ok I see - perhaps we should look into ignoring/suppressing repeated errors in the status widget, error flooding is something that will definitely come up more frequently in loops and such

@alexcjohnson
Copy link
Contributor

@MerlinSmiles I never could reproduce this, does it still behave that way for you? For me the whole widget is draggable, not just the title bar, so I can't get it stuck by hiding the title bar. I can drag it so far away that it disappears entirely, which doesn't seem very useful! So I'll look into fixing that.

Anyway with #237 the widget will no longer reopen automatically, so this whole issue should be less important.

@MerlinSmiles
Copy link
Contributor

Haven't looked at #237 , but this is very easy to reproduce.

  • Detach the widget from the corner so that it is floating
  • Move the widget away so that you cannot see it in the browser window anymore (Dont maximize your window)
  • Release the mouse

You cant move it back again now 😄

OSX and Windows, Chrome and Firefox.

@alexcjohnson
Copy link
Contributor

Ah OK, that's the behavior I was describing with:

I can drag it so far away that it disappears entirely, which doesn't seem very useful!

From your original description it sounded like you could still see everything except the title bar, so it was covering up much of the notebook and you couldn't do anything about that. That would be much worse, so do let me know if you ever see that again. But I'll figure out the disappearing trick anyway.

@MerlinSmiles
Copy link
Contributor

That is just as easy, just drag it to the top of your window so that the titlebar is below the tab-bar of your browser, if the widget is big enought it will block all notebook buttons ^^

its the same problem though.

I was thinking, is it possible to make this whole thing a notebook extension ?

@MerlinSmiles
Copy link
Contributor

Oh now I see that I can drag it from the yellow region :headbang: must have hit text before so yes, possible to drag it away from the buttons again...

@alexcjohnson
Copy link
Contributor

Closed by #237

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants