Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WF can't compile a working matrix with online configurator #58

Open
cubiq opened this issue Jul 4, 2016 · 5 comments
Open

WF can't compile a working matrix with online configurator #58

cubiq opened this issue Jul 4, 2016 · 5 comments

Comments

@cubiq
Copy link

cubiq commented Jul 4, 2016

something seems off with the latest configurator and the whitefox. I get very weird results, the matrix seems shifted to the left of a couple of positions. burning an older firmware works without issues.

@jbondeson
Copy link

Are you trying import an older layout by chance?

In order to handle the multiple layouts of the WF without adding hidden keys or get really tricky at the compilation level I modified the KLL generation code to key off of the scan codes with commit 5ee6215 this allows for the diff algorithm to be able to correctly reduce to the base map even when some keys are missing. The unfortunate downside to that was any layout based on the older non-AllBlank layout were broken.

With new layouts created from scratch on the configurator we haven't seen issues like you've described yet.

@cubiq
Copy link
Author

cubiq commented Jul 9, 2016

I believe I started from scratch, but the current system saves the latest layout (without asking which is a bit annoying). could it be that the new and old layouts got overlapped?

@jbondeson
Copy link

jbondeson commented Jul 9, 2016

Very odd. I can probably tell from the JSON it's using. Would you mind throwing it in a gist?

As for the saving, it's definitely geared to the occasional user rather than more advanced I'm planning on switching that up a bit (HaaTa has suggested a "recent downloads" functionality that I like). The biggest consideration was to not lose work when refreshing the page.

@cubiq
Copy link
Author

cubiq commented Jul 9, 2016

let me try to clean the browser cache and start over.

As per the auto-save I would instead add a "save" button, but that's just me.

@jbondeson
Copy link

The layouts are stored in local storage currently so the easiest it to just hit the "reset to default" button which returns to the stock layout for that keyboard variant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants