Skip to content

Primer doesn't like 'indirectOptional' arguments #1215

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.

Sign up for GitHub

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

Jump to bottom
Closed
pjrobertson opened this issue Nov 15, 2012 · 1 comment · Fixed by #2669
Closed

Primer doesn't like 'indirectOptional' arguments #1215

pjrobertson opened this issue Nov 15, 2012 · 1 comment · Fixed by #2669
Labels
noactivity Visual

Comments

@pjrobertson
Copy link
Member

This one courtesy of @tiennou

For some strange reason Primer places the iSelector on top of the dSelector for indirectOptional commands (try Run […])
pjrobertson added a commit that referenced this issue Mar 12, 2022
@pjrobertson
Properly fade iSelector in/out in primer
5b8fa13 
Set the iSelector opacity correctly based on indirect optional. Fixes #1215
@pjrobertson pjrobertson mentioned this issue Mar 12, 2022
Merged
@stale
Copy link

stale bot commented Apr 4, 2022

This issue hasn't been updated in over 2 years. It has been marked as 'stale' and will be closed in 30 days. Please check whether this is still an issue with the latest version of Quicksilver. If so, update or comment on this issue to keep it open.

@stale stale bot added the noactivity label Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
noactivity Visual
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update QSFadingView quicksilver/Quicksilver
1 participant
@pjrobertson