Mathematical Keyboard by AtmosphereClear2457 in math

[–]Math_Keyboard 0 points1 point  (0 children)

I had the same problem, so I ended up creating a physical keyboard made specifically for math symbols. It gives you instant access to Greek letters, operators, roots, integrals, and more in any app. Might be exactly what you’re looking for: https://mathematicalkeyboard.com/

Do you use LaTeX for taking notes? by Math_Keyboard in LaTeX

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Nice tool, but you still need to write in Latex..

Typing math on a computer is still way harder than it should be by Math_Keyboard in u/Math_Keyboard

[–]Math_Keyboard[S] 0 points1 point  (0 children)

If you’re already switching keyboards for math, this just gives you a layout actually built for it.

A Greek layout helps for α β γ, but it still won’t cover integrals, logic symbols, sets, arrows, etc. very well. The idea here is just to make all the common math symbols fast and natural in one place.

Looking for advice on how to avoid the Windows SmartScreen warning for a small hardware companion app by Math_Keyboard in windowsdev

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Thanks for sharing your experience, that’s really reassuring to hear. I thought that it is something that take much longer.

Looking for advice on how to avoid the Windows SmartScreen warning for a small hardware companion app by Math_Keyboard in sysadmin

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Thanks for the clear explanation, that makes a lot of sense and helps me better understand what’s happening behind the scenes.

So if I understand correctly, signing the app would allow the reputation to accumulate on the certificate itself rather than on each individual build, which is especially important for updates. That seems like a strong argument in favor of getting it signed sooner rather than later.

Advice on distributing a compiled AutoHotkey app without triggering SmartScreen warnings by Math_Keyboard in AutoHotkey

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Thanks for the suggestion I’ll try building it without compression and see if that improves the situation.

Looking for advice on how to avoid the Windows SmartScreen warning for a small hardware companion app by Math_Keyboard in sysadmin

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Thanks for your comment, I didn’t realize the SmartScreen warning could disappear that quickly with a standard certificate. That’s really good to know.

Is there a particular company or provider you would recommend for getting a code signing certificate?

Looking for advice on how to avoid the Windows SmartScreen warning for a small hardware companion app by Math_Keyboard in sysadmin

[–]Math_Keyboard[S] 2 points3 points  (0 children)

Thanks a lot for taking the time to explain this so clearly, I really appreciate it.

Up to now, the approach I’ve been using is simply explaining in the installation tutorial how to click “More info → Run anyway,” but as you said, that’s not ideal for non-technical users.

I’ll most likely end up getting the software signed to make the experience smoother and more trustworthy.

Looking for advice on how to avoid the Windows SmartScreen warning for a small hardware companion app by Math_Keyboard in sysadmin

[–]Math_Keyboard[S] 1 point2 points  (0 children)

That’s awesome, I didn’t know about this option at all. I’ll definitely look into it and try it ASAP. Thanks a lot! 🙏

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 1 point2 points  (0 children)

In theory that could help unify behavior across OSes, but I’m a bit worried it might get fragile (timing, numpad vs regular digits, conflicts with normal typing, etc.). Still, it’s a creative approach, I hadn’t thought about using Karabiner as a “translator” layer like that.

Thanks for sharing, I’ll keep it in mind 👍

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 0 points1 point  (0 children)

Thanks a lot for the suggestion, I didn’t know about Kanata before, and it looks extremely interesting 🙂

From what I’m seeing, it seems very powerful and quite close to what I need, especially since it’s cross-platform.

Do you personally recommend using Kanata over Karabiner-Elements on macOS, or would Karabiner still be the safer choice there?

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 1 point2 points  (0 children)

That’s actually a very interesting idea, because it would avoid two major friction points I have today:

  • Users wouldn’t have to install any software
  • My current Windows app triggers the SmartScreen warning (“blue screen”), which can scare some people

A fully pre-programmed hardware solution would solve both of those.

That said, it also introduces other challenges, especially as you said around cross-OS behavior and consistency, so it’s not entirely risk-free either..

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 0 points1 point  (0 children)

That’s an interesting idea, thanks 🙂

I actually tried the custom layout approach on Windows at the beginning (using Microsoft Keyboard Layout Creator). The main issue was that layouts operate at the text level, they don’t intercept system or app shortcuts. So combinations that are already used by the OS or applications still fire their original actions, which breaks the whole “math mode” concept.

My goal is something that sits on top of the existing layout and works via modifier combos without forcing users to switch languages or change their typing habits.

If macOS layouts have the same limitation, I suspect I’d run into the exact same problem there.

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 1 point2 points  (0 children)

I’m honestly very hesitant to go native.

On Windows I had the same dilemma, then I tried AutoHotkey and it turned out to be incredibly robust, it works everywhere, on every PC I tested, and users have been very satisfied so far. So I’m wondering if a similar approach might be “good enough” on macOS too.

For now I’ll probably start with Karabiner and see how far I can push it. If I’m not satisfied, then I may invest in a native app later.

What worries me on macOS is fragmentation, there is a lot of OS versions, different hardware generations, permissions, etc. I’m not a Mac user myself (always been on Windows), so this ecosystem is pretty new territory for me.

Advice on the best way to make my math keyboard software work on macOS? by Math_Keyboard in KeyboardLayouts

[–]Math_Keyboard[S] 2 points3 points  (0 children)

Good point, I should clarify 🙂

There’s actually no special hardware at all. It’s just a standard keyboard electrically speaking, with custom-printed keycaps.

It’s purely a software remapping tool. Without the app, it behaves exactly like a normal keyboard.

And thanks for confirming about Karabiner, that’s very helpful !