Skip to content
fzambroniPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

WeekDay

WeekDay is a lightweight Windows tray utility for meeting hotkeys. It shows the current weekday as a tray icon and turns configurable keyboard buttons, such as mute/unmute and camera on/off, into the correct shortcut for the active meeting app.

It was designed for setups where different keyboards send different key combinations, and where the same physical mute or camera key needs to work reliably across apps like Microsoft Teams, Zoom, Google Meet, Webex, Skype/Lync, Slack Huddles, or a custom meeting tool.

WeekDay visual identity


What WeekDay does

WeekDay listens for configurable hotkeys and, when one is pressed, it tries to find an actual meeting window before sending any command. This avoids the classic problem where a mute shortcut is sent to the wrong app, browser tab, chat window, or document.

Main capabilities:

  • Shows a dynamic weekday icon in the Windows system tray.
  • Supports separate keyboard profiles, such as Home and Office.
  • Detects mute/unmute and camera on/off key combinations.
  • Finds the current meeting app window before sending commands.
  • Activates/focuses the meeting window before sending the shortcut.
  • Supports multiple meeting apps through Settings.ini.
  • Allows different shortcuts per app.
  • Includes a Key Inspector to discover what a keyboard is actually sending.
  • Prevents accidental double toggles when the keyboard already sends the app-native shortcut.
  • Includes startup install/uninstall from the tray menu.
  • Extracts embedded runtime files automatically when the compiled app runs.
  • Extracts Help.html only when the Help menu is opened.
  • Writes local logs for troubleshooting.

Supported meeting apps

WeekDay includes default configuration templates for:

  • Microsoft Teams
  • Zoom
  • Google Meet
  • Cisco Webex
  • Skype / Lync
  • Slack Huddles
  • Custom meeting app profile

The app list is fully configurable in Settings.ini, so additional tools can be added without changing the AutoIt source code.

WeekDay is not affiliated with Microsoft, Zoom, Google, Cisco, Slack, or Skype. Product names and logos belong to their respective owners.


How it works

When you press a configured keyboard shortcut, WeekDay follows this flow:

  1. Detects whether the pressed key combination matches the active profile.
  2. Looks for a supported meeting window.
  3. Prioritizes the currently active meeting window when configured to do so.
  4. Activates/restores the meeting window.
  5. Waits briefly to confirm the window is focused.
  6. Sends the configured mute or camera shortcut for that specific app.
  7. Optionally restores the previous active window.
  8. Logs the result locally.

This behavior is controlled by the General, Profile.*, Apps, and App.* sections in Settings.ini.


Requirements

For running the compiled app:

  • Windows 10 or Windows 11
  • A writable folder for runtime extraction, logs, settings, and help files
  • Meeting apps installed or available in browser windows

For building from source:

  • AutoIt v3
  • SciTE4AutoIt3 or AutoItWrapper / Aut2Exe
  • The project files listed in the repository structure below

Recommended folder structure

A clean source folder can look like this:

.\WeekDay
├─ WeekDay.au3
├─ Settings.ini
├─ Help.html
├─ Splash.jpg
├─ Week.ico
├─ Install.ico
├─ 1.ico
├─ 2.ico
├─ 3.ico
├─ 4.ico
├─ 5.ico
├─ 6.ico
├─ 7.ico
├─ Updater_lib.au3
├─ Updater.exe
├─ FileUpdate.exe
└─ README.md

At runtime, the compiled executable creates and/or refreshes files next to the app, for example:

.\WeekDay
├─ WeekDay.exe
├─ Settings.ini
├─ settings.default.ini
├─ Help.html              # extracted when Help is opened
├─ Assets
│  ├─ Splash.jpg          # extracted when Help is opened
│  └─ Icons
│     ├─ 1.ico
│     ├─ 2.ico
│     ├─ 3.ico
│     ├─ 4.ico
│     ├─ 5.ico
│     ├─ 6.ico
│     └─ 7.ico
└─ Logs
   └─ WeekDay.log

Settings.ini is created automatically if it does not exist. Once created, it is not overwritten on every run, so user changes are preserved.

settings.default.ini is refreshed from the embedded default file and can be used as a clean reference.


Running the app

From a release build

  1. Download the latest release package.
  2. Extract it to a writable folder, for example:
.\WeekDay
  1. Run WeekDay.exe.
  2. Right-click the tray icon to open the menu.
  3. Open Settings.ini and adjust profiles or meeting apps as needed.
  4. Use Reload settings from the tray menu after editing the file.

From source

  1. Clone or download the repository.
  2. Open WeekDay.au3 in SciTE4AutoIt3.
  3. Make sure all FileInstall() source files exist in the project folder.
  4. Run the script directly for development testing.
  5. Compile it with AutoItWrapper / Aut2Exe.

