Clipboard History appears on application start #691

Closed
piersb opened this Issue Feb 8, 2012 · 11 comments

Comments

Projects
None yet
4 participants
@piersb

piersb commented Feb 8, 2012

Since the recent auto-update to B64 3915, the Clipboard History window now appears every time the application is started. There doesn't appear to be a setting in Preferences to stop this happening, and an Internet search says it's a bug - but I can't find a bugreport here.

So I'm creating one.

@pjrobertson

This comment has been minimized.

Show comment Hide comment
@pjrobertson

pjrobertson Feb 8, 2012

Owner

Do you have your clipboard docked to the side of a window, or is it
'floating' on the screen?
When you quit Quicksilver, is the clipboard open or closed?

Also, could you let me know which version of the Clipboard module you are
using (See the Plugins preference pane). You should be on v1.1.1

Thanks

On 8 February 2012 10:17, piersb <
reply@reply.github.com

wrote:

Since the recent auto-update to B64 3915, the Clipboard History window now
appears every time the application is started. There doesn't appear to be a
setting in Preferences to stop this happening, and an Internet search says
it's a bug - but I can't find a bugreport here.

So I'm creating one.


Reply to this email directly or view it on GitHub:
#691

Owner

pjrobertson commented Feb 8, 2012

Do you have your clipboard docked to the side of a window, or is it
'floating' on the screen?
When you quit Quicksilver, is the clipboard open or closed?

Also, could you let me know which version of the Clipboard module you are
using (See the Plugins preference pane). You should be on v1.1.1

Thanks

On 8 February 2012 10:17, piersb <
reply@reply.github.com

wrote:

Since the recent auto-update to B64 3915, the Clipboard History window now
appears every time the application is started. There doesn't appear to be a
setting in Preferences to stop this happening, and an Internet search says
it's a bug - but I can't find a bugreport here.

So I'm creating one.


Reply to this email directly or view it on GitHub:
#691

@piersb

This comment has been minimized.

Show comment Hide comment
@piersb

piersb Feb 8, 2012

It appears in the middle of the screen when the app starts, then closes. It's closed when I quit Quicksilver, and the plugin is v 1.1.1.

piersb commented Feb 8, 2012

It appears in the middle of the screen when the app starts, then closes. It's closed when I quit Quicksilver, and the plugin is v 1.1.1.

@pjrobertson

This comment has been minimized.

Show comment Hide comment
@pjrobertson

pjrobertson Feb 8, 2012

Owner

Hi again.

The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it. May I suggest you browse to this directory in Finder and delete the 'clipboard module'
~/Library/Application Support/Quicksilver/PlugIns

Once you've done that, try re-downloading the plugin.

Do you have the problem if you restart Quicksilver by pressing ⌘⌃Q or only when Quicksilver is first launched (e.g. when you log in)?

Owner

pjrobertson commented Feb 8, 2012

Hi again.

The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it. May I suggest you browse to this directory in Finder and delete the 'clipboard module'
~/Library/Application Support/Quicksilver/PlugIns

Once you've done that, try re-downloading the plugin.

Do you have the problem if you restart Quicksilver by pressing ⌘⌃Q or only when Quicksilver is first launched (e.g. when you log in)?

@skurfer

This comment has been minimized.

Show comment Hide comment
@skurfer

skurfer Feb 8, 2012

Owner

This happens with the Shelf too. It has nothing to do with B64. It’s been happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only if it was docked. If you’re wondering why I didn’t bring it up, the recent changes didn’t bring up any new problems and never promised to fix my old ones. :-)

I also haven’t been able to find enough of a pattern to make a good report. I’ve seen it on a fresh launch and with a relaunch. Sometimes the panels go away after a second, sometimes I have to move the mouse over them, then mouse out of them and they’ll go away, and sometimes I have to click the close button (which doesn’t close them) then mouse out before they’ll go away.

I’ve mentioned this before, but I’m convinced (in my case anyway) that these panels think they’re docked to a screen edge even though they aren’t. That would explain

  1. Why I can’t dock them to an edge
  2. Why they tend to only go away when I mouse out of them

I haven’t ben able to figure out where the state for these panels is stored between launches, or I would try trashing the settings.

Owner

skurfer commented Feb 8, 2012

This happens with the Shelf too. It has nothing to do with B64. It’s been happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only if it was docked. If you’re wondering why I didn’t bring it up, the recent changes didn’t bring up any new problems and never promised to fix my old ones. :-)

