swiftDialog 2.5.4

Hotfix release for some issues present in 2.5.3

• notifications causing boilerplate windows popping up #467
• boilerplate text being used when "" is provided to denote a null value #467
• overlay icons not showing when using a single --icon and --centreicon is used #466

swiftDialog 2.5.3

New:

• Added ability to create QR codes as images
  • e.g. --icon qr=<text> where can be a URL or other string
• Multiple icons can be specified when using --centreicon which will display centred along the top of the window
  • e.g. --centreicon --icon image1.png --icon image2.png --icon image3.png
• Added --helpimage which will add an image to the right of any --helpmessage. accepts any valid image type
  • e.g. --helpmessage "Scan the QR code for help" --helpimage "qr=https://swiftdialog.app"

Fixes:

• --webcontent caching account/sessions between dialog instances #439
• Add check for CGSession to make login window operations on boot more reliable #442
• moved file select dialog to a popover sheet. This lets it inherit the window peoperties of the parent and appear over the top of blurscreen #441
• Allow --helpmessage to support markdown files #447
• Fixed #456 - Enable rounded corners when using base64 encoded images
• Remove dependency on third party fileicon shell script for branding.
• Add -H option to the sudo command in the runAsUser function in /usr/local/bin/dialog script. Should help with context when performing tasks like launching URL's in Chrome

Under the hood changes

A lot of updates to how command line arguments are processed internally. This doesn't change operation but will assist future planned refactoring work.

Known issues

On macOS 15 you might see the following on stderr:

2024-10-24 19:07:22.157 Dialog[26712:1399071] +[IMKClient subclass]: chose IMKClient_Legacy
2024-10-24 19:07:22.157 Dialog[26712:1399071] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

This shouldn't affect any output processing and can be ignored. It has been raised as an issue to Apple as FB15576915 and is not unique to swiftDialog.

Workaround: send stderr to null i.e. dialog <args> 2>/dev/null

swiftDialog 2.5.3 Beta 3

All the things in Beta 2 plus the following:

• Added ability to create QR codes as images
  • e.g. --icon qr=<text> where can be a URL or other string
• Multiple icons can be specified when using --centreicon which will display centred along the top of the window
  • e.g. --centreicon --icon image1.png --icon image2.png --icon image3.png
• Added --helpimage which will add an image to the right of any --helpmessage. accepts any valid image type
  • e.g. --helpmessage "Scan the QR code for help" --helpimage "qr=https://swiftdialog.app"
• Fixed #456 - Enable rounded corners when using base64 encoded images

swiftDialog 2.5.3 Beta 2

Fixes

Same as Beta 1

• --webcontent caching account/sessions between dialog instances #439
• Add check for CGSession to make login window operations on boot more reliable #442
• moved file select dialog to a popover sheet. This lets it inherit the window peoperties of the parent and appear over the top of blurscreen #441
• Allow --helpmessage to support markdown files #447

Additional

This release is compiled with Xcode 15.4 instead of 16 which should resolve the issue where swiftDialog might not launch depending on the order and arrangement of the arguments you use when run on macOS 15. This has been raised as an issue with Apple as FB15577018

Under the hood changes

A lot of updates to how command line arguments are processed internally, mostly while debugging the issue with argument order described above. This doesn't change operation (or shouldn't, please test) but will make future planned refactoring a bit easier.

Known issues

On macOS 15 you might see the following:

2024-10-24 19:07:22.157 Dialog[26712:1399071] +[IMKClient subclass]: chose IMKClient_Legacy
2024-10-24 19:07:22.157 Dialog[26712:1399071] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

This output appears on stderr and shouldn't affect any output processing and can be ignored. It has been raised as an issue to Apple as FB15576915 and is not unique to swiftDialog.

swiftDialog 2.5.3 Beta 1

Fixes:

• --webcontent caching account/sessions between dialog instances #439
• Add check for CGSession to make login window operations on boot more reliable #442
• moved file select dialog to a popover sheet. This lets it inherit the window peoperties of the parent and appear over the top of blurscreen #441
• Allow --helpmessage to support markdown files #447

swiftDialog 2.5.2

Some small fixes and updates:

• update command file processing so all commands are parsed for built in variables
• update processing for markdown files so built in variables get processed
• fix mini mode because button3 doesn't belong there #427
• fix image corner radius when displayed as a list item icon #430
• fix error and help sheets when displayed in a login window context #404
• update authorisation key localisation #395

swiftDialog 2.5.2 Beta 1

Fix release

• Fix issue where default system properties like {computername} could not be used via command file #426
• Fix issue where infobutton could be displayed in mini view (wasn't designed to support that) #427
• Fix default image corner radius when used in info list items. was too large for the display size #430
• Fix error and help sheets not displaying in the login window context #404
• Fix help text for --key argument to add support for localised spelling of Authorisation. Also added AuthKey or just Key as valid key names. Will need to update the wiki #395

Some general code tidy up, particularly in how command file command and argument is processed. Some testing required but there shouldn't be any noticeable differences.

swiftDialog 2.5.1

Fixes:

• Fix "Builtin Variables not working when using markdown files" - issue #417
• Fix issue where windowbuttons behaviour could not be set using json
• Fix "Dialog Version 2.5 does not launch on macOS Monterey" - issue #386
• Fix "swiftDialog crashes with macOS Sequoia" - issue #400
• Fix "5302 Illegal instruction" - issue #412
• Fix "Crash when updating message if a list is present" - issue #415
• Fix "141 error on launch" - issue #420
• Fix issue where --displaylog ignores the first line sent to the file being watched - issue #396
• Merge "Adds Timer functionality to buttonstyle "stack"" - issue #414
• Merge "Fix typos in help text" - issue #403
• Merge "explicitly use spaces instead of tabs" - issue #390
• Merge "Imply ontop when using loginwindow" - PR #423
• Removed experimental stuff from the pkg postinstall script that I never reached 100% happiness with and thus was never documented or supported anyway.

Additions:

• Add "blurscreen" control to command file - blurscreen: <command> - enable to turn on, anything else to disable - issue #416
• New --appearance command. Takes options dark or light and will force swiftDialog to assume a dark or light appearance regardless of the users current preferences are. #421
• Icon assets can have an additional property to support alternate sources depending on system appearance. include :dark= and the path to the alternate source. Example --icon /path/to/light_icon.png:dark=/path/to/dark_icon.png
  • Note: The after launch, the image will be whatever was appropriate for dark or light mode. If the system or user changes appearance while swiftDialog is running, the image will not update. The exception to this is if SF Symbols are used which will update to the appropriate appearance.
  • Supported anywhere an icon image can be used (overlay, icon, list items etc)

swiftDialog 2.5.1 Beta 3

Fix macOS 12 and macOS 15 support

Hot on the heels of Beta 2 - The following issues should be resolved:

• #386 Dialog Version 2.5 does not launch on macOS Monterey
• #400 swiftDialog crashes with macOS Sequoia
• #412 5302 Illegal instruction: 4
• #415 Crash when updating message if a list is present
• #420 What would cause dialog to return 141 and not display a dialog

swiftDialog 2.5.1 Beta 2

↩️ Un-Breaking Change ↩️

swiftDialog 2.5.1 is back to being compiled for the macOS 12 SDK. The 2.5.0 release has a number of issues mostly related to changes in the way Markdown is rendered.

Caution

Known Issues in macOS 12

If you send an update or initiate a dialog with a single line of text, dialog with crash. If your message text extends to multiple lines (as > a single string or as multiple lines with embedded line breaks) then it should still display fine on macOS 12

macOS 13+ are not affected

If you're using macOS 12, it's still recommend you pin v2.4.2 for best results.

Updates in this release

• All the changes in Beta 1
• New --appearance command. Takes options dark or light and will force swiftDialog to assume a dark or light appearance regardless of the users current preferences are. #421
• Icon assets can have an additional property to support alternate sources depending on system appearance. include :dark= and the path to the alternate source:
  • e.g. --icon /path/to/light_icon.png:dark=/path/to/dark_icon.png
  • Note: The after launch, the image will be whatever was appropriate for dark or light mode. If the system or user changes appearance while swiftDialog is running, the image will not update. The exception to this is if SF Symbols are used which will update to the appropriate appearance.
  • Supported anywhere an icon image can be used (overlay, icon, list items etc)
• Fix issue where --displaylog ignores the first line sent to the file being watched #396
• Merge #423 - "Imply ontop when using loginwindow"
• Removed experimental stuff from the pkg postinstall script that I never reached 100% happiness with and thus was never documented or supported anyway.
• Set built target back to macOS 12