-
Posts
8,512 -
Joined
-
Last visited
-
Days Won
708
Content Type
Blogs
Gallery
Downloads
Events
Profiles
Forums
Articles
Media Demo
Posts posted by vitor
-
-
You mean for PDFs? You have to right-click, yes. Is that an option you change often? Could you expand on why that is?
-
@evortex Could you please email the info@ email address with your Diagnostics? You can get them by typing ?diagnostics into Alfred and then attach to the email.
-
You’re correct, I misinterpreted your screenshot as only having trashed some of them (which wouldn’t be right) because the folder contents were incomplete but I see now what I was missing.
-
I don’t know why they are in the Trash because that’s something that will have happened locally on your side. For example: if you used an overzealous App Cleaner.
What you’re looking at are support files for the Automation Tasks. You can simply update them to set them up in the correct place. -
Please provide the full debug log, as well as a short video with the debugger open.
Include also your version of macOS and the workflow.
-
Are you syncing your preferences? Because the only other thing that occurs to me would be that your sync service would be mangling the file and reverting to an old version. Perhaps try setting your sync folder to somewhere local and repeating the process. Also, as a last resort you can try editing the prefs.plist file directly in a text editor. I don’t recommend this because that is managed by Alfred but you could inspect it as a last resort.
Ultimately, there’s something specific about your macOS set up or OpenAI account that is causing the issue, and that’s what you need to figure out. The workflow isn’t doing anything weird, it uses the most basic tried-and-true methods for configuration that have been in place for a long time. -
@iandol @outcoldman @llityslife Please try this version. Instructions are at the bottom of the About, in the Advanced Configuration section. The update is to be considered experimental and things can change, but this method aims to allow you to use the local models you have set up more easily and not worry about the endpoint being overridden on updates, while at the same time not overwhelming other users.
-
You can use the new Text View for multi-line input. Check the What’s New page for other added features.
-
2 hours ago, sepulchra said:
You can put the lime in the coconut without requiring Harry Nilsson!
Not the first time you’ve made an analogy from music. I like that, digging the sound. I was familiar with some of his other songs but not that one.
2 hours ago, Stephen_C said:I guss you could get more flashy if you wished 😉, write to a text file and provide in the workflow for an option to edit that file if it exists.
See why I enjoy so much when you two discuss workflows? Nice idea!
2 hours ago, sepulchra said:you could add an external trigger to Vitor's Window Switcher Worklfow and then call that workflow after copy to clipboard and pick the open app/window you want to paste into.
Huh, interesting idea too! I can see that being useful in other cases. Just released 2024.1 which adds an External Trigger.
-
Updated to 2024.1.
- Add External Trigger.
- Skip Input as Universal Action.
- Use const for name and description.
-
4 hours ago, Benjamin Thomas said:
To me command enter for delete is risky as it is also new line in a lot of other interfaces.
In the macOS paradigm, ⌘↩ is a submit. Try it e.g. on a comment box on GitHub or this forum. It submits what you have in the textarea. Newlines are typically ⌥↩ and/or ⇧↩.
4 hours ago, Benjamin Thomas said:Also, why not just GPT as a keyword?
Realize I can customize this
ChatGPT is the name of the service. A GPT is a related but different thing. This makes the keyword more obvious. And as you noted, you can customise it to your liking very easily. Some people use just c.
-
If you’re looking to manipulate the position of Finder windows, you could do that previously. Use the Open File Action to open a specific folder and connect it to the Set Custom Window Bounds Automation Task. Chain a few in a row and watch your windows open and be layed out. Like so:
You’ll need to do the math on the positions and sizes to construct your grid.
-
This will be live in the Gallery soon at https://alfred.app/workflows/godbout/music-volume/.
On 2/13/2024 at 5:36 AM, godbout said:obrigado!
You’re welcome!
On 2/13/2024 at 5:36 AM, godbout said:obrigadinho.
I know you mean nothing by it—but just as a reference to avoid a faux pas if you’re ever interacting with another Portuguese—we almost exclusively use that word (the diminutive of “thank you”) sarcastically. Think “yeah, thanks a lot” in English. I’m not sure if that connotation is shared by other countries with Portuguese as the first language, though. Either way, no harm no foul. Since you went through the trouble of learning the words, I thought you might like the context.
Have a great weekend!
-
Looking at the workflow, it might work if you simply change the Language dropdown in the Run Script to /usr/bin/python3. That is assuming it’s not using features which changed in Python 3, but it’s small enough it might work.
-
Try the fake_key suggestion above. What do you get?
-
17 minutes ago, evortex said:
I repeated all the steps above.
And just to be sure: on step 2 you got no results?
Had another idea: Try setting the API key to something obviously wrong, like fake_key. What do you get then when using the workflow? -
- Remove the workflow.
- Try to use it. This step is important to make sure you don’t have e.g. some duplicate copy that you’re calling.
- Install it again, from the Gallery page. Make sure it’s version 2024.3 and that the configuration field for the key is empty.
- Add your API key to the configuration field.
- Try again.
What do you get now? If you’re still getting a notice with the old key after that you may have to contact OpenAI. Maybe they’re correlating both keys and sending an incorrect message. But the workflow only uses whatever string in pasted into the configuration, nothing else.
-
40 minutes ago, evortex said:
Also: If I enter a new key in the workflow prefrences (just to be sure), it is still using the "old" key.
What exactly do you mean by this? Are you editing the default value in the configuration builder? Don’t, that should be left empty. But yes, even if doing that it would still use the key set in the correct place, that’s working as intended.
As per above, that error message is not in the workflow, it’s being returned by OpenAI themselves. Make sure you’re not using an old or invalid key or pasting extra stuff. That’s an issue which can only be solved from your side.
-
Where exactly are you adding the key? Please provide a screenshot.
-
The API doesn’t allow that, so that’s a request you have to make to OpenAI.
-
If you’re looking to import snippets from CSV files, you can use the official Snippet Transformer.
-
Updated to 2024.1.
- Skip Input as Universal Action.
- Remove colons in keyboard shortcuts.
- Edit shortcut with Automation Task.
- Add Hotkey.
- Use JSON caching.
- Split between shortcuts which take input or not.
- Convert scd to JXA.
- Shorter Objective-C functions.
- Fix typo.
- Floating.Point and jesused
- 2
-
6 minutes ago, Mr Pennyworth said:
Specifically, it looks like it toggles between two options. Is that right?
Correct. Try it also on the Text View and Image View. -
46 minutes ago, Mr Pennyworth said:
Dragging files out of the grid view
That works now. Set the type key in the JSON to file. Or try it just by sending a list of files to the Grid View with Object Input as the Source.
1 hour ago, Mr Pennyworth said:Size of the grid and text views
Try ⌘0. That shift in size is remembered per object, which means that you can have them bigger or smaller depending on context and also adapt on demand.
- universe and luckman212
- 1
- 1
Using alternative and local models with the ChatGPT / DALL-E workflow
in Workflow Help & Questions
Posted
I’m not seeing it. You’re in the position to find out since you can test with your model. You’ve poked around in the code before so you can look in the same whereabouts and try different things, like console.log the values, remove the / in the code and add it in the variable, using a replace… Until the cause is clear and can be properly addressed.