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

Groups (i.e. folders) for Triggers don’t work at all #135

Closed
jackbrannen opened this issue Nov 19, 2010 · 12 comments
Closed

Groups (i.e. folders) for Triggers don’t work at all #135

jackbrannen opened this issue Nov 19, 2010 · 12 comments

Comments

@jackbrannen
Copy link

For instance, in the Triggers window, trying to move a trigger into a group has no effect.

@pjrobertson
Copy link
Member

Confirmed.

Gives:

20/03/2011 01:40:20 Quicksilver[9834] drop on nil description - 788E8BCC-E114-41BF-B9AF-A5F7ED6343EF at index -1
20/03/2011 01:40:20 Quicksilver[9834] indexes: (
"<NSIndexPath 0x141051e0> 1 indexes [14]"
)

In the console

@HenningJ
Copy link
Contributor

This works for Catalog entries, but not for Triggers. Got to look at what's the difference there.

@jackbrannen
Copy link
Author

Since the big 64 bit hurdle has been cleared (woohoo!) I thought I might bump this again, if anyone is interested in taking it. I imagine it’s not a huge bug to squash, but it would be wonderful to have this working again.

@jxpx777
Copy link

jxpx777 commented Jul 20, 2013

Any progress on this? I just tried it in 1.0.0 and it is still broken…

@floriskruisselbrink
Copy link

This is still not fixed in 1.1.3 (4007).
Either remove the ability to create trigger groups until this is fixed, or just fix it.

The way it looks now in the app is completely confusing.

@gdvine
Copy link

gdvine commented Feb 7, 2019

This appears to still be broken. User can create a group, but cannot drag Triggers into it.

@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 that needs to be fixed, and if so please update or comment on this issue to keep it open.

@stale stale bot added the noactivity label Apr 4, 2022
@MonkeyBars3k
Copy link

This issue still exists... going on nearly 12 years

@stale stale bot removed the noactivity label Apr 4, 2022
@pjrobertson
Copy link
Member

For the meantime, we have removed the option to create 'groups' for triggers, as it still does not work.

@MonkeyBars3k
Copy link

Shouldn't the status be "Won't fix" rather than Closed?

@pjrobertson
Copy link
Member

Sure, that makes sense. Thanks

@borgo1971
Copy link

R.I.P... If they was working, they could be very nice to organise triggers...
Note: I'm here because using QS 2.2.2, I wanted to open the issue. Now I'll update :-(

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

No branches or pull requests

8 participants