1

Topic: using FN-Hotkeys for Changing Sound-Volume

Hello all,

I have some trouble with the Volume-Up and Volume-Down Shortcuts of my Notebooks. In Windows I have to use FN+F3 (Volume-down) and Fn+F4 (Volume-Up). This is currently - when I have Litestep-shell activated - not possible.

After searching the internet I did the following extensions to my Litestep:

personal.rc:
*LoadModule C:\Litestep\modules\pcp_vol.dll     
jKeyUseHotkeyDef

hotkey.rc:
*Hotkey Win+Shift Y !Volume_Up
*Hotkey Win+Shift X !Volume_Down
I only used the combination Win+Shift Y and X for testing if it works.

vk104.txt (for j-key):
Volume_Up, AE
Volume_down, AF

By running this configuration I get no Errors, but also it doesn´t work.

So,
1. what do I have to do for getting it working?
2. how can i get it working, so I can use the FN+F3 and FN+F4 Shortcuts?

Many thanks.

Adleano

2

Re: using FN-Hotkeys for Changing Sound-Volume

I have in my step.rc:

    LoadModule $ModulesDir$tVolEzy.dll
    tVolEzyUnmuteOnVolDown false
    tVolEzyUnmuteOnVolUp true
    tVolEzyVolumeChangedCommand "!CommandSetText New Volume: #VOLUME#"
    tVolEzyMuteChangedCommand "!CommandSetText Mute Changed: #MUTE#"
    *Hotkey .none VOL_UP !tVolEzyUp 7
    *Hotkey .none VOL_DOWN !tVolEzyDown 7
    *Hotkey .none VOL_MUTE !tVolEzyToggleMute

and in vk104.txt

VOL_DOWN , AE
VOL_UP , AF
VOL_MUTE , AD

This works for me on my laptop with WinXP. You probably want to *NetLoadModule tVolEzy instead of loading it like I do...

3

Re: using FN-Hotkeys for Changing Sound-Volume

Hello Tobbe,

thanks for your help.
I implemented your suggestion in my Litestep-Theme.

I have still a problem with this part:

  *Hotkey .none VOL_UP !tVolEzyUp 7
   *Hotkey .none VOL_DOWN !tVolEzyDown 7
   *Hotkey .none VOL_MUTE !tVolEzyToggleMute

I put this in my File "hotkey.rc", because I need some other Hotkeys, too.
Hope that it´s right ;-)

Here I get the following Error:
Headline: jKey
Message: Invalid <hotkey> - "VOL_UP"
Error in definition:
*Hotkey .none VOLUP !tVolEzyUp 7

The Entries in the file vk104.txt are the same as called:
VOLDOWN , AE
VOLUP , AF
VOLMUTE , AD

Is that right, that the name "VOLUP" in the *Hotkey-line have to be the same as in the vk104.txt?

The implementation-call for the module VolEzy.dll is in the theme.rc and the step.rc (might be done double?). I load it local, cause I downloaded it and copied to the modules-folder.

Do you or somebody have an idea what is wrong?

Many thanks.

4

Re: using FN-Hotkeys for Changing Sound-Volume

maybe you want to edit vk104.txt like this:
VOL_UP , AF
VOL_DOWN , AE
VOL_MUTE , AD

i prefer dont edit "main LiteStep files" like step.rc or hotkey.rc.
Theme makers can securely to do your changes on theme.rc.
i'm sorry by my bad english.

5

Re: using FN-Hotkeys for Changing Sound-Volume

DiamondXplosion is right. The name in vk104.txt and in the *Hotkey definition must match exactly. Either change it to "VOLUP" etc in both places or "VOL_UP" etc in both places. You can not mix with/without the underscore. Also, you said you loaded "VolEzy.dll". The module name is actually "tVolEzy.dll", notice the "t" in the beginning. Make sure you got your LoadModule line correct.

6

