Fix: non-functional keybinding for floating windows

[rajghosh06-dev]

Description

This pull request fixes a typo in the Hyprland keybindings configuration.
The directive was incorrectly written as bindd, which Hyprland does not recognize.
It has been corrected to bind, ensuring the shortcut works properly.

Changes

• Improved
• Bug Fixes
• Feature
• Documentation
• Other

Context

Hyprland supports bind, binde, and bindm as valid binding keywords.
The configuration contained bindd, which caused Hyprland to throw an error and ignore the shortcut.
By replacing bindd with bind, the shortcut now executes the script ml4w-toggle-allfloat correctly.

How Has This Been Tested?

• Tested locally on Arch Linux + ML4W setup.
• Confirmed that bindd throws a config error and does not work.
• Confirmed that replacing with bind fixes the issue and the shortcut works as intended.

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my code.
• My changes do not introduce new warnings.
• I have tested the fix locally and confirmed functionality.

Screenshots

NOTE: this is a one-line config fix.

IMG1: Shows the error!

IMG2: Shows the Error

IMG3: Corrected Version

IMG4: Working Pic

Related Issues

One Related Issue, I have explained it in the Comments. This PR directly addresses the problem.

Additional Notes

This is a small but important fix to ensure the configuration parses cleanly and the shortcut works out of the box.

---

[rajghosh06-dev]

@mylinuxforwork
Hi, I noticed that the floating windows shortcut SUPER + SHIFT + T wasn’t working because the config used bindd, which Hyprland doesn’t recognize.

I tested locally on my Arch + ML4W, and replacing it with bind fixed the issue — the shortcut now works properly. This PR applies that correction.

[rajghosh06-dev]

@mylinuxforwork Hi, I noticed that the floating windows shortcut SUPER + SHIFT + T wasn’t working because the config used bindd, which Hyprland doesn’t recognize.

I tested locally on my Arch + ML4W, and replacing it with bind fixed the issue — the shortcut now works properly. This PR applies that correction.

I noticed that in my custom config defaultRG.conf, bindd throws errors, while bind works correctly.

In the shipped latest update, default.conf, the bindd seems to work without errors, possibly due to ML4W-specific extensions [it’s something ML4W’s wrapper scripts or patched configs interpret].
This PR corrects the line to use bind, which is the standard Hyprland keyword.
Please confirm if bindd was intentional or a typo?

default.conf when enabled from ml4w-settings [shows NO ERROR]

- Here no error is raised when used `bindd`

my custom keybinding-> 'defaultRG.conf' (using bindd) when enabled from ml4w-settings [shows ERROR, not functional]

- Error raised when used `bind`. This is only seen here in my custom .conf (`defaultRG.conf`)

ERROR Message

but in the same custom keybinding-> 'defaultRG.conf' (using bind) when enabled from ml4w-settings [shows no ERROR, and is functional]

---

Ultimately, this difference in behavior between bind and bindd introduces complications, especially for users maintaining custom keybinding configs. Aligning with the standard Hyprland keyword (bind) would ensure consistency and prevent unexpected errors across different setups.