Jump to content

twberger

Member
  • Posts

    6
  • Joined

  • Last visited

Everything posted by twberger

  1. Sorry for the late reply, I was an idiot and assumed I got auto-subscribed to this topic. I haven't, but I will. It definitely does seem like Adobe is the one doing something odd, but I posted here because a) I'm almost certain Adobe won't be as responsive as you, and being able to deal with odd software could only make Alfred better. Even if Adobe fixes it, whatever they were/are doing that causes the problem could still be done by somebody else. I haven't installed it, but supposedly there is one window manager that does work with Photoshop, slate. Maybe there's a hint as to why in its code - it's open-source. Another hint may be that Photoshop seems to treat its tabs as windows, and the over-arching window as not a window - Cmd-w closes tabs, but won't close the window. Also, I read that older versions of photoshop didn't even have a main menu, that the tools were all in floating toolbars. Maybe the main window still uses some sort of mode intended for floating toolbars?
  2. Steps to reproduce: 1. Launch Adobe Photoshop CS6 and focus its window 2. Activate Alfred (hit the assigned keyboard shortcut) Expected behavior: the Alfred popup is drawn on top of the Photoshop window Actual behavior: Photoshop's window disappears, revealing whatever was beneath it, and the Alfred popup is drawn on top of that. When Alfred is closed, the Photoshop window reappears. OS X: 10.9.5 Alfred: 2.4 (279) This happens 100% of the time, across many reboots and even multiple versions of Alfred, Photoshop, and OS X. I haven't seen it with any application but Photoshop. Speculating now, but I suspect Photoshop is using some alternative windowing mechanism that is interacting poorly. I've noticed that Photoshop also breaks tools that resize windows, like Cinch and Spectacle.
  3. Currently I'm just seeing what looks like an "unknown application" icon. Finding and launching it work just fine, but it would be nice to have the icon as well. This behavior - mirroring the target's icon in the alias's icon - is what Finder does, so implementing it would bring Alfred more in-line with native behavior.
  4. Currently the Features tab is subdivided by the process that runs when the feature is activated, eg "File Search", "Web Search", "Calculator", etc. I think it would make more sense to subdivide by keyword. The main view could be a list similar to the "list" view in Finder, with a column for each trigger type, and and column for the handler (containing a button/link leading to the handler configuration). This has the benefit of giving a top-down view of the entire behavior, allowing users to quickly see how their input is being interpreted. It would give users a "cheatsheet", making it much easier for them to learn all associations between keywords and features. Optionally, this would also allow you to divorce handlers from their keywords, making it easier to think about and change each independently.
  5. Came across this and it's exactly what I wanted, except that I'm not crazy about the 0.5 second delay. There's no guarantee Calendar will be running in 0.5 seconds, and if it's already running then you have to wait 0.5 seconds for nothing. So I tweaked it a bit (with the help of reddit.com/u/cooper12), and made it run immediately if Calendar is running, otherwise wait until Calendar is ready. on alfred_script(q) activate application "Calendar" repeat until application "Calendar" is running delay 0.1 end repeat activate application "Calendar" tell application "System Events" keystroke "n" using {command down} keystroke q keystroke return end tell end alfred_script
×
×
  • Create New...