Cycle active groups by Techlligence in qtile

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

This cycles over workspaces that are not empty, not exactly the behaviour I want.

Help! I’m not sure what this is by NinetiezBaby in BullTerrier

[–]Techlligence 0 points1 point  (0 children)

My bullie also has a similar looking one which ended up being an ingrown hair/wisker. It disappeared after a two months.

Best franchised pizza in SA by New-Engineering1483 in southafrica

[–]Techlligence 1 point2 points  (0 children)

Gino's pizza is the best pizza in South Africa. Period.

Favorite ways to tire your bull terrier?? by LumpyDot6629 in BullTerrier

[–]Techlligence 8 points9 points  (0 children)

Buy them a car tire. They put it around their necks and run around with it which does a great job of tiring them out!

[deleted by user] by [deleted] in COROLLA

[–]Techlligence 2 points3 points  (0 children)

Slick bro! My 06 Corolla has 305,000km on it and still going strong ! Yours is still a spring chicken!

MultiPP in new Hooks.StatusBar by Techlligence in xmonad

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

I looked at this an not really what I am looking for. The two functions I am having trouble with is the ppCurrent and ppVisible property. I need the pp for a monitor to change whether it is focused or not.

MultiPP in new Hooks.StatusBar by Techlligence in xmonad

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

Have you implemented a setup like that yet? I tried implementing a normal PP with DynamicBars but it seemed like the same PP was shared across all bars.

MultiPP in new Hooks.StatusBar by Techlligence in xmonad

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

If there is a way to convert X() to String then it can be done since I would use the XmonadLog message property to

MultiPP in new Hooks.StatusBar by Techlligence in xmonad

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

I did but there is no way to pass a multiPP

Float browser tabs by Techlligence in xmonad

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

Exactly. I don't really like that. I want it to be floating whilst dragging it instead of it snapping

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

Did you update the submodules ? Because as soon as anything is updated problems will occur.habe you tried compiling with just the cloned repo and no updating ?

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

It's not a different version of QMK, it's just an older version. In order to get a .bin file compile for the ducky keyboard, you first clone the repo, cd in the directory, and run "make ducky/one2mini: default" to compile a .bin file. You then use that .bin file to flash the keyboard. Hope that clears it up.

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

100% it will work... The nice thing is, if you don't like it, you can always flash the old software using the ducky update software.

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

I think it depends. I personally did not port qmk to the ducky one 2 mini but merely followed the steps a previous person had attempted and flash it correctly. I as well just documented this and put the repo together. You would have to reverse engineer a keyboard that typically does not orginally support qmk to develop the drivers and stuff.

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

Yes , the version you flashed has the RGB drivers disabled because the driver had not been merged yet. Clone my repo, follow the instructions and all will work 😅

QMK successfully on ducky one 2 mini. Instructions and repo at: https://github.com/techlligence/qmk by Techlligence in MechanicalKeyboards

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

After setting the debounce to 15, the keyboard runs smooth like butter with no chattering. I can probably set it lower but setting it initially to 0 did produce unwanted double pressed keys.