Private.xml file and Elements 11.1

[RuslanI]

Hello, Takayama! 

from what I can see private.xml file does not exist any more in new Elements 11.1. 

So are all custom remappings now done through Karabiner's interface?

And is there a way to import the setting from my old private.xml file into new Elements 11.1? 

[Michael Dixon]

The Karabiner Elements interface lets you select from a number of remappings that have been predefined to cover a lot of use cases. It's in the Complex Modifications tab.

Any of these settings will be saved to ~/.config/karabiner.json, which is also where you can write your own changes directly. As far as I know, there is no way to import an existing private.xml file into a karabiner.json file.

[hba...@gmail.com]

I spent about a year (4 years ago) to made a very complex file of improvements which covers not only

the standard keyboard/mouse behaviour but fixes dozens of issues of OSX standard applications

(switching between windows or tabs, showing/closing windows, blocking something somewhere, etc.)

It's very, VERY unforgiving that I can't import my carefully tuned file into new version.

I had to upgrade the system due to disk failure and I'm fucked up now. Nothing is working as usual...

:-(

Dne pondělí 9. října 2017 12:50:05 UTC+2 Michael Dixon napsal(a):

[Mike Petonic]

I'm sure that you probably weren't trying to hate on the author, but just be thankful that such a tool can even exist, given Apple's continual locking down of MacOS.

The very nature of the vastly different capabilities of Karabiner vs Karabiner-elements necessitates such configuration file changes.  There was no way to keep the formats the same, especially since Elements was so crippled in the beginning (but catching up nicely).

[Hynek Bartoš]

Dear Mike,

I am glad that my donation enabled the author to build a fresh-new

application which is completely incompatible with the previous one.

Because I use multiple systems every single day, I need them to

behave exactly the same. This led to I throwed the Mac away and

avoiding it for almost 4 years...

Now I need to use it again, so I'm trying to convert my previous

definitions. And 'cause there are conditions related to the device,

window or application, I am not able to use any of the most wanted

subset of them. (See attached file.)

Could you please help me with the conversion of those definitions?

With the best regards, Hynek

PS: I converted the original XML file into JSON because I thought

that it could help me with the translation. It is easily readable,

but I can send you the XML as well.

On Thu, Apr 12, 2018 at 9:34 PM Mike Petonic <pet...@gmail.com> wrote:

I'm sure that you probably weren't trying to hate on the author, but just be thankful that such a tool can even exist, given Apple's continual locking down of MacOS.

The very nature of the vastly different capabilities of Karabiner vs Karabiner-elements necessitates such configuration file changes.  There was no way to keep the formats the same, especially since Elements was so crippled in the beginning (but catching up nicely).

On Thursday, March 29, 2018 at 1:29:52 PM UTC-10, hba...@gmail.com wrote:

I spent about a year to made a very complex file of improvements which covers not only

the standard keyboard/mouse behaviour but fixes dozens of issues of OSX standard applications

(switching between windows or tabs, showing/closing windows, blocking something somewhere, etc.)

It's very, VERY unforgiving that I can't import my carefully tuned file into new version.

I had to upgrade the system due to disk failure and I'm fucked up now. Nothing is working as usual...

:-(

Dne pondělí 9. října 2017 12:50:05 UTC+2 Michael Dixon napsal(a):

The Karabiner Elements interface lets you select from a number of remappings that have been predefined to cover a lot of use cases. It's in the Complex Modifications tab.

Any of these settings will be saved to ~/.config/karabiner.json, which is also where you can write your own changes directly. As far as I know, there is no way to import an existing private.xml file into a karabiner.json file.

On Saturday, October 7, 2017 at 12:05:56 AM UTC-4, RuslanI wrote:

Hello, Takayama! 

from what I can see private.xml file does not exist any more in new Elements 11.1. 

So are all custom remappings now done through Karabiner's interface?

And is there a way to import the setting from my old private.xml file into new Elements 11.1? 

--
You received this message because you are subscribed to a topic in the Google Groups "Karabiner" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osx-karabiner/8E-PXjt5ju0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osx-karabine...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osx-karabiner/b831f272-f9e0-41cb-87c0-87bb704ecd4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hynek Bartoš]

The most sad thing is that the author chose the JSON format

(over the previous XML) which is less synoptic, intolerant

to commas after the last element and incapable of using any

comments. During testing and debugging phase anybody needs

to comment/uncomment lines to quickly discover where the

bug is.

I made some new rules into \assets\complex_modifications

folder (single .json file). The first rule worked but after

I've added 2 more, the file disappeared from the Karabiner

and I don't know why. The .json itself is valid by all the

RFC 8259, RFC 7159, RFC 4627 and ECMA-404, but there is

something K-E doesn't like and I don't know why. Everything

is according to the website help. :-(

If you then consider the inability to comment lines, you

have a very nice game for the whole evening...

Hynek