AgileBits Update: Please don't do this. Details on why are outlined in this post. - Thanks.
Folks,
TL;DR: Skip to Solution below
I see this on:
1Password 7, Version 7.4.4.BETA-0 (70404000) 1Password Beta
on mac os 10.14.6 on the main 1password window.
There the command mentioned there is: defaults delete com.apple.Photos NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
The help window (ie the ? top right) says something similar The domains where this default is set are: NSRegistrationDomain (volatile) defaults delete «domain» NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
Dumping all defaults from my user context to a with defaults read >alldefaults.out.txt
shows only one case where "NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints" shows up
for com.agilebits.onepassword7-updater
So: Experimenting, quit one password completely, I execute defaults delete com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
both defaults read com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
and a dump defaults read >alldefaults.out.txt confirm the key is gone,
however not even rebooting it avoids the issue.
After some head-scratching, i conclude it is set as a debug flag in the app code at runtime in the (volatile==in memory NSRegistrationDomain)
Further googling reveals this stackoverflow answer: https://stackoverflow.com/a/23157051
Solution:
1. quit 1Password completely,
2. execute from a terminal: defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NO
4. Start 1Password
5. Problem solved.
From what I understand this sets the flag GLOBALLY for ALL programs, so perhaps not the solution for developers, bc this will suppress it for all users and all programs.
Better solution perhaps to set it at the app level by using: defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NO
However this might mean it crops up on sub modules, like the Updater?
Depending on a users tastes the global setting may be preferable.
Best regards, Martin
PS:
Further experimentation reveals that both defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool false
and defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool false
work just as well, & set the type to the proper boolean value & the help does in the top right does change once the default value is set on the app level.
Also defaults read com.agilebits.onepassword7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
and defaults read -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints
So I learned something about the mac today.
;-)
PPS:
one more item to track this down to the actual code:
Clicking on the purple frame yields the following entries in Console.app
We would really prefer people not do that, as then we won't get valuable feedback about UI issues. The reason we publish beta builds is so we can get that kind of feedback. Without that feedback there isn't much incentive to provide betas.
I found how to reproduce it.
Open up the help menu and start typing something you are searching for. (1 Character is enough). Then backspace all the way. It will immediately pop up.
Thanks for reporting this issue. That one is unfortunately not one that we'll be able to directly solve as that is an issue with Apple's help menu search field.
I've got the purple border of doom.
osx 10.15.4
1Password 7
Version 7.6.BETA-0 (70600000)
1Password Beta
I'm in safari, using cmd-\ to fill a dialog
I've gotten it a bunch of times this morning
No suggestions; the "purple windows" are intentional. They're there to help developers identify UI issues. They will only show in beta builds, not stable builds. What part of 1Password are you seeing this particular window in? I.e. What are you trying to do when you see the window? I'll let our development team know to make sure they're aware. Thanks.
@Ben I am not doing anything. Just have 1Password running. If I quit and restart 1Password it just pops up. Frequently empty, like this:
Should I capture and share logs?
Can you please try quitting 1Password completely (right-click on 1Password mini in the menu bar at the top right of your screen > Quit 1Password Completely), and then relaunch 1Password? Do you see the same behavior?
Comments
Can still reproduce when I try to Quick Look 1Password documents
Team Member
Hi @gboudreau ,
Is it all quicklook documents or just a specific type? (e.g. images, PDF, word doc, etc.)
Thanks,
Kevin
Getting this message as well on the latest beta
Team Member
@agilerabbit:
Do you get this message all the time or just when you try to quicklook 1Password documents?
All the time!
Team Member
Thank you for the confirmation
We will continue looking into this.
AgileBits Update: Please don't do this. Details on why are outlined in this post. - Thanks.
Folks,
TL;DR: Skip to Solution below
I see this on:
1Password 7, Version 7.4.4.BETA-0 (70404000) 1Password Beta
on mac os 10.14.6 on the main 1password window.
I thought that there may be a way to fix this via the command-line along the lines of this post for Apple Photos
https://discussions.apple.com/thread/7259036
There the command mentioned there is:
defaults delete com.apple.Photos NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsThe help window (ie the ? top right) says something similar
The domains where this default is set are: NSRegistrationDomain (volatile) defaults delete «domain» NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsDumping all defaults from my user context to a with
defaults read >alldefaults.out.txtshows only one case where "NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints" shows up
for com.agilebits.onepassword7-updater
So: Experimenting, quit one password completely, I execute
defaults delete com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsboth
defaults read com.agilebits.onepassword7-updater NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsand a dump
defaults read >alldefaults.out.txtconfirm the key is gone,however not even rebooting it avoids the issue.
After some head-scratching, i conclude it is set as a debug flag in the app code at runtime in the (volatile==in memory NSRegistrationDomain)
Further googling reveals this stackoverflow answer:
https://stackoverflow.com/a/23157051
Solution:
1. quit 1Password completely,
2. execute from a terminal:
defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NO4. Start 1Password
5. Problem solved.
From what I understand this sets the flag GLOBALLY for ALL programs, so perhaps not the solution for developers, bc this will suppress it for all users and all programs.
Better solution perhaps to set it at the app level by using:
defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints NOHowever this might mean it crops up on sub modules, like the Updater?
Depending on a users tastes the global setting may be preferable.
Best regards,
Martin
PS:
Further experimentation reveals that both
defaults write -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool falseand
defaults write -globalDomain NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints -bool falsework just as well, & set the type to the proper boolean value & the help does in the top right does change once the default value is set on the app level.
Also
defaults read com.agilebits.onepassword7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsand
defaults read -app 1Password\ 7 NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraintsSo I learned something about the mac today.
;-)
PPS:
one more item to track this down to the actual code:
Clicking on the purple frame yields the following entries in Console.app
The first with the sidebar expanded
The second with the sidebar collapsed
Team Member
@MaForisch
We would really prefer people not do that, as then we won't get valuable feedback about UI issues. The reason we publish beta builds is so we can get that kind of feedback. Without that feedback there isn't much incentive to provide betas.
Ben
I just got this issue
From the about screen:
1Password 7
Version 7.4.4.BETA-0 (70404000)
1Password Beta
I have the same issue when I select help from the menu bar.
Although I'm trying to get steps to reproduce it, but so far cannot.
Here's a better look at the purple window:
I found how to reproduce it.
Open up the help menu and start typing something you are searching for. (1 Character is enough). Then backspace all the way. It will immediately pop up.
Team Member
@skarchmit,
Thanks for reporting this issue. That one is unfortunately not one that we'll be able to directly solve as that is an issue with Apple's help menu search field.
I've got the purple border of doom.
osx 10.15.4
1Password 7
Version 7.6.BETA-0 (70600000)
1Password Beta
I'm in safari, using cmd-\ to fill a dialog
I've gotten it a bunch of times this morning
Team Member
@huffalumpy
Hopefully, the developers can get this one fixed up. Thanks for the report.
I am getting this now as well with:
Any suggestions?
Team Member
Hi @vidgizmo
No suggestions; the "purple windows" are intentional. They're there to help developers identify UI issues. They will only show in beta builds, not stable builds. What part of 1Password are you seeing this particular window in? I.e. What are you trying to do when you see the window? I'll let our development team know to make sure they're aware. Thanks.
Ben
@Ben I am not doing anything. Just have 1Password running. If I quit and restart 1Password it just pops up. Frequently empty, like this:
Should I capture and share logs?
Team Member
@vidgizmo:
Can you please try quitting 1Password completely (right-click on 1Password mini in the menu bar at the top right of your screen > Quit 1Password Completely), and then relaunch 1Password? Do you see the same behavior?