I also haven’t been able to find enough of a pattern to make a good report. I’ve seen it on a fresh launch and with a relaunch. Sometimes the panels go away after a second, sometimes I have to move the mouse over them, then mouse out of them and they’ll go away, and sometimes I have to click the close button (which doesn’t close them) then mouse out before they’ll go away.

I’ve mentioned this before, but I’m convinced (in my case anyway) that these panels think they’re docked to a screen edge even though they aren’t. That would explain

  1. Why I can’t dock them to an edge
  2. Why they tend to only go away when I mouse out of them

I haven’t ben able to figure out where the state for these panels is stored between launches, or I would try trashing the settings.

@pjrobertson

This comment has been minimized.

Show comment Hide comment
@pjrobertson

pjrobertson Feb 8, 2012

Owner

I thought that was for people that did want to see it on launch but
only if it was docked.

Recent (last 6 months) changes to the clipboard module have:

  1. Stopped the panel appearing when other applications quit (the randomly
    appearing bug)
  2. Fixed what you have just mentioned above (which I broke whilst fixing 1)

I did not know anything about the panel appearing on launch.

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.

There's a BOOL in Quicksilver's prefs that specify whether the panel should
open or not on launch. Called QSPasteBoardHistoryIsVisible. Try setting
that to NO.
I'm not sure what the QSPasteBoardController BOOL does, but I have it set
to YES so maybe you should try that if it isn't?
QSGeneralShelfIsVisible also exists for the shelf.

On 8 February 2012 18:13, Rob McBroom <
reply@reply.github.com

wrote:

This happens with the Shelf too. It has nothing to do with B64. Its been
happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it
is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only
if it was docked. If youre wondering why I didnt bring it up, the recent
changes didnt bring up any new problems and never promised to fix my old
ones. :-)

I also havent been able to find enough of a pattern to make a good
report. Ive seen it on a fresh launch and with a relaunch. Sometimes the
panels go away after a second, sometimes I have to move the mouse over
them, then mouse out of them and theyll go away, and sometimes I have to
click the close button (which doesnt close them) then mouse out before
theyll go away.

Ive mentioned this before, but Im convinced (in my case anyway) that
these panels think theyre docked to a screen edge even though they arent.
That would explain

  1. Why I cant dock them to an edge
  2. Why they tend to only go away when I mouse out of them

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.


Reply to this email directly or view it on GitHub:
#691 (comment)

Owner

pjrobertson commented Feb 8, 2012

I thought that was for people that did want to see it on launch but
only if it was docked.

Recent (last 6 months) changes to the clipboard module have:

  1. Stopped the panel appearing when other applications quit (the randomly
    appearing bug)
  2. Fixed what you have just mentioned above (which I broke whilst fixing 1)

I did not know anything about the panel appearing on launch.

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.

There's a BOOL in Quicksilver's prefs that specify whether the panel should
open or not on launch. Called QSPasteBoardHistoryIsVisible. Try setting
that to NO.
I'm not sure what the QSPasteBoardController BOOL does, but I have it set
to YES so maybe you should try that if it isn't?
QSGeneralShelfIsVisible also exists for the shelf.

On 8 February 2012 18:13, Rob McBroom <
reply@reply.github.com

wrote:

This happens with the Shelf too. It has nothing to do with B64. Its been
happening to me for at least 6 years.

The Clipboard module was recently fixed to avoid this behaviour, so it
is strange you are still seeing it.

I thought that was for people that did want to see it on launch but only
if it was docked. If youre wondering why I didnt bring it up, the recent
changes didnt bring up any new problems and never promised to fix my old
ones. :-)

I also havent been able to find enough of a pattern to make a good
report. Ive seen it on a fresh launch and with a relaunch. Sometimes the
panels go away after a second, sometimes I have to move the mouse over
them, then mouse out of them and theyll go away, and sometimes I have to
click the close button (which doesnt close them) then mouse out before
theyll go away.

Ive mentioned this before, but Im convinced (in my case anyway) that
these panels think theyre docked to a screen edge even though they arent.
That would explain

  1. Why I cant dock them to an edge
  2. Why they tend to only go away when I mouse out of them

I havent ben able to figure out where the state for these panels is
stored between launches, or I would try trashing the settings.


Reply to this email directly or view it on GitHub:
#691 (comment)

@skurfer

This comment has been minimized.

Show comment Hide comment
@skurfer

skurfer Feb 9, 2012

Owner

I did not know anything about the panel appearing on launch.

