See the tips and fixes for your platform's
first-run warnings,
and
app-folder permissions.
Both of these apply only to the macOS app, not source code.
The
readme
covers Launchpad on your platform.
Mojave users: see also this
to fix crashes and blank windows caused by macOS dark mode.
Apple M-chip users: the Rosetta 2 emulator is required to run the app package
(until 3.0), but not source code.
Update: per 2023 vetting on macOS Ventura, launching the 2017 app package directly
no longer works, because its splashscreen cannot open the main program; launch instead
by opening the app package's main program at Contents/MacOS/frigcal
within the unzipped Frigcal.app.
The source-code package still works in full, but
a newer Tk used by newer Pythons may cause text-color issues in dark mode
(e.g., white on light); work around this by config-file color changes, or disabling
dark mode—either globally, or for Python with commands
here.
Update: in 2024, Frigcal 3.0 makes most preceding concerns moot. The macOS app runs
natively on both Intel and Apple M-chip devices, the launcher is replaced by a
frigcal-main.py run by the app, and dark-mode colors
and recent Tk cosmetic changes have been accommodated.
Update: in 2025, a macOS Catalina test machine began using white as the highlight
color for all selected text in dark mode, which is unusable with light backgrounds.
This impacts all Tk-based GUIs on this machine, and is likely a macOS or Tk bug.
Fortunately, its one-time workaround is easy: open System Preferences => General,
and change the "Highlight color" there to Blue (or other). Alternatively, pick a
dark color scheme via frigal_configs.py settings, or use light mode on your macOS PC.
Update: as of 2025, recent versions of macOS have grown more heavy-handed in their
treatment of apps installed from sources other than the Apple app store. This
includes Frigcal, whose first run will generate an ominous and wholly invalid
warning
with neither pointers to remedies nor options in Settings. To get Frigcal to open on these
macOS versions, you must first run one of the following command lines in the Terminal app
(replace Applications with your unzip/install folder if you haven't
moved the app there):
xattr -c /Applications/Frigcal.app
xattr -r -d comp.apple.quarantine /Applications/Frigcal.app
The first of these clears all extended attributes on the app and the second removes
just its quarantine attribute. Once you've run either of these one-time setup steps,
the app will open without warnings thereafter. For screen captures of the process,
see this gallery. Though untested, you may
also be able to fully disable the Gatekeeper layer behind the new constraints; more info
here and
here.
See this doc
for details on running Frigcal on your platform. In short, you'll fetch and
patch its source-code package, and launch it in an app's IDE.
Android 11+ users: see also this
for recent changes on Android; most don't impact Frigcal directly (until the next note).
Update: in 2023, Pydroid 3's version 6 imposed extra steps for
running this program on Android; see the coverage
here and
here.
In short, you must unzip and run in a specific accessible
folder, and sync or copy your calendar files to the same.
Update: in 2024, Pydroid 3's version 7 finally obtained Android's All Files Access
permission, which restores access to shared storage in code the app runs and negates
the preceding note. See the update
Update: in 2024, Android no longer requires code patches, because Frigcal
3.0's source-code package incorporates all former Android patches: simply
install and run its "frigcal-main.py" in the Pydroid 3 app. You may also
configure as usual in "frigcal_configs.py' and a commented-out code line in
"frigcal-main.py" may be enabled to support file-explorer opens and shortcuts.
For more details, see section "4. PLATFORMS" in
README-3.0.txt
![[Home page]](PythonPowered.gif "Home page"){kind=small}
