Date picker - #7
Open
brettz9 wants to merge 3 commits into
Open
Conversation
- Enhancement: Promise return option - Enhancement: Default to timeout of 0 - Optimization: Add `use strict` directive - Docs: Syntax highlight example - npm: Fix: `license` and add recommended `contributors` property
…lias on Mac - .gitignore
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on PR #6 to update the date-picker.
AppleScript code kindly updated by CJK and submitted with permission under the MIT license as per https://stackoverflow.com/questions/56216434/problem-with-date-picker-showing-main-thread-issue/56217976 .
I've wrapped the Applescript in an Automator workflow which we can use to allow the datepicker out of a normal GUI context to continue to work while returning stdout.
Unfortunately, as
man automatorshows on the Mac, this CLI interface has no way to build a workflow from the command line, so I cannot add a programmatic step showing how to build the workflow file (unless perhaps I were to make an Automator workflow to build the Applescript-based workflow, but that would still require bundling a workflow!). At least the non-strings files are transparent.