Welcome to the Linux Foundation Forum!
Help function of "dialog"
langerak
Posts: 15
in Command Line
Hi all,
I'm currently writing some bash scripts using the "dialog" functionality to enhance the user experience on the command line.
All is going well, but there is one problem I cannot sort out and little info is found via Google, that is, the help system of dialog. There are options to show a help button and when the user selects it, the corresponding help text appears.
I can get the button to shop up, but there is no documentation on how to show the corresponding help text into a box. Dialog just quits with "HELP:".
Does anyone here on the forums have any usable knowledge about the help functionality of dialog and is willing to help me out?
Thanks in advance and should you need more information, please ask, so I can supply it.
0
Comments
-
Hmm, I haven't thought about that strategy yet. Though it is a bit cumbersome, especially when handling multiple actions and various dialog boxes. I would have to think about a good strategy for that.
Another question, if I read the help correctly, it should be possible to keep the originating window and place the help window on top of that. Do you have any idea to accomplish this?
Thanks already for your help!0 -
That's possible, I'm only pasting the part of what's relevant, since it's a huge script by now
#!/bin/bash escaper() { action=$? if [ $action = 1 -o $action = 255 ]; then dialog --title "$title" --yesno "\nAre you sure you want to quit?" 7 35 sure=$? if [ $sure = 0 ]; then clear exit fi fi } genhour() { genhour=9 hour=$RANDOM let "hour %= $genhour" } genminute() { genminute=59 minute=$RANDOM let "minute %= $genminute" } pid=$(echo $$) if [ -z $1 ]; then genhour genminute dialog --backtitle "$backtitle" --title "$title" --keep-window --form "\nYour Backup Account Details\n" 20 60 0 \ "Username....:" 1 1 "" 1 15 14 0 \ "Password....:" 2 1 "" 2 15 14 0 \ "Server......:" 3 1 "" 3 15 30 0 \ "Backup root.:" 4 1 "/" 4 15 30 0 \ "Weeks.......:" 5 1 "0" 5 15 2 0 \ "Months......:" 6 1 "0" 6 15 2 0 \ "MySQL dumps.:" 7 1 "$mysqldumps" 7 15 1 0 \ "SQL Dir.....:" 8 1 "/var/sqlbackups/" 8 15 30 0 \ "Cron (HH)...:" 9 1 "$hour" 9 15 2 0 \ "Cron (MM)...:" 10 1 "$minute" 10 15 2 0 \ "Logging.....:" 11 1 "Y" 11 15 1 0 \ "Email log...:" 12 1 "N" 12 15 1 0 \ "Emailaddress:" 13 1 "" 13 15 30 0 2> /tmp/$pid-options escaper choice=$? array=( `cat /tmp/$pid-options `) if [ -f /tmp/$pid-options ]; then rm /tmp/$pid-options > /dev/null 2> /dev/null fi while ! [ ${#array[@]} = 13 ] do dialog --backtitle "$backtitle" --title "$title" --msgbox "\nNot all fields are populated!\n\nPlease make sure you fill in all the fields." 10 50; clear genhour genminute dialog --backtitle "$backtitle" --title "$title" --keep-window --form "\nYour Backup Account Details\n" 20 60 0 \ "Username....:" 1 1 "" 1 15 14 0 \ "Password....:" 2 1 "" 2 15 14 0 \ "Server......:" 3 1 "" 3 15 30 0 \ "Backup root.:" 4 1 "$defaultbackuppath" 4 15 30 0 \ "Weeks.......:" 5 1 "0" 5 15 2 0 \ "Months......:" 6 1 "0" 6 15 2 0 \ "MySQL dumps.:" 7 1 "$mysqldumps" 7 15 1 0 \ "SQL Dir.....:" 8 1 "/var/sqlbackups/" 8 15 30 0 \ "Cron (HH)...:" 9 1 "$hour" 9 15 2 0 \ "Cron (MM)...:" 10 1 "$minute" 10 15 2 0 \ "Logging.....:" 11 1 "Y" 11 15 1 0 \ "Email log...:" 12 1 "N" 12 15 1 0 \ "Emailaddress:" 13 1 "" 13 15 30 0 2> /tmp/$pid-options escaper choice=$? array=( `cat /tmp/$pid-options `) if [ -f /tmp/$pid-options ]; then rm /tmp/$pid-options > /dev/null 2> /dev/null fi done fi
As you can see, it's showing a message if the array is not completely filled. I want that window on top of the original box, so if a user selects OK, it returns to the original window, keeping the fields with their input.
As stated before, it's not the complete code, but enough to run. Should you need more, let me know. And indeed, the manpage on dialog is very limited...
0 -
Before getting into your problem, I'll make a couple of suggestions.
Since you are using bash ((#!/bin/bash):
1 - Use [[ (builtin) instead of [ (external test/[ command). [[ is safer,faster and has more options than test/[
2 - Don't use `` for commands, as it is deprecated. Use $() instead (it's easier to nest commands, better readability, you can use "",etc)
3 - Try not to insert external commands into variables ( array=( ` cat /tmp/$pid-option `) ). Better use something like:while read -r line do echo "$line" done < "$file"
4 - "pid=$(echo $$)" ?? Why not just "pid=$$"? ( This could go in the point 3 )
Now, to your problem:
You have the options that the user chose in the /tmp/$pid-options file (or in the array variable) , why don't you use that info to fill the blanks on the call to the dialog? I mean, if your user, for example, just introduced the "Username" field that data can be used to fill the first spot in your dialog:"Username....:" 1 1 "${array[0]}" 1 15 14 0
Gosshhh I love scripting
0
Categories
- 9.1K All Categories
- 15 LFX Mentorship
- 68 LFX Mentorship: Linux Kernel
- 382 Linux Foundation Boot Camps
- 234 Cloud Engineer Boot Camp
- 76 Advanced Cloud Engineer Boot Camp
- 30 DevOps Engineer Boot Camp
- 9 Cloud Native Developer Boot Camp
- 983 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 106 LFD103 Class Forum
- 6 LFD121 Class Forum
- 56 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 450 LFD259 Class Forum
- 90 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 715 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 283 LFS211 Class Forum
- 51 LFS216 Class Forum
- 27 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 12 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 113 LFS253 Class Forum
- 814 LFS258 Class Forum
- 8 LFS258-JP クラス フォーラム
- 54 LFS260 Class Forum
- 81 LFS261 Class Forum
- 18 LFS262 Class Forum
- 76 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 10 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 183 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 191 LFW211 Class Forum
- 114 LFW212 Class Forum
- 880 Hardware
- 207 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 205 Networking
- 98 Printers & Scanners
- 82 Storage
- 730 Linux Distributions
- 85 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 127 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 349 Ubuntu
- 450 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 105 System Management
- 45 Web Management
- 51 Mobile Computing
- 19 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 501 Off Topic
- 121 Introductions
- 193 Small Talk
- 19 Study Material
- 756 Programming and Development
- 243 Kernel Development
- 479 Software Development
- 903 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 73 Games
- 314 Installation
- 26 All In Program
- 26 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)