Re: using FN-Hotkeys for Changing Sound-Volume

I think you do not need to change the file vk104.txt (as I've said before). just add these lines to theme.rc:

*Hotkey .none 0xAF !tVolEzyUp 1
*Hotkey .none 0xAE !tVolEzyDown 1
*Hotkey .none 0xAD !tVolEzyToggleMute

My main worry is that we, the creators of the theme, we lose the features we put into the core files of LiteStep, when the theme that we share with other users LiteStep or even re-installed LiteStep (OMAR, or Losi). So we would need to constantly change these core files. Putting the settings in the theme files would remain saved settings in any environment LiteStep, both theme creator and the end user.

7

Re: using FN-Hotkeys for Changing Sound-Volume

DiamondXplosion wrote:

I think you do not need to change the file vk104.txt (as I've said before). just add these lines to theme.rc:

*Hotkey .none 0xAF !tVolEzyUp 1
*Hotkey .none 0xAE !tVolEzyDown 1
*Hotkey .none 0xAD !tVolEzyToggleMute

My main worry is that we, the creators of the theme, we lose the features we put into the core files of LiteStep, when the theme that we share with other users LiteStep or even re-installed LiteStep (OMAR, or Losi). So we would need to constantly change these core files. Putting the settings in the theme files would remain saved settings in any environment LiteStep, both theme creator and the end user.

In all honesty, one shouldn't distribute themes with hotkeys defined in them. Your preference for a hotkey might not mesh with another's preference.

If you really really want hotkeys in your theme, at the very least leave them commented, with an explanation given that the user can enable and/or the hotkey if they want.

8

Re: using FN-Hotkeys for Changing Sound-Volume

I agree with you the-golem. I'm just trying to follow the use of OTS.
I'm preparing my theme with what you have mentioned. some resources becomes disabled by default (unlike commented, I set to "false"), and the user can enable them by !bang command (I use xpopup + xlabel + xtextedit + xstatsclass to change options).
for example:

1 - enable thumbnails in xtaskbar-2.3.4 (on WinXP does not work)
2 - language (if available all like to use your own language if not English)
3 - keyboard shortcuts (as quoted in your post).

about LiteStep themes sharing, LiteStep users are getting with few options, or become creators of themes (which takes too long time. it took me three years to make a decent theme), or use themes that have less features than the interface standard win7-macosx-linux (besides the old modules that do not always work with stable LiteStep version, like lswchanger-1.2). many of them return to the default shell for winxp / 7 because it is more functional, and the advantage of not needing to become an expert user in LiteStep. Currently users need good LiteStep themes and share them is the best way to keep alive LiteStep. I hope to help with what I can.

9

Re: using FN-Hotkeys for Changing Sound-Volume

DiamondXplosion wrote:

I think you do not need to change the file vk104.txt (as I've said before). just add these lines to theme.rc:

*Hotkey .none 0xAF !tVolEzyUp 1
*Hotkey .none 0xAE !tVolEzyDown 1
*Hotkey .none 0xAD !tVolEzyToggleMute

@Adleano: You really do not need to change the file vk104.txt if you add the above lines. just choose where to put the settings: hotkey.rc or theme.rc. but keep in mind that you need to reconfigure the file hotkey.rc each time you re-install LiteStep.
remember:
".none 0xAD" = FN+MUTE_KEY
".none 0xAE" = FN+DOWN
".none 0xAF" = FN+UP

10

Re: using FN-Hotkeys for Changing Sound-Volume

Hello all,

thanks for all the answers. I still get an error with this configuration:

error-Message:
title: jKey
text: Invalid <hotkey> - "0xAF"
        Error in definition:
        *Hotkey.none 0XAF !tVolEzyUp 1

I get the same error-Message with 0XAD and 0XAE

Here my current configuration:

theme.rc:
Added lines:
LoadModule    "C:\Litestep\modules\tVolEzy.dll"
;Audiosteuerung Getac aktivieren
LoadModule $ModulesDir$tVolEzy.dll
tVolEzyUnmuteOnVolDown false
tVolEzyUnmuteOnVolUp true
tVolEzyVolumeChangedCommand "!CommandSetText New Volume: #VOLUME#"
tVolEzyMuteChangedCommand "!CommandSetText Mute Changed: #MUTE#"

here the complete theme.rc
OTSMajorVersion 2
OTSMinorVersion 0

ThemeName    "Dybe"
ThemeAuthor    "ICS - Matthias Schöchle"
; geaendert von Christian Barthelmes am 16.04.2009
;geändert von Marc Zuckschwerdt am 17.11.2011

; System______________________________________________

ConfigDir       "$ThemeDir$Config\"
LSImageFolder     "$ThemeDir$images\"
MiscDir         "$ThemeDir$misc\"

; Modules_____________________________________________

NetLoadModuleOnLoad !NetUnloadModule
NetLoadModuleOnFail "Cannot get all modules"

*NetLoadModule  taskbar3-0.305
;*NetLoadModule    systray2kad.dll
LoadModule    "C:\Litestep\modules\tVolEzy.dll"
*NetLoadModule  jdesk-0.73
*NetLoadModule    hotkey.dll
*NetLoadModule  tVolEzy.dll
*NetLoadModule    shortcut2.dll
*NetLoadModule    label-1.99
*NetLoadModule    syscolor-2.3

;Wallpaper
include "$ThemeDir$wallpaper.bmp"

tVolEzyUnmuteOnVolDown false
tVolEzyUnmuteOnVolUp true
tVolEzyVolumeChangedCommand "!CommandSetText New Volume: #VOLUME#"
tVolEzyMuteChangedCommand "!CommandSetText Mute Changed: #MUTE#"

; JDESK _______________________________________________

jDeskWorkArea            "0,0,0,-24"

; Taskbar3 ____________________________________________

TaskbarPositioning
TaskBarX         222
TaskBarY        -20
TaskbarHeight        20
TaskbarWidth        508
TaskbarMaxTaskWidth    515
TaskbarStartButton    false
TaskbarBorder        0
TaskBarSpacing        0
TaskbarNormalFontFace        "Verdana"
TaskbarActiveFontFace        "Verdana"
TaskbarMinimizedFontFace    "Verdana"
TaskbarNormalFontHeight        16
TaskbarActiveFontHeight        16
TaskbarMinimizedFontHeight    16
TaskbarActiveFontColor         101010
TaskbarMinimizedFontColor     505050
TaskbarNormalFontColor        000000
TaskbarSkinCenter        taskbar.png
TaskbarNormalSkinCenter        tasknormcenter.png
TaskbarNormalSkinLeft        tasknormleft.png
TaskbarNormalSkinRight        tasknormright.png
TaskbarActiveSkinCenter        taskselcenter.png
TaskbarActiveSkinLeft        taskselleft.png
TaskbarActiveSkinRight        taskselright.png
TaskbarMinimizedSkinCenter    tasknormcenter.png
TaskbarMinimizedSkinLeft    tasknormleft.png
TaskbarMinimizedSkinRight    tasknormright.png
TaskBarRButtonDown    !PopupTaskbar
TaskBarMButtonDown    !PopupSpecial
TaskButtonFlash        False
TaskBarTButtonM        .ontop
TaskBarTButtonL        .select
TaskBarTButtonR        .menu
TaskbarLines        1
TaskBarRefresh        100
TaskbarNoFontShift        true
Taskbarnoskinshift        true
TaskbarButtonFontBorder 19 4 2 1
TaskbarButtonBorder 1
TaskBarIconSize 12
TaskBarIconY 2
TaskbarIconX 3
TaskbarDisableFlashing
TaskbarRefresh 500
TaskbarUseFontShadow false

*TaskbarNoFlash        IEFrame
*TaskbarNoFlash        Commander
*TaskbarNoFlash        #32770

; Shortcuts_____________________________________________

; Stand Schoechle
;*Shortcut "" 400 200 Dybe.bmp DybeOver.bmp DybeDown.bmp "C:\litestep\update.bat"
;*Shortcut "" 400 300 restart.bmp restartover.bmp restartdown.bmp "C:\litestep\shutdown.bat"
;*Shortcut "" 400 400 Pruf.bmp PrufOver.bmp PrufDown.bmp "C:\programme\dybe2\prüfvorschriften.pdf"

; Aenderung Marc Zuckschwerdt 16.11.2011
*Shortcut "" 50  50 button1.bmp button1Over.bmp button1Down.bmp "C:\litestep\Start_1.exe"
*Shortcut "" 260 60 US_weiss.bmp US_normal.bmp US_aktiv.bmp "C:\litestep\Ch_language_de_en.bat"
*Shortcut "" 260 125 Deutsch_weiss.bmp Deutsch_normal.bmp Deutsch_aktiv.bmp "C:\litestep\Ch_language_en_de.bat"
*Shortcut "" 390 50 button2.bmp button2Over.bmp button2down.bmp "C:\litestep\Start_2.bat"


;    *Shortcut "" 59 -24 .none .none .none [!shutdown]

*Shortcut ""  0 -20    bar.png .none .none

;Audiosteuerung Getac aktivieren_________________________________________________
LoadModule $ModulesDir$tVolEzy.dll
tVolEzyUnmuteOnVolDown false
tVolEzyUnmuteOnVolUp true
tVolEzyVolumeChangedCommand "!CommandSetText New Volume: #VOLUME#"
tVolEzyMuteChangedCommand "!CommandSetText Mute Changed: #MUTE#"

; Label_________________________________________________

Labels TimeLabel, date

TimeLabelHeight  20
TimeLabelWidth      60
TimeLabelX         0
TimeLabelY         -20
TimeLabelFont        "Verdana"
;TimelabelFontBold
TimeLabelFontColor            303030
TimeLabelFontHeight            18
TimeLabelLeftBorder            3
TimeLabelTopBorder            1
;TimeLabelFontShadow
TimeLabelFontShadowColor    909090
TimeLabelFontShadowX         1
TimeLabelFontShadowY         1
TimeLabelJustify            center
;TimeLabelImage                time.png
TimeLabelText                "[time('ii:nn')]"

dateHeight    20
dateWidth     160
dateX         61
dateY         -20
;dateFont             "lucida grande"
dateFont             "Verdana"
dateFontColor         000000
;DateFontShadow
DateFontShadowColor    24394D
DateFontShadowX     1
DateFontcShadowY     1
dateFontHeight         18
dateBottomBorder     0
dateJustify         center
;dateImage         date.png
dateText         "[date('ddd, d mmm yyyy')]"

I also tried to set up the addings in the hotkey.rc and the step.rc, but I got the same error-Message as well. The tVolEzy.dll is in the modules-folder and the path is right.

What did i do wrong?
Many thanks.

11

Re: using FN-Hotkeys for Changing Sound-Volume

open run box (WIN+R) and paste this:

"C:\LiteStep\litestep.exe !about"

or open !popup choose "LiteStep" then "About LiteStep"
choose in the list "Loaded Modules" and find "jkey" or post here as a screenshot if you prefer.

i want make sure a thing. we all ars talking about jkey but i think that you uses jkey (default by LS) and Hotkey module:
if you already uses jkey, you can comment this line and maybe after, erase.

*NetLoadModule    hotkey.dll ; comment this line

and take care with spaces: *Hotkey .none 0XAF !tVolEzyUp 1

Invalid <hotkey> - "0xAF"
        Error in definition:
        *Hotkey.none 0XAF !tVolEzyUp 1 ; this definition is wrong

12

Re: using FN-Hotkeys for Changing Sound-Volume

Thanks for the answer, DiamondXplosion

I did what you told me and found out, that jkey 0.37 (jugg/hollow) was in the loaded module list.
I updated it to version 0.39 and loaded the module in the theme.rc

Now I get no errors by using the hotkeys. Volume up and volume down are both working (I did the implementation of the hotkeys in hotkey.rc):

Only the mute-key doesn´t work. I get no Error-Message)

Entry in hotkey.rc:
*Hotkey .none 0xAD !tVolEzyToggleMute

The keycode with AD is the right one (I tested this with a scankey-tool). Do sombebody know any problems by using this bangCommand?

13

Re: using FN-Hotkeys for Changing Sound-Volume

Adleano wrote:

I updated it to version 0.39 and loaded the module in the theme.rc

1 - loaded it on theme.rc? erease it from theme.rc and open C:\LiteStep\personal\personal.rc find jkey. it must have some line like this:

*NetLoadModule    jkey-0.37

change it to:

*NetLoadModule    jkey-0.39

2 - why do you use LoadModule and "NetLoadModule" at the same time? you must choose one of two to load its modules. Module loading section must be like this:

; Modules_____________________________________________

*NetLoadModule taskbar3-0.305
*NetLoadModule jdesk-0.73
*NetLoadModule tVolEzy-2.0
*NetLoadModule shortcut2
*NetLoadModule label-1.99
*NetLoadModule syscolor-2.3

NetLoadModuleOnLoad !execute [!NetUnloadModule .]
NetLoadModuleOnFail !alert "Cannot get all modules" "LiteStep"

or like this:

; Modules_____________________________________________

LoadModule "$ModulesDir$taskbar3-0.305.dll"
LoadModule "$ModulesDir$jdesk-0.73.dll"
LoadModule "$ModulesDir$tVolEzy-2.0.dll"
LoadModule "$ModulesDir$shortcut2.dll"
LoadModule "$ModulesDir$label-1.99.dll"
LoadModule "$ModulesDir$syscolor-2.3.dll"

3 - Make a backup of the file vk104.txt (copy and replace .txt with .old at the end), and comment any line included for you to file vk104.txt
4 - Make some code clean-up on theme.rc. it has some lines repeated
5 - Post here your OS version and LiteStep version too (run "C:\Litestep\litestep.exe !about")

14

Re: using FN-Hotkeys for Changing Sound-Volume

hi guys,

I am trying to mute my volume when litestep starts and set it to 10%. I can get this to work in mzscript with umslider but not with tvolezy. Do you have any idea why it does not?

*script start !tVolEzyToggleMute     <--- just doesn't work

thank you

15

Re: using FN-Hotkeys for Changing Sound-Volume

Is the script bang executing before volume module is loaded?  Check load order would be my best guess.

16

Re: using FN-Hotkeys for Changing Sound-Volume

newman wrote:

I am trying to mute my volume when litestep starts and set it to 10%.

Have you tried this?

NetLoadModuleOnLoad !execute [!tVolEzyToggleMute][!tVolEzyDown 100][!tVolEzyUp 10]

I'm assuming you're using tVolEzy-2.0 on Windows7

17

Re: using FN-Hotkeys for Changing Sound-Volume

hi guys, sorry for the late reply

xcal: you were right, my dll load order was off. I couldn't believe that I did not think of it

DiamondXplosion: I figured that one out but I put the bangs in my mzscript when it starts. Same idea as yours, first un-mute the volume then toggle it to mute it.

*script start !execute [!tVolEzyDown 100] [!tVolEzyUp 11]
*script start !execute [!tVolEzyToggleMute]


Thank you xcal and DiamondXplosion

18

Re: using FN-Hotkeys for Changing Sound-Volume

newman wrote:

xcal: you were right, my dll load order was off. I couldn't believe that I did not think of it

No problem, glad you got it going.  smile