When testing directly as .au3, some embedded-file behavior may differ from the compiled .exe, because FileInstall() is primarily intended for compiled AutoIt executables.


Tray menu

Right-click the WeekDay tray icon to access:

Menu item Description
Open Settings.ini Opens the active configuration file.
Reload settings Reloads configuration without restarting the app.
Profile Switches between configured keyboard profiles.
Pause hotkeys Temporarily disables hotkey handling.
Test audio toggle Sends the configured audio command to the detected meeting app.
Test camera toggle Sends the configured video command to the detected meeting app.
Key Inspector - 10 seconds Detects pressed keys and copies the result to the clipboard.
Install startup shortcut Adds WeekDay to Windows startup.
Remove startup shortcut Removes WeekDay from Windows startup.
Open app folder Opens the folder where the app is running.
Open log Opens the local log file.
Help Extracts and opens Help.html.
Exit Closes WeekDay.

Configuration overview

WeekDay is configured through Settings.ini.

The default configuration is organized into these main areas:

[General]
[Profile.Home]
[Profile.Office]
[Apps]
[App.TeamsNew]
[App.Zoom]
[App.GoogleMeet]
[App.Webex]
[App.SkypeLync]
[App.SlackHuddle]
[App.Custom1]

General settings

Example:

[General]
ActiveProfile=Home
Profiles=Home,Office
PollMs=35
DebounceMs=650
ActivateMeetingWindow=1
RequireMeetingWindow=1
ActivationRetries=3
ActivationVerifyMs=800
RestorePreviousWindowAfterSend=0
UseActiveWindowFirst=1
ShowTrayTips=1
LogEnabled=1
StartPaused=0
SkipSendWhenInputAlreadyMatchesTarget=1
Setting Description
ActiveProfile The keyboard profile currently in use.
Profiles Comma-separated list of available profiles.
PollMs How often WeekDay checks for configured key combinations. Lower values feel faster but use slightly more CPU.
DebounceMs Prevents repeated triggers when a key is held down.
ActivateMeetingWindow If 1, WeekDay focuses the meeting window before sending a command.
RequireMeetingWindow If 1, WeekDay will not send a shortcut unless a supported meeting window is found.
ActivationRetries Number of attempts to activate the meeting window.
ActivationVerifyMs Time allowed for the target window to become active.
RestorePreviousWindowAfterSend If 1, WeekDay returns focus to the previously active window after sending the shortcut.
UseActiveWindowFirst If 1, the currently active meeting window has priority over other detected apps.
ShowTrayTips Enables or disables tray notifications.
LogEnabled Enables or disables local logging.
StartPaused Starts WeekDay with hotkeys paused.
SkipSendWhenInputAlreadyMatchesTarget Prevents double toggles when the physical keyboard already sends the same shortcut expected by the active app.

Keyboard profiles

Profiles let you use different keyboards or environments without editing the app.

Example:

[Profile.Home]
MuteHotkeys=SHIFT+WIN+A|ALT+A
CameraHotkeys=SHIFT+WIN+V|ALT+V

[Profile.Office]
MuteHotkeys=CTRL+ALT+A|ALT+A
CameraHotkeys=CTRL+ALT+V|ALT+V

Multiple input combinations can be separated with |.

For example:

MuteHotkeys=SHIFT+WIN+A|ALT+A|VOLUME_MUTE

This means any of the listed combinations can trigger the audio toggle.


Key names for input detection

WeekDay can detect common virtual keys, including:

CTRL, SHIFT, ALT, WIN
A-Z, 0-9
F1-F24
SPACE, ENTER, ESC, TAB
INSERT, DELETE, HOME, END
PGUP, PGDN
LEFT, RIGHT, UP, DOWN
VOLUME_MUTE, VOLUME_DOWN, VOLUME_UP
MEDIA_PLAY_PAUSE, MEDIA_STOP, MEDIA_NEXT, MEDIA_PREV
LAUNCH_APP1, LAUNCH_APP2

You can also use raw virtual-key hex codes, for example:

MuteHotkeys=AD

AD is the Windows virtual-key code for volume mute.


Key Inspector

The Key Inspector is useful when a keyboard has special mute/camera keys and you do not know what they send.

To use it:

  1. Right-click the tray icon.
  2. Click Key Inspector - 10 seconds.
  3. Press the keyboard mute or camera key.
  4. Wait for the inspector to finish.
  5. The detected combination is copied to the clipboard.
  6. Paste it into MuteHotkeys or CameraHotkeys.
  7. Save Settings.ini.
  8. Click Reload settings.

If nothing is detected, the keyboard may be sending a proprietary HID command that is not exposed as a standard Windows virtual key.


Meeting app configuration

The [Apps] section controls app priority.

Example:

[Apps]
Order=TeamsNew,Zoom,GoogleMeet,Webex,SkypeLync,SlackHuddle,Custom1

WeekDay checks apps in this order unless the active window already matches a supported app and UseActiveWindowFirst=1.

Each app has its own section.

Example:

[App.TeamsNew]
Enabled=1
Name=Microsoft Teams
MeetingWindow=[REGEXPTITLE:(?i).*((Teams Meeting)|(Meeting.*Microsoft Teams)|(Microsoft Teams.*Meeting)|(Call.*Microsoft Teams)|(Microsoft Teams.*Call)).*]
Window=[REGEXPTITLE:(?i).*((Teams Meeting)|(Meeting.*Microsoft Teams)|(Microsoft Teams.*Meeting)|(Call.*Microsoft Teams)|(Microsoft Teams.*Call)).*]
Focus=
CloseWindow=
PreSend=
AudioSend=^+m
VideoSend=^+o
PostSend=
ActivationDelayMs=150
Setting Description
Enabled Enables or disables this app profile.
Name Friendly name shown in notifications and logs.
MeetingWindow Window selector used to find the actual meeting/call window.
Window Legacy fallback selector. Kept for compatibility.
Focus Optional alternate selector used when a specific app needs a different focus target.
CloseWindow Optional selector for popups that should be dismissed before sending a command.
PreSend Optional command sent before the main shortcut.
AudioSend AutoIt Send() syntax for mute/unmute.
VideoSend AutoIt Send() syntax for camera on/off.
PostSend Optional command sent after the main shortcut.
ActivationDelayMs Short delay after focusing the window before sending the shortcut.

AutoIt Send syntax

Meeting app shortcuts use AutoIt Send() syntax.

Common modifier symbols:

Symbol Key
^ Ctrl
+ Shift
! Alt
# Windows key

Examples:

AudioSend=^+m       ; Ctrl + Shift + M
VideoSend=^+o       ; Ctrl + Shift + O
AudioSend=!a        ; Alt + A
VideoSend=!v        ; Alt + V
AudioSend=^d        ; Ctrl + D
VideoSend=^e        ; Ctrl + E

Special keys should be wrapped in braces:

PreSend={ESC}
PostSend={ENTER}
AudioSend=^+{SPACE}

Default app shortcut examples

Typical default mappings:

App Audio Video
Microsoft Teams ^+m ^+o
Zoom !a !v
Google Meet ^d ^e
Cisco Webex ^m ^+v
Skype / Lync #{F4} ^+{ENTER}
Slack Huddle ^+{SPACE} empty by default

Shortcuts may vary depending on app version, operating mode, language, or whether the meeting is running in a desktop app or browser. Adjust Settings.ini as needed.


Adding a custom meeting app

  1. Add the app ID to the [Apps] order:
[Apps]
Order=TeamsNew,Zoom,GoogleMeet,Webex,SkypeLync,Custom1
  1. Create or edit the app section:
[App.Custom1]
Enabled=1
Name=Custom Meeting App
MeetingWindow=[REGEXPTITLE:(?i).*Your Meeting Window Title.*]
Focus=
CloseWindow=
PreSend=
AudioSend=^m
VideoSend=^+v
PostSend=
ActivationDelayMs=150
  1. Save Settings.ini.
  2. Right-click the WeekDay tray icon.
  3. Click Reload settings.
  4. Test with Test audio toggle and Test camera toggle.

Window selectors

WeekDay uses AutoIt window selectors.

Useful selector examples:

MeetingWindow=[REGEXPTITLE:(?i).*Zoom.*(Meeting|Webinar).*]
MeetingWindow=[REGEXPTITLE:(?i).*(Google Meet|Meet -|meet.google.com).*]
MeetingWindow=[CLASS:LyncConversationWindowClass]

Tips:

  • Prefer MeetingWindow selectors that identify an actual call/meeting window, not just the main app window.
  • Use case-insensitive regex with (?i) when possible.
  • For browser-based meetings, include part of the browser tab or page title.
  • If WeekDay does not find the meeting window, check Logs\WeekDay.log and adjust the selector.

Startup installation

WeekDay can install or remove its Windows startup shortcut from the tray menu.

To install:

  1. Right-click the tray icon.
  2. Click Install startup shortcut.

To remove:

  1. Right-click the tray icon.
  2. Click Remove startup shortcut.

The startup shortcut points to the running executable when compiled. When running as an .au3 script, it points to the AutoIt interpreter with the script path as an argument.


Embedded files and runtime extraction

The latest version is designed so runtime assets can be embedded into the compiled executable using AutoIt FileInstall().

At startup, WeekDay extracts or refreshes:

  • Day icons: Assets\Icons\1.ico through Assets\Icons\7.ico
  • Default settings reference: settings.default.ini
  • Runtime folders such as Assets and Logs

