#qt

15 posts · Last used 12d

Replying to
I can now go sailing with it too :p I think I got as far as possible for now though. Hopefully the qt people will add support for unix sockets, so the satellite info will be easily available (I suggested that), and also fix the data issues (I will suggest that). If/when that happens, I could make this an actual app, if anyone would be interrested. #postmarketOS #plasma_mobile #qml #qt #linuxonmobile
6
0
0
0
"The mere fact of dealing with people as mass statistical abstractions – hundreds of thousands of Amazon workers, billions of social media users and Google searchers – turns the majority of the world's other humans into phantasms, defective bots whose bothaviors are maddeningly non-deterministic and sub-optimal." #QT https://mamot.fr/@pluralistic/117273997330667202
0
0
0
0
Support for the xx-cutouts-v1 #Wayland protocol landed in #Qt yesterday, which means Qt's SafeArea API will then also work with Wayland compositors supporting this protocol. So far only @phosh@social.phosh.mobi implements this on the compositor side, now #KDE apps will have the means to stay away from display cutouts/notches there automatically, reusing all the work we have done for this on the app and framework level for Android already. #LinuxMobile
58
0
52
0
Last parts to make my desktop wiki Neville base usable is done. Or almost - path to the book is still hard coded but that is for tomorrow to deal with. Still a lot of rough edges though and not even in beta stage (but I will start use it to test it though). And with my new AI-policy (a couple of days before Codeberg changed their) I can continue use CodeBerg :) https://codeberg.org/neville/neville #qt #FreeSoftware #gpl #markdown_editor #markdown
0
0
0
0
Union QtWidgets update: It looks broken, but it's getting there. At least now it's mostly reading data from Union and standing on it's own: It's not just modified Breeze QtWidgets style anymore, but actually reading the CSS and trying it's best to look similar. There are a lot of things still missing. Some elements here are wrong size or are using the QCommonStyle items, which is basically "unstyled Qt" because I have not yet created drawcalls for them. For example scrollbars and tabs. But it's slowly shaping up. I have had to tear this apart and rebuild multiple times due to there not being good information on how to create a QStyle out there. A lot of trial and error and investigating what Breeze is doing. It will need more time. But I really really hope I can get it for 6.8. No promises, but I am really trying. #KDE #Union #QtWidgets #Qt #Linux
5
0
3
0
Replying to

Found the culprit! It was the max_id parameter in /api/v1/timeline/api/v1/timelines/home endpoint.

The code inside Tokodon is as follows:

// maintimelinemodel.cpp

if (!fromId.isEmpty() && !query.hasQueryItem(QStringLiteral("max_id"))) {
        // TODO: this is an *upper bound* so it always is one less than the last post we read
        // is this really how it's supposed to work wrt read markers?
        query.addQueryItem(QStringLiteral("max_id"), fromId);
    }

This code can be searched via max_id keyword. You need to comment out the query.addQueryItem line and Tokodon will work just fine.

I think this is a BUG for the following reasons:

  1. max_id invalidation failure
  2. Lack of retry logic w/o this query item when we know API response (data variable) is empty.
  3. When user logged out, all such data should be deleted as well. A full logout from the app should've reset this data.

A part of me thinks this info was sent by Mastodon server as part of my account info.

@tokodon@kde.social @kde@floss.social

This is in Manjaro Linux fully updated with #Qt 6.10

This was a fun bug to track though :)

#diary #linux #opensource #kde #bugs

2
1
0
1
You've seen all posts