- 170 Posts
- 312 Comments
Cool, I didn’t know that SMW central has its own patcher. I used this one: https://www.marcrobledo.com/RomPatcher.js/
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish3·1 month agoI also tried with the fingerprint sensor enabled, but managed to reproduce the issue :(
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish1·1 month agoYes :)
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish2·1 month agoThat’s strange - they said they finished shipping. Maybe try reaching out to them.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish1·1 month agoAh, you have the antenna issue 😢
I read that it’s possible to fix with a hardware modification, but it’s very difficult.
I find the Pro1 X to be too large for my hands; a phone around 4.5–5" would be ideal.
That’s unfortunate - there aren’t many modern alternatives. Even the F(x)tec is a bit outdated by today’s standards.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish1·1 month agoWhat keyboards have you tried?
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish2·1 month agoI’m aware of musl/Linux, uClibc/Linux and other variants - I just wanted to distinguish them from Android since they all use the Linux kernel 🙂
GNU/Linux is just the most common.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish2·1 month agoI’m guessing cases for this are hard to come by?
Never looked for a case. But it’s a rare beast, I don’t think there is any case for it in the wild 😅
And what about lint/dust/sand
I think it closes quite firmly. So dust doesn’t get inside.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish5·1 month agoGood point! Another issue is that only FUTO and FlorisBoard currently offer FOSS swipe implementations, both of which are in alpha. The AOSP keyboard doesn’t have this feature - it’s exclusive to Google Keyboard.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish3·1 month agoYou can still buy one from backers. Since deliveries only recently finished, many units are still in near mint condition.
Shatur@lemmy.mlOPto Android@lemmy.world•Review of F(x)tec Pro1 X after 3 months of useEnglish5·1 month agoI bought it from someone on the unofficial Discord server. They have a dedicated channel for that. It felt a bit shady, but at least the prices are fair.
I made only a single toot on Mastodon :) You’re replying to a post on Lemmy. I usually post to both Lemmy and Mastodon. They’re federated, this is why you might see both. It’s my Lemmy-specific profile, I use a different profile for Mastodon.
I couldn’t wait, so read all available comics on the website 🙂
Ah, I thought it’s about Valve’s Proton 😅
I have a special trait that generates a reverse command. And store a stack of commands. Here is the source.
I presume you don’t delete the entities on undo but hide them instead?
No, I do a full despawn. Just remember it’s data to spawn again thanks to the mentioned trait.
How do the buttons feel?
The difference is the same as between Bevy’s regular triggers and events. We aim to mirror the Bevy API and simply make it networked.
Events are buffered and pull-style, while triggers are called on commands flush and can target entities and components. Triggers were introduced in Bevy 0.14. Generally, you should use triggers for events that happen rarely and events for things that need to be processed in batches.
Ah, you are right. But I didn’t know where to upload them. What would you use for files?
Love it! I planning to post a text-based review after more use.