When Help is selected from the tray menu, WeekDay extracts:

  • Help.html
  • Assets\Splash.jpg

The Help file is intentionally extracted only when requested, keeping startup lightweight while still allowing the compiled executable to recreate its own support files.


Building a release

Before compiling, make sure the project uses relative resource references and does not include private local paths.

Recommended build checklist:

  1. Keep all required source assets in the project folder.
  2. Confirm Settings.ini is safe for public release and does not contain personal data.
  3. Confirm Help.html and Splash.jpg are present.
  4. Confirm icons 1.ico through 7.ico are present.
  5. Confirm Week.ico is present for the executable icon.
  6. Compile WeekDay.au3 using AutoItWrapper / Aut2Exe.
  7. Test the compiled .exe from a clean writable folder.
  8. Confirm the app recreates Assets, Logs, settings.default.ini, and Help.html when needed.
  9. Confirm startup shortcut installation/removal works.
  10. Confirm Teams, Zoom, Google Meet, Webex, and custom profiles behave as expected.

Recommended output package:

WeekDay.zip
├─ WeekDay.exe
├─ README.md
└─ LICENSE

Because the executable can extract its embedded assets, releases do not need to include every runtime file unless you want users to see or edit them directly.


Suggested .gitignore

# Build outputs
*.exe
*.a3x
*.zip

# Runtime files
Logs/
Assets/
Help.html
settings.default.ini

# Local user configuration
Settings.local.ini

# Editor/system files
.vscode/
.idea/
*.bak
*.tmp
Thumbs.db
Desktop.ini

If you use Settings.ini as the embedded default configuration, keep a sanitized version in the repository. Do not commit personal keyboard profiles, machine-specific paths, private update URLs, or local environment details.


Troubleshooting

The hotkey does nothing

Check:

  • Is WeekDay running in the tray?
  • Is Pause hotkeys disabled?
  • Is the correct profile selected?
  • Does MuteHotkeys or CameraHotkeys match the keyboard output?
  • Does Key Inspector detect the key combination?
  • Is RequireMeetingWindow=1 preventing the command because no meeting window was found?

The command goes to the wrong app

Check:

  • ActivateMeetingWindow=1
  • RequireMeetingWindow=1
  • The MeetingWindow selector for the target app
  • The app order in [Apps]
  • Whether another meeting app window is open and matched first

The command toggles twice

Set:

SkipSendWhenInputAlreadyMatchesTarget=1

This helps when the keyboard already sends the exact app-native shortcut and WeekDay would otherwise send it again.

WeekDay cannot focus the meeting window

Try increasing:

ActivationRetries=5
ActivationVerifyMs=1200
ActivationDelayMs=250

Also check whether the meeting window is minimized, hidden, or running as an elevated/admin process while WeekDay is not.

Help does not open

WeekDay extracts Help.html only when the tray Help menu is clicked. If it fails, the app folder may not be writable.

Move the app to a writable folder, such as:

.\WeekDay

or run it once as administrator.

Logs are empty

Check:

LogEnabled=1

Then open:

Logs\WeekDay.log

from the tray menu.


Security and privacy

WeekDay is intended to run locally on Windows.

  • It does not need cloud access to handle hotkeys.
  • It does not record audio or video.
  • It does not read meeting content.
  • It only checks keyboard state, window titles/classes, and sends configured shortcuts.
  • Logs are written locally to the app folder.

If auto-update support is enabled in your build, review the updater configuration before publishing and document where updates are checked from.


Development notes

Important AutoIt functions used by the app include:

  • _IsPressed() for hotkey detection
  • WinList() / WinExists() / WinActive() for meeting window detection
  • WinActivate() / WinSetState() for focus handling
  • Send() for app-specific commands
  • FileInstall() for embedded resources
  • FileCreateShortcut() for startup installation
  • TrayCreateItem() / TrayGetMsg() for the tray UI

The source is intentionally configuration-driven. In most cases, new keyboards or meeting apps should be added through Settings.ini, not by changing the AutoIt code.


Roadmap ideas

Possible future improvements:

  • UI editor for Settings.ini.
  • Automatic meeting app selector preview.
  • Window selector test tool.
  • Profile auto-switching based on keyboard/device/location.
  • Per-app status indicator in the tray tooltip.
  • Optional sound or visual feedback after a successful toggle.
  • Portable release package with first-run setup wizard.

License

No license has been defined yet.

Before publishing publicly on GitHub, add a LICENSE file and update this section with the selected license.


Disclaimer

WeekDay sends keyboard shortcuts to meeting applications based on the configured rules. Meeting apps may change shortcut behavior, window titles, or window classes after updates. If something stops working, review Settings.ini, run Key Inspector if needed, and check Logs\WeekDay.log.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages