You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Per short chat in Slack, I've discovered that sending progress: [ hide | remove | delete ] to a running dialog in mini mode does not hide/remove the progress bar, and it instead remains in its last set state. Each of these keywords function as expected with a standard (not-mini) dialog.
This behavior exists in the latest dialog version as of this writing (2.4.2).
To Reproduce
Steps to reproduce the behavior:
Create dialog in mini mode with a command file. For consistency, the exact command used to validate this bug is: /usr/local/bin/dialog --mini --message "something" --progress 100 --commandfile /private/tmp/testcmd.log --moveable &
Send progress: hide (or remove/delete) to the command file: echo progress: hide >> /private/tmp/testcmd.log
Observe that the progress bar remains visible.
Repeat these steps without --mini in step 1, and step 2 hides the progress bar as expected.
Expected behavior
The progress bar should be hidden when the appropriate command is sent to a dialog's command file when using mini mode. As shown in the screenshots below, other progress: commands function as expected.
Screenshots
Desktop (please complete the following information):
macOS version: 14.4.1
swiftDialog version: 2.4.2
Additional context
This issue was originally identified with dialog 2.3.2. Upgrading to 2.4.2 did not resolve the issue.
The text was updated successfully, but these errors were encountered:
This is intended behaviour. The purpose of mini mode is to provide a quick progress indicator or message. It's dismissed by sending a quit: command when complete.
Describe the bug
Per short chat in Slack, I've discovered that sending
progress: [ hide | remove | delete ]
to a running dialog in mini mode does not hide/remove the progress bar, and it instead remains in its last set state. Each of these keywords function as expected with a standard (not-mini) dialog.This behavior exists in the latest dialog version as of this writing (2.4.2).
To Reproduce
Steps to reproduce the behavior:
/usr/local/bin/dialog --mini --message "something" --progress 100 --commandfile /private/tmp/testcmd.log --moveable &
progress: hide
(or remove/delete) to the command file:echo progress: hide >> /private/tmp/testcmd.log
--mini
in step 1, and step 2 hides the progress bar as expected.Expected behavior
The progress bar should be hidden when the appropriate command is sent to a dialog's command file when using mini mode. As shown in the screenshots below, other
progress:
commands function as expected.Screenshots
![image](https://private-user-images.githubusercontent.com/37225540/322879472-6f013f50-f8bc-4777-8194-e304d79fd253.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyNDE5MjAsIm5iZiI6MTcyMDI0MTYyMCwicGF0aCI6Ii8zNzIyNTU0MC8zMjI4Nzk0NzItNmYwMTNmNTAtZjhiYy00Nzc3LTgxOTQtZTMwNGQ3OWZkMjUzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA2VDA0NTM0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM3YzJkNTNhNzk3MjI1ZDZiM2VlNzg3ZGFjMmY5MTJlMjVlMDA1ZDhmZWZiYWQ3ZjRiYzdmYzBjOWFlMGE4OGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.RrFPxgygbxEfENLNk_x9xIXtSFoSuhJx4JIw-STm9e4)
![image](https://private-user-images.githubusercontent.com/37225540/322879832-f856a3f3-cab8-4132-a3a8-b7d5724fd5c9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyNDE5MjAsIm5iZiI6MTcyMDI0MTYyMCwicGF0aCI6Ii8zNzIyNTU0MC8zMjI4Nzk4MzItZjg1NmEzZjMtY2FiOC00MTMyLWEzYTgtYjdkNTcyNGZkNWM5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA2VDA0NTM0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJjYzZiY2UzZTk1ZDM2NDk2NGM2MWRiNjdhZGU3N2MyMmFmMDNmOTQ3YTM0YmY1NGY4Njc0ZTk4MTAxZjExY2ImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.lSsF1UB4b5gTdUHy1r05mAdjrCvAg9YtwJpXd9WBXLU)
![image](https://private-user-images.githubusercontent.com/37225540/322880194-c95e8d5d-80a9-48e8-be2b-fb2e5dc89c6b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyNDE5MjAsIm5iZiI6MTcyMDI0MTYyMCwicGF0aCI6Ii8zNzIyNTU0MC8zMjI4ODAxOTQtYzk1ZThkNWQtODBhOS00OGU4LWJlMmItZmIyZTVkYzg5YzZiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA2VDA0NTM0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY2OTYyYjNhZGFkZDE4YmVkM2UyYTBjNjRlZGY1MzQxNzI0MjFmYTIyOTM3MTliZTcxZDlhYzQzMmMyNWFiOTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.qtiND9vdY48RW7_zsSZcKrg3pCh_L0uZX4tFHXsBJ-A)
Desktop (please complete the following information):
Additional context
This issue was originally identified with dialog 2.3.2. Upgrading to 2.4.2 did not resolve the issue.
The text was updated successfully, but these errors were encountered: