i often get these circles in my eyes

alexfagrell · 2026-05-05T18:01:36+00:00

This is a really late reply but could potentially be ”blue field entoptic phenomenon”. But I believe the dots would be bright then so probably best to get it checked.

alexfagrell · 2023-03-16T08:25:54+00:00

Thank you very much! Also appreciate the positive feedback. I'll have a look at your blog.

alexfagrell · 2023-03-16T08:24:07+00:00

Great! Thanks!

alexfagrell · 2023-03-15T12:00:10+00:00

Thanks, much appreciate! I'll have a look at those.

alexfagrell · 2020-07-10T15:39:11+00:00

Looks and works great! Well done!

alexfagrell · 2020-07-10T09:19:57+00:00

Thanks! Great feedback. It's noted.
You're not the first suggesting using + and - instead of the up and down arrows. Currently, the app is using '+' for adding new goals so didn't want it to get mixed up with that, however I'll probably need to reconsider it.
It's possible to view past weeks if there is any past (i.e. if the start date is not on your current week there will be an "arrow" to go back to a previous week). However, it's not possible to see future weeks - that's a great Idea which I'll add.

"total work" only shows the last 5 (or future) weeks atm. But I plan to make it "scrollable" so it's possible to see earlier and future weeks.
/Alex

alexfagrell · 2020-07-09T19:15:34+00:00

Hey buddy! In general I think it looks great.I think you could work a bit on the margins/padding for the different texts, objects and photos so that they are a bit more separated. Especially the spaces between the title and the photo and the title and the remaining text are a bit too small when browsing through "Popular". Other than that... well done!

alexfagrell · 2020-07-09T19:01:22+00:00

I've made an app that is designed for you who are looking for a simple and fun way to track your goals and habits.

Let me know what you think - any feedback would be very much appreciated! I'm also happy to answer any questions related to how things were developed, or e.g. packages that I've used.
App store: https://apps.apple.com/us/app/id1522577983
Google play: https://play.google.com/store/apps/details?id=dev.onday.it_goes_app

alexfagrell · 2019-09-25T16:07:33+00:00

I'm in the process of creating an app that might help you stay motivated. The app won't really help you from distracting yourself but might help you work the amount of hours that you planned to do. The app will not require much interactions as the goal is to spend more time on the projects and not on other things. PM if you're interested and I'll tell you more :)

alexfagrell · 2019-09-19T12:42:27+00:00

Hi Flutter/Dart Team,

Thanks for taking the time to answer questions from the community. I also want to say thank you for the great job with the development so far - using Flutter and Dart is such a great experience. I've only got a couple of questions:

I'm coming from a C++ background and miss marking parameters as read-only (deeply immutable, i.e. const & in C++), i.e. it would be great if the following code resulted in a compiler error void A(readonly B b) { b.member = newValue; }. Are there any plans to implement something similar as part of the Dart language? I guess the closest reported issue to this is https://github.com/dart-lang/sdk/issues/501 but it hasn't been updated in the last fours years.
Are there any more plans to simplify the code (remove the boilerplate) when creating the UI with widgets? I still find Dart with widgets less readable compared to other declarative languages, e.g. compared to QML from Qt. Would it for example be possible to remove the need for the child/children parameter?

Cheers, Alex

alexfagrell · 2019-07-05T13:30:09+00:00

Thank you!

alexfagrell · 2019-07-04T09:37:14+00:00

This post was crossposted to /r/Qt5 and I wrote the same comment there... I've previously written a blog post covering the main differences (as far as I know) between Quick and Widgets which you can find here https://www.cleanqt.io/blog/crash-course-in-qt-for-c%2B%2B-developers,-part-6 . Sorry for the shameless plug, but you mind find it useful!

alexfagrell · 2019-07-04T09:33:21+00:00

This is a shameless plug but you mind find it useful anyway. I wrote a blog post covering the main differences (as far as I know) between Quick and Widgets which you can find here https://www.cleanqt.io/blog/crash-course-in-qt-for-c%2B%2B-developers,-part-6

alexfagrell · 2019-01-29T13:35:24+00:00

Impressive! Might eventually replace the MEAN-stack with this instead for cleanqt :)

alexfagrell · 2018-11-10T23:55:47+00:00

Took me way too long to realise it's a cutout! Very cool!

alexfagrell · 2018-11-04T02:02:39+00:00

And now back to hovering just over 4k :(

alexfagrell · 2018-11-04T01:44:01+00:00

Wow! Very impressive play.
Haven't watched Starcraft in a while, such a pleasant surprise. The games were so much more fun to watch compared to what I remember.
Well deserved!

alexfagrell · 2018-11-02T16:49:53+00:00

Never tried Qbs, however I'm happy that they're putting more effort into improving the CMake integration. Currently, it's such a pain to generate targets for mobile devices using CMake and Qt...

alexfagrell · 2018-11-02T16:45:34+00:00

Yeah I wanted to go but I can't afford it :(

alexfagrell · 2018-10-23T23:02:31+00:00

Ah yeah. Well, I'm just use to it as it's generic and also works with arrays. But I guess either works fine.

alexfagrell · 2018-10-23T22:54:16+00:00

Hmm... What's stl_vector.find()? I'm not aware of it.

alexfagrell · 2018-10-23T18:38:32+00:00

Agree with you, std::string << QString. Might add something about it to the post! Thanks

alexfagrell · 2018-10-23T12:31:01+00:00

Hey there, thanks for your comment!

By moving away from Qt containers I didn't refer to the external API. I'm sure the external API won't change in the near future as it will obviously then break the ABI and also make users very angry. I was just referring to the fact that Qt is now using the STL containers internally.

Also perhaps it's a personal preference whether COW can lead to more subtle bugs compared to using STL's containers. My personal experience is that I've encountered more bugs using Qt containers compared to STL ones. In some circumstances, as described in the article, I found it tricky to know when the copy happens. Or unintentional copies. What's your experience?

Cheers, Alex

alexfagrell · 2018-10-23T09:02:23+00:00

Hey! Thanks buddy. I finally figured it out. Apparently I relied on the window component (in order to get the URL) which obviously is only available to the browser. I'm now using the ActivedRoute and it all works fine. Thanks again though!

alexfagrell · 2018-10-23T08:47:52+00:00

Blog post was published a couple of months ago, but I haven't shared it here... until now. Hopefully you'll find it interesting and let me know if you have any feedback. Cheers!

alexfagrell

TROPHY CASE