Search results

Sold and happily with its new owner :)

The device is for sale again, as I couldn't find a way to ship it to USA with the battery. The courier services I tried just wouldn't accept the delivery because of the battery. I think I could send this more easily within the EU, so I'll only accept offers from this corner of the globe from...

The device is now spoken for.

Yep, I live in Tampere. I totally missed that rule, here you go

1659530509

After some consideration I think my Pyra #21 would be better off in somebody else's hands. Due to family things I simply don't have the time to do anything with it. It's a 4GB EU 4G model and in mint condition. It has pretty much just sat on my desk. I can buy a new one if I find time again, but...

PNDManager uses qtpndman as a package abstraction, which in turn is a Qt wrapper around libpndman, which handles pretty much all the actual package management tasks. In addition PNDManager uses some parts of pandora-libraries for platform specific stuff. In order to use PNDManager with DBPs an...

Just a note: I implemented variable speed scrolling with configurable sensitivity and high resolution scrolling support over the weekend. Should make its way to your pyras at some point. Have fun :D

Hm, I may have found useful documentation to fix the scrolling in a more standard way. Let's put a pin on that discussion for now.

It would probably need two limit values: when it switches to slow speed and when it changes to fast speed. If these are the same number there's an uncomfortable area where the speed would skip erratically due to the noise in the nubs. The principle is simple, but there's some tuning like this to...

That's a good point, but they're probably handled separately. For example my laptop's touchpad looks like: Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 328 (BTN_TOOL_QUINTTAP) Event code...

Indeed. Pyrainput does read it as analog axes through evdev, but mouse wheels are not analog. So transforming the analog position into a series of mouse wheel scroll events for uinput is not that straightforward. Of course for example a joystick made from the nub events works as expected.

Yeah, the nubs are, but the uinput input event interface is not. It would be possible to fake it, but that's a bit more involved to get consistent. We could make an experimental mode for it, but for now I think it's more important to get the basics nailed down before too many packages depend on...

Sure, though it's a bit tricky to get right. See, the events specify the scroll amount as an integer, with the smallest changes being +1 or -1. The current implementation uses a thread for mouse handling that sends mouse events every 16ms if there's been changes. This means the simplest, and...

Profile support is done and merged. Next up is the configuration pipe. After these I'd like to do Configuration of all face buttons Just a simple system with a couple of options for now that enable the current keyboard/gamepad/mouse functionalities, not full remapping Replace the currently...

Working off that idea, maybe it should trigger a script on both events. That would be nicely configurable.

Update: I've implemented support for multivalue settings and have been working on profile support. I first made the hotkey Fn+Pyra+<number>, but that was both hard to use and not really nice code wise. The current implementation I'm trying out includes adding a "command mode" that can be...

Currently there's no configuration support for remapping ABXY, but I'm thinking people who want to do it could simply, for example, have two profiles that swap or unswap B and X. Those could be layered on top of any configuration the application uses. Meaningful names have been discussed before...

Well, the user can always override package specific mappings with appdata. I think package specific configuration should be used sparingly and in as limited a fashion as possible. Or stick to enabling a specific profile.

On discord I thought this would mean making profiles.current a path to profile, but actually the dbp can just pipe its configuration to /var/run/pyrainput, then just issue a reload of the current profile after it's run to revert.