sorted by: new top controversial old
[-] FrameXX@discuss.tchncs.de 3 points 5 days ago

RCS is an open standard, but Google's implementation of it isn't AFAIK. That's why there exist no 3rd party RCS client outside of those praised by Google.

[-] FrameXX@discuss.tchncs.de 1 points 1 week ago* (last edited 1 week ago)

Change for the sake of change. At least it seems to be in a good direction.

[-] FrameXX@discuss.tchncs.de 6 points 2 weeks ago

I don't understand why the control panel UI wasn't modernized instead? Would that really be unfeasible? I think it still might have been less work than to maintain 2 coexistent "settings/control panel" apps and migrate from one to another. Sometimes you have to throw out the old code base and start from scratch. But if you do so shouldn't you rather distrubute the result when your finished and not in a half-baked compromise-like state?

[-] FrameXX@discuss.tchncs.de 2 points 2 weeks ago* (last edited 2 weeks ago)

I don't understand why the control panel UI wasn't modernized instead? Would that really be unfeasible? I think it still might have been less work than to maintain 2 coexistent "settings/control panel" apps and migrate from one to another. Sometimes you have to throw out the old code base and start from scratch. But if you do so shouldn't you rather distrubute the result when your finished and not in a half-baked compromise-like state?

[-] FrameXX@discuss.tchncs.de 4 points 3 weeks ago

they never worked very reliably in my experience.

It works perfectly on my phone (Poco X3 NFC). It is probably different from phone to phone.

[-] FrameXX@discuss.tchncs.de 2 points 1 month ago

On Android, from FDroid you can install an app called Seal

I like ytdlnis more.

[-] FrameXX@discuss.tchncs.de 1 points 4 months ago* (last edited 4 months ago)

Lawnchair 2 is no longer under development. The development team always starts to develop a new launcher based on the latest stock launcher every time a new Android version is released (so basically every year). This way the app usually never gets past the alpha or beta builds till they already move on to start from scratch. I don't understand their strategy.

[-] FrameXX@discuss.tchncs.de 3 points 4 months ago* (last edited 4 months ago)

I use Google Lens and I also have to keep Google app installed. I agree it's annoying that they just can't make the apps work standalone. There already is a package that nearly all Google apps dependend on. The package is Google Play Services. Why can't they implement this into Google Play Services as they do with all the other stuff (quick share, find my phone, location services etc...)?

[-] FrameXX@discuss.tchncs.de 24 points 6 months ago

To anyone with a TV running Android I recommend SmartTubeNext: https://github.com/yuliskov/smarttube

[-] FrameXX@discuss.tchncs.de 2 points 6 months ago

I am not aware of any.

25

I know this is probably a primitive topic for most, but I just got into coding in c++ because a simple project I am working on that uses esp8266 which can be programmed using c++. Before this I only had experiemce with python, javascript and typescript.

Now to my problem: I am trying to split my code that is getting longer into multiple files.

I already think that I understand right that each library has a header (.h) file and source (.cpp or .c in case of c) file. The first thing I already have problem with is that as you are defining your functions and classes in the header file and then implementing them in the source file you are repeating yourself with the declarations which is not something I would like. I presume that most IDEs will probably automatically help you with generating or editing the header file automatically as you change code in the source file and I guess I will need to learn to live with it.

Then there's the thing with importing. It may happen that if you create a library it also has some dependencies that it needs to include. But as far as I understand one library shouldn't be included multiple times. So from what I can see most libraries check whether a global variable with an ARBITRARY name that the library chooses itself is not defined and then if that's true it defines that variable to indicate it has been included (the name of the variable is not compketely arbitrary and usually follows LIBRARY_NAME_H but the convention cannot be really relyed on). When the library includes other library it also needs to check whether the variable of that library that is defined on its import is defined. The main file should also probably check this for every library it includes because it can't know what lins were already imported by libs it imported? Am I getting something wrong or is it sometimes ok for some libraries to be included multiple times. There's the #pragma once to handle these situations?

view more: next ›

FrameXX

joined 1 year ago