- This topic has 25 replies, 7 voices, and was last updated Mar 19-7:33 pm by olsztyn.
-
Posts
-
RJP
Volume indicator works fine if it placed $HOME folder. Indicador does not work other locations. Maybe the script should edit like
touch /tmp/volume.txt echo '0' > /tmp/volume.txt [[ $(cat /tmp/volume.txt) -eq 1 ]] && exit 0… so that it works from other locations too?
- This reply was modified 1 month, 3 weeks ago by RJP.
Lead Farmer
I have to admit I did not previously paid attention to this thread since I am not typically using IceWM. However I just flipped over to IceWM and installed this volume indicator for testing/evaluation purpose.
Having just tested I have to say that it works very nicely. I do like it the way it works. When the time allows I will also test under JWM, reformatting the keys syntax of course, but it should work as well.
Just to mention, on antiX 23, where I am testing, IceWM Settings to edit are no longer in the Control Center. So, instead the key file in ./icewm folder must be edited for mapping of keys.Thanks Lead Farmer! Very nice…
Thanks for the feedback.
Interesting decision moving IceWM keys from the setting in Control Center, I hope the Devs will add a easy to accesses it instead of opening a file in a hidden folder.
olsztyn
Interesting decision moving IceWM keys from the setting in Control Center, I hope the Devs will add a easy to accesses it instead of opening a file in a hidden folder.
In my understanding this was actually to move various IceWM options to a dedicated to IceWM app, where you pick options you want via buttons instead of manually editing IceWM config file. This IceWM config screen is mostly the entire collection of IceWM tweaks developed by PPC and BobC.
There is a sub-app to add/delete IceWM keys, where the keys you need for this volume control can be added. These on-screen config controls are actually easier to use than the traditional IceWM settings was in Control Center.As I mentioned before I do not typically use IceWM anymore but I still have it installed for testing.
Your Volume control caan be also easily installed under JWM, which was my main WM until relatively recently.- This reply was modified 1 month, 3 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersVolume indicator works fine if it placed $HOME folder. Indicador does not work other locations. Maybe the script should edit like
touch /tmp/volume.txt echo '0' > /tmp/volume.txt [[ $(cat /tmp/volume.txt) -eq 1 ]] && exit 0… so that it works from other locations too?
It will not work that way. you need a separate file to store the value if volume indicator in running or not, with 0 not running as the default value, and 1 mean it’s running, by knowing the status I can exit script if the hotkey is pressed for the second time and not show the volume indicator again, turning it on or off with the same keys.
You can add the file in the startup but I think it defy purpose, and also the images of the speaker and headphone using the same path.
- This reply was modified 1 month, 3 weeks ago by Lead Farmer.
- This reply was modified 1 month, 3 weeks ago by Lead Farmer.
Volume indicator works fine if it placed $HOME folder. Indicador does not work other locations. Maybe the script should edit like
touch /tmp/volume.txt echo '0' > /tmp/volume.txt [[ $(cat /tmp/volume.txt) -eq 1 ]] && exit 0… so that it works from other locations too?
It will not work that way. you need a separate file to store the value if volume indicator in running or not, with 0 not running as the default value, and 1 mean it’s running, by knowing the status I can exit script if the hotkey is pressed for the second time and not show the volume indicator again, turning it on or off with the same keys.
You can add the file in the startup but I think it defy purpose, and also the images of the speaker and headphone using the same path.
Really?
Attachments:
@RJP English is not my first language, so it’s hard to me explain why volume.txt should be a separate file, and not be created from the script, I recommend you use the original script.
- This reply was modified 1 month, 3 weeks ago by Lead Farmer.
@RJP English is not my first language, so it’s hard to me explain why volume.txt should be a separate file, and not be created from the script, I recommend you use the original script.
I do not speak english, but I tried to say that if volume.txt is into /tmp, the script can be launched other locations than $HOME/volume_indicator too. Your script is working fine.
- This reply was modified 1 month, 3 weeks ago by RJP.
ile
There is a sub-app to add/delete IceWM keys, where the keys you need for this volume control can be added. These on-screen config controls are actually easier to use than the traditional IceWM settings was in Control Center.
I looked it up, it’s the Add Key app, it’s looks ok (except it’s width is twice my screen width), but I prefer to edit the text file myself.
I looked in the control center script and saved the “Edit IceWM Setting” command in case I will want to make a menu shortcut in the future.geany $HOME/.icewm/winoptions $HOME/.icewm/preferences $HOME/.icewm/keys $HOME/.icewm/startup $HOME/.icewm/toolbar $HOME/.icewm/menu &- This reply was modified 1 month, 2 weeks ago by Lead Farmer.
- This reply was modified 1 month, 2 weeks ago by Lead Farmer.
Brian Masinick
Menu –> System –> Control Centre, then select Edit IceWM settings does exactly the same thing – it starts up the default IDE editor, Geany with the same configuration files.
Your way is fine; those who prefer the graphical interface can access it through the Control Centre.
--
Brian MasinickMenu –> System –> Control Centre, then select Edit IceWM settings does exactly the same thing – it starts up the default IDE editor, Geany with the same configuration files.
Not in antiX 23 though. IceWM settings is gone from Control Center in antiX 23. By design.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