I guess I always thought it was the same thing that made it appear randomly at other times, but now that I think about it, the random appearances when quitting apps does appear to be fixed. I wasn’t suggesting you missed something. :-)

Hmmm. QSPasteboardHistoryIsVisible seems to be NO when Quicksilver is shut down, but when running, I see it set to YES at times. (This is without doing anything in Quicksilver since launch.) I think QSPasteBoardController corresponds to “Hide after pasting”.

I think NSWindow Frame QSPasteboardHistoryWindow must be what I’m looking for. I’ll mess with it tomorrow.

Owner

skurfer commented Feb 9, 2012

I did not know anything about the panel appearing on launch.

I guess I always thought it was the same thing that made it appear randomly at other times, but now that I think about it, the random appearances when quitting apps does appear to be fixed. I wasn’t suggesting you missed something. :-)

Hmmm. QSPasteboardHistoryIsVisible seems to be NO when Quicksilver is shut down, but when running, I see it set to YES at times. (This is without doing anything in Quicksilver since launch.) I think QSPasteBoardController corresponds to “Hide after pasting”.

I think NSWindow Frame QSPasteboardHistoryWindow must be what I’m looking for. I’ll mess with it tomorrow.

@skurfer

This comment has been minimized.

Show comment Hide comment
@skurfer

skurfer Feb 9, 2012

Owner

More info… The problem seems to be with line 61, which reads

BOOL visible = ![(QSDockingWindow *)[[self sharedInstance] window] hidden];

The result seems to alternate between YES and NO every time Quicksilver quits. That is, quitting seems to toggle the setting. So every other launch is where I see the window reappear.

Owner

skurfer commented Feb 9, 2012

More info… The problem seems to be with line 61, which reads

BOOL visible = ![(QSDockingWindow *)[[self sharedInstance] window] hidden];

The result seems to alternate between YES and NO every time Quicksilver quits. That is, quitting seems to toggle the setting. So every other launch is where I see the window reappear.

@pjrobertson

This comment has been minimized.

Show comment Hide comment
@pjrobertson

pjrobertson Feb 9, 2012

Owner

the hidden value is controlled by the setting in QSDockingWindow.m

I guess the hidden BOOL isn't properly being set for you for some reason.

On 9 February 2012 15:53, Rob McBroom <
reply@reply.github.com

wrote:

More info The problem seems to be with line 61, which reads

BOOL visible = ![(QSDockingWindow *)[[self sharedInstance] window]
hidden];

The result seems to alternate between YES and NO every time Quicksilver
quits. That is, quitting seems to toggle the setting. So every other launch
is where I see the window reappear.


Reply to this email directly or view it on GitHub:
#691 (comment)

Owner

pjrobertson commented Feb 9, 2012

the hidden value is controlled by the setting in QSDockingWindow.m

I guess the hidden BOOL isn't properly being set for you for some reason.

On 9 February 2012 15:53, Rob McBroom <
reply@reply.github.com

wrote:

More info The problem seems to be with line 61, which reads

BOOL visible = ![(QSDockingWindow *)[[self sharedInstance] window]
hidden];

The result seems to alternate between YES and NO every time Quicksilver
quits. That is, quitting seems to toggle the setting. So every other launch
is where I see the window reappear.


Reply to this email directly or view it on GitHub:
#691 (comment)

skurfer added a commit to skurfer/Quicksilver that referenced this issue Feb 9, 2012

@sanzoghenzo

This comment has been minimized.

Show comment Hide comment
@sanzoghenzo

sanzoghenzo Feb 15, 2012

I'm experiencing the same problem, should I assume the next version contains the fix?

I'm experiencing the same problem, should I assume the next version contains the fix?

@skurfer

This comment has been minimized.

Show comment Hide comment
@skurfer

skurfer Feb 15, 2012

Owner

should I assume the next version contains the fix?

No, but we’re working on it.

Owner

skurfer commented Feb 15, 2012

should I assume the next version contains the fix?

No, but we’re working on it.

@skurfer skurfer referenced this issue in quicksilver/elements.clipboard-qsplugin Apr 12, 2012

Merged

determine startup state on startup instead of shutdown #3

@skurfer

This comment has been minimized.

Show comment Hide comment
@skurfer

skurfer Apr 12, 2012

Owner

This should have closed automatically when the fix was merged, but of course, didn’t.

Owner

skurfer commented Apr 12, 2012

This should have closed automatically when the fix was merged, but of course, didn’t.

@skurfer skurfer closed this Apr 12, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment