deskthority

One thing i DO have a problem with with EU immigration is , if I as a ( currently at least) EU citizen was to move to Sweden i would have to have a job or have the means to support myself. In the UK however you don't , you can just come even if you don't have a job, the direct quote form the uk.gov ...

In sales we have "buyer's remorse" and there is a rule in the US that either party has 3 business days to rescind certain types of contracts.
Sure I know what you mean, common policy. But this is not sales. Although some may argue that quite a few Brexit voters had their vote "sold" to them under ...

Not the fat cats at the top of the heap. It's the peons, at the bottom of the food chain - who actually voted for this abortion - they are the ones who will have to truly absorb the punishment.
Unfortunately not. It's always the middle class who (...voted overwhelmingly for remain...) pays for ...

Quite interesting to see the vote by age brackets. Baby boomers, you f**k us over once again!

Boot delay: There is a 1.5second wait in the USB init function. The order of things is: disconnect USB BUS (release the pullup on D+ line), wait 1.5 seconds, connect USB BUS (enable the pullup on D+ line). This code is my entirely my "fault"; it is there for the case when the code is run after a ...

You should use FN0 (not FN1) - the number corresponds to the number in the brackets in fn_actions.
For the possible keycodes, see this post .
Note that you can't type e.g. tilde (~) directly on most layouts, simply because there is no such key. For the computer to produce a tilde, it needs to think ...

Hi folks - feel free to correct me if the problem is on my side (very likely), but DT looks weird for me when I am on HiDPI on linux.

Imgur album here .

There are 4 screenshots in the album above: "Native" DT, "native" other forum (phpbb-based I think), "2x-zoom" DT, "2x-zoom" other forum. You can ...

Yea, while I liked pcbway before this whole shebang (as I wrote above), I'll most likely not be using, or recommending, them again.

Nice!

Right. Looks like a lot of stuff to try out... will do. Eventually. Thanks!

I guess the first up are some IBM Model F and some Islay drinks.

{And thanks for the drink!}

https://upload.wikimedia.org/wikipedia/commons/thumb/a/a2/Whiskyhogmanay2010.jpg/398px-Whiskyhogmanay2010.jpg

This reminded me that I gotta figure out a liquid something for my in-law. I've had some Talisker 18YO with him and I thought it's pretty good - but I don't really know much about scotch ...

I've used PCBWay for my kb45p . The reason was price (for these bigger PCBs it was very good IMO). I personally value the most the quality of the PCBs (compared to the price) - and this batch from PCBWay was pretty good (I'd say the same or better as some other China-based PCB manufacturers I've ...

The MCU we're considering at the moment (MKL27Z256*), the main reason for QFN is space. The various packages are priced about the same (with QFN slightly cheaper), but the smallest package with leads on that one is LQFP-64. Which is big.

For me the most compelling reason for ARMs is the hardware ...

Thanks, I understand now. My mistake, I said min 3V above. Every ARM chip can do that, but the actual minimum depends. For the MCU we're considering (MKL27Zxxx) it's 1.71V according to the datasheet. This normally means it can usually go a bit lower, but it becomes unpredictable.

The (arm) MCU is not designed to be powered from 2x AA as it can only use about 20% of the batteries full capacity, thus I would not design any features around it.
Didn't know about that - any reference?
The 2xAA was only an example, it could be any power source producing reasonably stable 1.8V to ...

IO: as many as we can. ISP: depends on the architecture (it is 4 for AVRs: reset, miso, mosi, clk; but only 2 for ARMs: SWDIO, SWCLK). I personally would like to see at least one more power pin, "VIN", plus a bunch of solder jumpers.

Once more about the power: 4 pins altogether: GND, VUSB, VIN, VCC ...

There are a few reasons I prefer Freescale (well it's also NXP now) Kinetis to LPC chips: LPC chips need both a crystal AND a voltage regulator; Jacob's (aka kiibohd) code is for Kinetis ("bare-metal", so portable to other Kinetis chips without too much work, but other families require quite a bit ...

The proposed chip (MKL27Z256*) does not have any special capacitive sensing hardware module (this is really very similar chip as the one in Teensy LC). {The K20 family, think Teensy 3.x/MCHCK/InputClubKeyboard, does have *a* capsense module, the hardware module is called TSI.} {So any capacitive ...

I think it's quite fine to go with 1.2mm thick PCB, or even 1mm. The thing will be small, and that thickness is plenty. Source: I've had 1.2mm batch of these. {I actually also have a 0.5mm thick this one - and that one flexes slightly when some amount of force is applied.}

Ad 1): the 'dfu-util' part should be modified to point to where the dfu-util program is. (See e.g. here .) The 'default-fw.bin' should either be the full path to where the firmware you're trying to flash is (e.g. 'C:\Users\<your_username>\Desktop\firmware.bin'), or you can run the command when your ...

Ah, sorry Cookie, this thread slipped through my Spy feed.

Unfortunately I haven't seen any micro sockets with mini footprint... It may be possible to create a custom super-thin PCB which would carry the micro USB and solder to the mini footprint ... but I think that for practical purposes it is ...

sorry guys, very busy at work.

That error refers to this.

They are in the sources here and here. Not sure, they may also be explained on the wiki, but I can never find it.

You current error is caused by this:
In your keymap_common.h:

K5F, K5G, K5H, \
) { \
{ KC_##K00, KC_NO , KC_##K02, KC_##K03, KC_##K04, KC_##K05, KC_##K06, KC_##K07, KC_##K08, KC_##K09, KC_NO , KC_##K0B, KC_##K0C, KC_##K0D, KC_##K0E, KC_##K0F, KC_##K0G, KC_##K0H }, \

There should be no comma ...

failed
make: *** [obj_gh60_lufa/keymap_poker.o] Error 1

above it there are a whole bunch of lines telling me that many of my keys are undeclared
This is not the actual error, just a message that the compilation failed. The actual problem is printed above this message. If you want someone here to ...

Ah! Sorry - I didn't mean to publicise this much, it is just that this was the only macro actually used in your keymap

Need to also interpret the 'D(..)' and 'U(..)'. Forget where the docs are; but from memory 'D' is for 'down', 'U' is for 'up', 'T' is for 'tap' (='down'+pause+'up').

So that macro does 'press down alt+tab' (and keep pressed) when FN8 is pressed down, and 'release the tab' when FN8 is released {not ...

Looks good, although I can't confirm the distances.

The KLE layouts are: for split spacebar and for normal spacebar.

Macros are done via FN , so you assign FN8 in that example.

The parameter in the ACTION_MACRO is just a number, but using labels is helpful.

In the definition - this gets called both when FN8 is pressed (then record->event.pressed is true) and then FN8 is released (then it's false).

The ...

You have one more dfu-capable device attached (some bluetooth things are), so you need to select the right one (as you've figured out). I would go with specifying the VID:PID (that should be most reliable):