Bazecor v1.4.5

Hi, Dygmates

After a well-enjoyed summer break, we're back with another update.

This time around, we focused on fixing a weird bug that caused Bazecor to crash when importing a layer created with 1.4.4.

We also continued making adjustments to how keys with modifiers are represented.

If you have Bazecor 1.4.4 on Windows and Mac, it should auto-update unless you disable that in preferences. On Linux, you have to download it manually.

What's new

• Fixed a bug where Bazecor would crash when importing a layer created with 1.4.4.
• Removed the modifier indicators in the Keyboard representation when the modified key has a visual representation. For example, show only "(" instead "Shift+9".
• Fixed a bug where you couldn't assign the previous macro inside a new macro.

What's next

For the next releases, we are mainly working on three things:

• Continue polishing some inconsistencies with the Keyboard Manager: there are some corner cases when disconnecting with virtual keyboards.
• New UX and UI for the layout editor.
• Improved connectivity over BT.

You can check our software and firmware roadmap at https://dygma.com/roadmap

As always, thank you so much for your support! See you in the next release!

–The Dygma Team

What's Changed

• fix: added parser to import routine to replace obj with React.JSX for icon keys by @alexpargon in #873
• fix: modified disable function for existing macro by @alexpargon in #874
• fix: solved symbol representation for multiple combinations of mods by @alexpargon in #877

Full Changelog: v1.4.4...v1.4.5

Bazecor v1.4.4

Hi, Dygmates

Here we are with another Bazecor update.

This release includes improvements to how the modifiers are represented when creating shortcuts.

We also have great news for Chrome OS users: you can now use Bazecor to configure your keyboard! Before, the app would open, but it wouldn't detect the keyboard.

If you have Bazecor 1.4.3 on Windows and Mac, it should auto-update –unless you have that disabled in preferences. On Linux, you have to download it manually.

What's new

• You can now use Bazecor to configure your keyboard in ChromeOS
• Improved the way modifiers are represented when creating shortcuts in the layout editor and in the Macros and Superkeys menus.
• Fixed a bug where icons of layers were not shown in the Macros and Superkeys menus.
• Fixed a bug where applying a color after deselecting a key could make Bazecor crash.
• Fixed a bug where the Retry button in the flashing procedure didn't work
• Fixed a bug in the preferences menu where the value indicator in a slider could prevent you from accessing the slider on top of it.

What's next

For the next releases, we are mainly working on three things:

• Continue polishing some inconsistencies with the Keyboard Manager: there are some corner cases when disconnecting with virtual keyboards.
• More UX and UI polishing.
• Improved connectivity over BT

You can check our software and firmware roadmap at https://dygma.com/roadmap

As always, thank you so much for your support! See you in the next release!

–The Dygma Team

What's Changed

• Use uaccess tag instead of mode 666 in udev rules and split Defy rules by @0rzech in #690
• Fix sk macro render icons by @alexpargon in #860
• Fix modifiers on keyboard representation by @thiagohernandez in #857
• Fix new responsive issues on layout editor by @thiagohernandez in #859
• Chore: Added support to change the slider indicator direction (top/bottom) by @thiagohernandez in #858
• Fix dot notation mods by @alexpargon in #861
• fix: added changes to better support icons in keys by @alexpargon in #862

Full Changelog: v1.4.3...v1.4.4

Bazecor v1.4.3

Hi, Dygmates

Here we are with another Bazecor update.

This release includes more improvements to the keyboard manager –we fixed a bug where the first disconnect of a keyboard was not detected– and more visual bug fixing.

We also added new options when assigning colors to your keyboard. You can now bulk-configure the backlight and underglow of each side separately. Thanks @folivaresrios for making this possible 😊

If you have Bazecor 1.4.2 on Windows and Mac, it should auto-update –unless you have that disabled in preferences. On Linux, you have to download it manually.

What's new

• We added the option to bulk-assig colors to the backlight and underglow of each side separately.
• Fixed a bug where the keyboard manager would not remove a keyboard from the menu the first time you unplugged it from the computer.
• Fixed a bug where an "Uncaught Exception" message appeared if your update preferences were not set.
• Fixed a bug where you couldn't add virtual keyboards on Linux.
• Fixed a bug where the Edit Mode buttons would overlap with the key picker is the Layout Editor.
• Fixed a bug where the wired neuron was displayed on the Layout Editor even if you had a Raise 2 or a wireless Defy.
• Fixed a bug where we displayed the neuron of the OG Raise in the firmware update screen of the Raise 2.
• Change the display name of the Raise2 to Raise 2.
• Fixed a bug where the system logs were flooded with wireless status requests
• Fixed a typo in the pop-up that appeared when you reconnected the sides in the RF settings. It said "has ben" instead of "has been".

What's next

For the next releases, we are mainly working on three things:

• Continue polishing some inconsistencies with the Keyboard Manager: there are some corner cases when disconnecting with virtual keyboards.
• More UX and UI polishing.
• Fix a bug where Bazecor can't connect to the keyboard in some Linux distros.

You can check our software and firmware roadmap at https://dygma.com/roadmap

As always, thank you so much for your support! See you in the next release!

–The Dygma Team

What's Changed

• fix: removed required flag from new value bakcupFrequency by @alexpargon in #845
• fix: upped electron version to get rid of dialog bug by @alexpargon in #846
• fix: changed device comms logs to debug, and only enabled that tag in… by @alexpargon in #847
• Fix mac zip signing for auto updater by @alexpargon in #844
• Modified device names for better readibility by @alexpargon in #849
• Fix: fixed typo on alert message by @alexpargon in #850
• Fix: Added new styles to avoid and prevent overlap buttons when the u… by @thiagohernandez in #851
• Chore: Removed Neuron representation from Raise2/Layout Editor by @thiagohernandez in #852
• Fix: Added the right shape for the Raise2 Neuron by @thiagohernandez in #853
• Rework color edit by @folivaresrios in #825
• fix: added getDevices to enumerate devices to be listened at startup by @alexpargon in #854
• fix: Defy wireless has no LED neuron, so changed it's visibility by @alexpargon in #856
• fix: changed name for virtual raise 2 to separate number by @alexpargon in #855

Full Changelog: v1.4.2...v1.4.3

Bazecor 1.4.2

Hi, Dygmates

Here we are with another Bazecor update.

This release includes more visual debugging, improvements in the Keyboard Manager and the option to flash custom firmware on your keyboard –no, it doesn't mean you can flash QMK or ZMK 😅

We've also fixed a bug that prevented Bazecor from auto-updating on some computers. If you downloaded Bazecor 1.4.0 or 1.4.1 and it hasn't updated automatically, please manually download it.

What's new

• We added support for flashing custom firmware directly on Bazecor. This is ideal for testing alpha releases or making your own modifications to the firmware.
• We improved the visual representation of Dual-Function keys, One-Shot Layers and One-Shot Modifiers.
• You can now access the Firmware Update screen via Bluetooth to check your firmware version. If you want to update the firmware, you will still need to connect the keyboard via USB.
• We added OS-specific representations of modifiers (like Option, Command, Ctrl, etc.)
• We fixed a bug where Bazecor would not update automatically on some computers.
• We fixed a bug in which your keyboards were not listed in the keyboard manager the first time you opened Bazecor after installing it.
• We fixed a bug where when loading a virtual keyboard, your actual keyboard would show as connected in the keyboard manager.
• We fixed a bug where your Bluetooth keyboards were disconnected when you disconnected a wired keyboard.

What's next

For the next release, we are mainly working on four things:

• Continue polishing some inconsistencies with the Keyboard Manager: it won't detect the first time you unplug a wired keyboard, and there are some corner cases when disconnecting with virtual keyboards.
• Continue polishing the UI and UX.
• Fix a bug where Bazecor can't connect to the keyboard in some Linux distros.

You can check our software and firmware roadmap at https://dygma.com/roadmap

As always, thank you so much for your support! See you in the next release!

–The Dygma Team

What's Changed

• Bluetooth users now may access FW Flashing screen by @alexpargon in #831
• Custom fw support by @alexpargon in #830
• Refactor: Added animation and different buttons colors according the n… by @thiagohernandez in #832
• fix: added optional chaining to verify the existence of an array by @alexpargon in #833
• fix: virtual devices are now fixed and remain in deviceManager by @alexpargon in #834
• fix: listNonConnected now properly returns the connected devs properly by @alexpargon in #835
• Improve UI elements on FirmwareCustomModal, add new warning section and added the right text according different models by @thiagohernandez in #839
• Fix auto updater by @alexpargon in #840
• Change the way to highlight keys, such as One Shot, Dual function and OS Keys by @thiagohernandez in #838
• Fix: Add support to ISO and ANSI layouts on ordinary preview keyboard (KeyPicker) by @thiagohernandez in #842
• Chore: Change the UI elements in Firmware update panel by @thiagohernandez in #843

Full Changelog: v1.4.1...v1.4.2

Bazecor 1.4.1

Hi, Dygmates

With our goal of continuously improving the configurator software for the Dygma Keyboards, today we have version 1.4.1.

This new release comes with a ton of small fixes to the UI and UX and a nifty new clear layer feature to further customize the layer you're clearing. Thanks, @folivaresrios.

Remember, if you already have Bazecor 1.4.0 with auto-update enabled, you shouldn't need to download this version. It automatically checks for updates once every 24 hours.

What's new

• New clear layer options: you can change each keyboard side's backlight and key type.
• The "Need Help" call to action now takes you to our new support page.
• We've adjusted the padding and spacing of buttons all across Bazecor for better visual consistency.
• We've removed the "export layer to PDF", as it wasn't working.
• Added responsive videos in the video tooltips.
• We improved the visual hierarchy of the "Choose a custom KeyCode" pop-up.
• We removed the buttons in the "Keyboard Manager" top bar. They were redundant.
• We improved the color and contrast of the Macro Timeline.
• We disabled the option to add mouse movements on Superkeys, as they are incompatible and didn't work.
• We redesigned the pop-up that appears when you hover over the battery icons.
• We fixed a bug where the Standard View / Single View selector would overlap with the key picker.

What's next

For the next release, we are mainly working on four things:

• Add support to flash a custom firmware from a file
• Polish some inconsistencies with the Keyboard Manager
• Continue polishing the UI and UX
• Fix a bug where Bazecor can't connect to the keyboard in some Linux

You can check our software and firmware roadmap at https://dygma.com/roadmap

As always, thank you so much for your support! See you in the next release!

–The Dygma Team

What's Changed

• feat: Extend ClearLayer by @folivaresrios in #822
• UI bug fixing pkg2 by @alexpargon in #824

Full Changelog: v1.4.0...v1.4.1

Bazecor 1.4.0

Hi, Dygmates!

After months of hard work, we finally have the stable release of Bazecor 1.4! Now, you can configure your wireless Dygma Keyboard via Bluetooth!

And that's just the tip of the iceberg! Let's walk you through everything new:

What's new

• You can now configure your keyboard via BT. Open Bazecor, press scan keyboards, and your keyboard will appear. However, this mode still has some limitations: you can edit your keyboard and save changes, but you can't update the firmware or restore backups.
• We have a new keyboard manager that lets you switch between your keyboards and easily create or load virtual keyboards (ideal for testing ideas or configuring your layout while you wait for your Dygma board to arrive)
• We've completely refactored the code of the firmware update process. It's much more robust and always restores your configuration after the update.
• We've redesigned the preferences menu from the ground up so it's more intuitive and easy to use.
• Bazecor will now auto-update to the latest stable release. You'll see a pop-up to allow this the first time you open Bazecor, and you can also configure it in the preferences menu.
• We've added compatibility with the Raise 2 so beta-testers can configure their keyboards.
• We've included a lot of small quality-of-life improvements.
  • If you try to leave a screen without saving your changes, a pop-up will warn you and force you to save or discard them.
  • In macros, we added a clear macro button and navigation buttons to move to the beginning or end of a macro.
  • In superkeys, you can now use Layer Shift on Hold and Modifiers on Tap. To use this, you need the 1.2.7 Firmware for the Defy and the 1.0.11 for the Raise.
• Finally, there's been a lot of invisible work to improve performance and future-proofing the code, like:
  • Migration to Typescript and Tailwind.
  • Updating dependencies to the latest versions, like Electron, React, etc.
  • Removing obsolete dependencies like React Bootstrap.
  • Improving the internal error logger for easier troubleshooting.

And, of course, a LOT of small bug fixing. You can see all the changes from 1.3.11 in the changelog at the bottom 👇

What's next

Of course, we'll keep working on improving our software and firmware with more frequent releases.

If you want to know what that will include, you can check our development roadmap at Dygma.com/roadmap.

As always, thank you so much for your support!

–The Dygma Team

What's Changed

• Preferences review by @alexpargon in #694
• Layout editor fix for Bz 2.0.0 by @alexpargon in #676
• chore: use prettier to format json files by @unional in #698
• Convert some code to TypeScript by @unional in #655
• chore: ignore some spelling issues by @unional in #699
• convert Focus to TypeScript by @unional in #700
• fix: erase only firmware program and not ble data by @Noteolvides in #572
• Bazecor 1.4.0 by @alexpargon in #569
• fix: device virtual connection state was not properly set by @alexpargon in #712
• Fix macro for text input with eurkey layout by @skvvara in #714
• [fix] Color palette sometimes not showing colors assigned to slots. by @skvvara in #713
• build(deps): bump ip from 2.0.0 to 2.0.1 by @dependabot in #711
• fix: when selecting color, Layer selection does not move any more by @alexpargon in #719
• feat: added custom keycode button to add any code including consumer keys by @alexpargon in #718
• fix: superkeys now create empty positions as expected by @alexpargon in #720
• feat: auto-restore process after bad FW update process backup restora… by @alexpargon in #721
• fix: added web preference that prevents background throttling of JS code by @alexpargon in #722
• fix: theme mode is now working again on mac by @alexpargon in #723
• feat: added UX behavior to follow permissions guidelines in MacOs by @alexpargon in #724
• fix: macros now record properly any modifiers combination by @alexpargon in #725
• Keymap API migration to typescript by @alexpargon in #726
• Clean and refactor Modules by @alexpargon in #727
• Update forge by @alexpargon in #730
• Loading keyboard info by @alexpargon in #729
• feat: changed the application icons by @alexpargon in #731
• feat: xtra options for Qukeys added to preferences, it requires firmw… by @alexpargon in #728
• HID issues on disconnect and find keyboards resolution by @alexpargon in #732
• fix: text in color picker inputs by @skvvara in #735
• fix: modified store handler to add types for stored data by @alexpargon in #736
• fix: custom keycode modal now has prefix and works properly by @alexpargon in #738
• fix: preferences now store qukeys values properly by @alexpargon in #737
• Fix schema violations by @alexpargon in #739
• Improving custom text by @alexpargon in #740
• feat: Choose the key (NOKEY/TRANS) and the color to clear layer with by @skvvara in #741
• fix: macros recorder now merges properly actions by @alexpargon in #742
• fix: app crashes when there's no config file (#743) by @skvvara in #744
• fix: app crashes when superkey actions array contains nulls (#748) by @skvvara in #749
• fix: added a device flag for the Raise2 wireless features support by @alexpargon in #756
• build(deps): bump follow-redirects from 1.15.4 to 1.15.6 by @dependabot in #747
• build(deps): bump webpack-dev-middleware from 5.3.3 to 5.3.4 by @dependabot in #752
• build(deps): bump express from 4.18.2 to 4.19.2 by @dependabot in #753
• build(deps-dev): bump vite from 4.5.2 to 4.5.3 by @dependabot in #755
• build(deps): bump tar from 6.1.15 to 6.2.1 by @dependabot in #763
• build(deps): bump semver from 5.7.1 to 7.6.0 by @dependabot in #766
• build(deps): bump ejs from 3.1.9 to 3.1.10 by @dependabot in #775
• feat: add french Ergo-L layout by @cyril-flieller in #770
• fix: missing settings property "isStandardView" prevents app from start by @skvvara in #769
• Fix macro recording by @skvvara in #771
• fix: firstChild was comming out as undefined in some instances by @alexpargon in #779
• Add logger tool by @alexpargon in #782
• feat: added update-electron-app package to auto update Bazecor by @alexpargon in #781
• Remove focus api by @alexpargon in #787
• Shadcn tailwind migration by @alexpargon in #792
• refactor: dropdwon -> dropdown by @unional in #784
• feat(ergo-l): update ergo-l layout to 1.0 by @cyril-flieller in #789
• build(deps): bump ws from 7.5.9 to 7.5.10 by @dependabot in #794
• feat: add Latin American Layout by @folivaresrios in #795
• Add .node-version and .nvmrc files with Node.js version 20.13.1 by @folivaresrios in #796
• fix: changing backup frequency setting doesn't work by @skvvara in #798
• fix: standardview now resets selected key when changing modes by @alexpargon in #800
• fix: superkeys view now checks for undefined string before .substr by @alexpargon in #801
• fix: DeviceManager View by @folivaresrios in #797
• Fix: Change the way to render icons inside the popover menu on Macro… by @thiagohernandez in #802
• fix: now keys selected on standard view behave as expected in superkView by @alexpargon in #803
• Backup settings notify change by @alexpargon in #804
• fix: now deviceManager filters out unconnected devices by @alexpargon in https://github.com/Dygmalab/Bazecor/pul...

v1.4.0-rc.6

Hi, Dygmates!

We have great news! This is the final Release Candidate before the stable release of Bazecor 1.4.0!

In this RC-6, we fixed a ton of small bugs and also added new settings for the new auto-update feature:

Now, when you open Bazecor for the first time, a pop-up will ask you if you want auto-update enabled. Of course, there's also a setting in the preferences to activate it or not if you change your mind later.

IMPORTANT! In some cases very rare cases, we've seen Bazecor tell you that the keyboard is in bootloader mode after the firmware update. If this happens to you, don't worry: unplug all the cables from the neuron, restart Bazecor, restore your latest backup from the preferences menu, and you're good to go. Report it, though, as that's something that should not happen.

What's New on Bazecor 1.4 rc.6

• Added new Raise 2 virtual keyboards so you can start preparing your layers
• Improved re-scaling performance of the key picker in Single View
• We temporarily removed the option to restore your backups via Bluetooth. It was too slow and triggered visual errors.
• Fixed a bug where accessing the Superkeys Menu triggered an error
• Fixed a bug where deleting a Superkey corrupted your layers and layer names
• Fixed a bug where you couldn't edit a Trans Key in Standard View
• Fixed a bug where the cancel update button was not working
• We improved the visual representation of keys in the macro editor
• Fixed a bug where the macro recorder added extra inputs
• Fixed a bug where NO KEY was shown regardless of the key selected in the Superkeys Standard View
• Fixed a bug where you couldn't edit your deep sleep setting

What's next?

During this week we want to polish any more bugs like these that might appear and release Bazecor 1.4.0 officially next week 😊

Apart from that, you can check Dygma.com/roadmap to learn what else we are working on!

As always, thank you so much for your support!

–The Dygma Team

What's Changed

• refactor: dropdwon -> dropdown by @unional in #784
• feat(ergo-l): update ergo-l layout to 1.0 by @cyril-flieller in #789
• build(deps): bump ws from 7.5.9 to 7.5.10 by @dependabot in #794
• feat: add Latin American Layout by @folivaresrios in #795
• Add .node-version and .nvmrc files with Node.js version 20.13.1 by @folivaresrios in #796
• fix: changing backup frequency setting doesn't work by @skvvara in #798
• fix: standardview now resets selected key when changing modes by @alexpargon in #800
• fix: superkeys view now checks for undefined string before .substr by @alexpargon in #801
• fix: DeviceManager View by @folivaresrios in #797
• Fix: Change the way to render icons inside the popover menu on Macro… by @thiagohernandez in #802
• fix: now keys selected on standard view behave as expected in superkView by @alexpargon in #803
• Backup settings notify change by @alexpargon in #804
• fix: now deviceManager filters out unconnected devices by @alexpargon in #805
• Fix typo in LED Preferences page by @bit-operator in #806
• fix: now cancel event buttons work in the firmware state machines by @alexpargon in #809
• Fix: Adjusted the max height on the keyboard on Single View by @thiagohernandez in #808
• Refactor: Added new color palette and keymap for Raise 2 virtual keyb… by @thiagohernandez in #812
• Fix: Added new styles to improve experince in Layout Editor across di… by @thiagohernandez in #811
• feat: added OptIn tool for autoUpdate options by @alexpargon in #807
• Fix: Allow HTML on the selected value on Superkeys stadanrd view by @thiagohernandez in #810
• fix: disabled backup restore in HID due to comms instability through … by @alexpargon in #813
• fixed true sleep slider to be enabled with condition by @alexpargon in #814
• fix: added delay to mitigate wireless battery commands intrusion by @alexpargon in #815
• fix: text to inform the user about backup restore with BT is now more… by @alexpargon in #816
• fix: now standard view lets you configure properly a no key with modi… by @alexpargon in #817
• fix: superkeys replace process now works as expected when saving new … by @alexpargon in #818
• UI bug fixing by @alexpargon in #819

New Contributors

• @folivaresrios made their first contribution in #795
• @thiagohernandez made their first contribution in #802
• @bit-operator made their first contribution in #806

Full Changelog: v1.4.0-rc.5...v1.4.0-rc.6

v1.4.0-rc.5

Hi, Dygmates!

We are very close to the stable release of Bazecor 1.4.0! This new Release Candidate adds two new key elements of that release:

• A new, more intuitive and robust Keyboard Manager that replaces the old Keyboard Selector
• A refactored firmware update process that should help get rid of all those pesky update problems.

We've troubleshot both extensively, but a change of that caliber needs your help, so please install it and try it out!

IMPORTANT! In some cases, we've seen Bazecor tell you that the keyboard is in bootloader mode after the firmware update. If this happens to you, don't worry: unplug all the cables from the neuron, restart Bazecor, restore your latest backup from the preferences menu, and you're good to go. Report it, though, as that's something that should not happen.

What's New on Bazecor 1.4 rc.5

• We have designed a new Keyboard Manager to easily select or switch between devices.
• We have refactored the firmware update process for more robust updates.
• We added an additional step to the firmware process that detects if your layers have been restored and restores your last backup if they haven't. If there's any hiccup in the process, a pop-up will tell you that your layers haven't been restored.
• The firmware update process will now reset your Bluetooth devices; we found out that not resetting them was causing a lot of bugs afterward.
• We've added an auto-updater feature that'll update Bazecor to the latest stable release (it doesn't update to RCs).
• We've migrated the key Style Components dependencies to Tailwind for better consistency and reliability in the UI.
• We've also removed Bootstrap dependencies, as it was going to be phased out.
• Bazecor is now capable of configuring the Raise 2, although not via BT.

What's Changed

• Add logger tool by @alexpargon in #782
• feat: added update-electron-app package to auto update Bazecor by @alexpargon in #781
• Remove focus api by @alexpargon in #787
• Shadcn tailwind migration by @alexpargon in #792

Full Changelog: v1.4.0-rc4...v1.4.0-rc.5

What's next?

We've prepared a complete roadmap with what we're working on and what we'll tackle next. You can check it out at Dygma.com/roadmap.

Besides fixing the above bugs and implementing the new home screen, we are working on making Bazecor auto-update, so you don't need to download it whenever there's a new release.

As always, thank you so much for your support!

–The Dygma Team

v1.4.0-rc.4

Hi, Dygmates!

Quick release this week to fix some bugs while we work on a new home screen for Bazecor that will improve how you manage your devices.

As you may already know, Bazecor 1.4.0 now works over Bluetooth, and it has a reworked preferences section and refactored code in Typescript.

Please download it, try it out, and let us know your thoughts.

What's New on Bazecor 1.4 rc4

• Fixed a bug where the app crashes if there's no previous configuration file
• Fixed a bug where the app crashes if there are empty superkeys
• Added support for wireless features in the Raise 2 virtual keyboards
• Updated multiple dependencies
• Added French Ergo-L layout by @cyril-flieller
• Fixed a Windows MacroEditor error that failed when recording macros by @skvvara
• Fixed a MacroEditor Timeline error where the scrollbar can disappear when being updated

What's Changed

• fix: app crashes when there's no config file (#743) by @skvvara in #744
• fix: app crashes when superkey actions array contains nulls (#748) by @skvvara in #749
• fix: added a device flag for the Raise2 wireless features support by @alexpargon in #756
• build(deps): bump follow-redirects from 1.15.4 to 1.15.6 by @dependabot in #747
• build(deps): bump webpack-dev-middleware from 5.3.3 to 5.3.4 by @dependabot in #752
• build(deps): bump express from 4.18.2 to 4.19.2 by @dependabot in #753
• build(deps-dev): bump vite from 4.5.2 to 4.5.3 by @dependabot in #755
• build(deps): bump tar from 6.1.15 to 6.2.1 by @dependabot in #763
• build(deps): bump semver from 5.7.1 to 7.6.0 by @dependabot in #766
• build(deps): bump ejs from 3.1.9 to 3.1.10 by @dependabot in #775
• feat: add french Ergo-L layout by @cyril-flieller in #770
• fix: missing settings property "isStandardView" prevents app from start by @skvvara in #769
• Fix macro recording by @skvvara in #771
• fix: firstChild was comming out as undefined in some instances by @alexpargon in #779

New Contributors

• @cyril-flieller made their first contribution in #770

Full Changelog: v1.4.0-rc.3...v1.4.0-rc4

Known Bazecor bugs

• The flashing procedure doesn't work on all computers. In some, it gets stuck in the neuron.
• EurKey alt keys need a visual update
• EurKey doesn't work well in the macro text box
• The Scan keyboards button doesn't work unless you disconnect the previous keyboard
• There's no way to edit delays in the macro editor
• Bazecor is not able to detect the keyboard via BT in some Linux devices

What's next?

Besides fixing the above bugs and implementing the new home screen, we are working on making Bazecor auto-update, so you don't need to download it whenever there's a new release.

As always, thank you so much for your support!

–The Dygma Team

v1.4.0-rc.3

Hi, Dygmates!

Quick release this week to fix some bugs caused by changes introduced in 1.4.0-rc2 😅

As you may already know, Bazecor 1.4.0 now works over Bluetooth, and it has a reworked preferences section and refactored code in Typescript.

Please download it, try it out, and let us know your thoughts.

What's new in Bazecor 1.4.0-rc3

• A new clear layer menu thanks to @skvvara lets you select the color of the cleared layer and if you want No Key or Transparent keys

Bugfixing

• Fixed a bug where saving your preferences would give you an error message
• Fixed a bug where the Superkeys menu made Bazecor crash
• Fixed a bug where the new custom keycodes would not work (and we also tried to explain them better)
• Fixed a bug where the macro recording would not work in some scenarios
• Fixed a bug where Bazecor wouldn't start if you did a clean stall

Known Bazecor bugs

• The flashing procedure doesn't work on all computers. In some, it gets stuck in the neuron.
• EurKey alt keys need a visual update
• EurKey doesn't work well in the macro text box
• The Scan keyboards button doesn't work unless you disconnect the previous keyboard
• There's no way to edit delays in the macro editor
• Bazecor is not able to detect the keyboard via BT in some Linux devices

What's next?

Besides fixing the above bugs, we are working on making Bazecor auto-update, so you don't need to download it whenever there's a new release.

As always, thank you so much for your support!

–The Dygma Team

Changelog

• fix: text in color picker inputs by @skvvara in #735
• fix: modified store handler to add types for stored data by @alexpargon in #736
• fix: custom keycode modal now has prefix and works properly by @alexpargon in #738
• fix: preferences now store qukeys values properly by @alexpargon in #737
• Fix schema violations by @alexpargon in #739
• Improving custom text by @alexpargon in #740
• feat: Choose the key (NOKEY/TRANS) and the color to clear layer with by @skvvara in #741
• fix: macros recorder now merges properly actions by @alexpargon in #742

Full Changelog: v1.4.0-rc.2...v1.4.0-rc.3