Kabo
@kaboc.bsky.social
iOS and iPad used to have a limited variety of screen sizes. It was a developer- and designer-friendly advantage over Android. Is that not as true anymore?
June 10, 2025 at 2:59 PM
iOS and iPad used to have a limited variety of screen sizes. It was a developer- and designer-friendly advantage over Android. Is that not as true anymore?
I think it happens on 3.24 as well, unless you set ThemeData.useMaterial3 to true.
It's kind of funny they tried to fix the bug but decided not to merge it because it would introduce a breaking change, despite the fact that the bug itself already introduced one.
github.com/flutter/flut...
It's kind of funny they tried to fix the bug but decided not to merge it because it would introduce a breaking change, despite the fact that the bug itself already introduced one.
github.com/flutter/flut...
TextDecoration doesn't inherit text color in Material3 · Issue #129553 · flutter/flutter
Is there an existing issue for this? I have searched the existing issues I have read the guide to filing a bug Steps to reproduce Create a new Flutter app and set useMaterial3 to true Create a text...
github.com
May 30, 2025 at 8:17 AM
I think it happens on 3.24 as well, unless you set ThemeData.useMaterial3 to true.
It's kind of funny they tried to fix the bug but decided not to merge it because it would introduce a breaking change, despite the fact that the bug itself already introduced one.
github.com/flutter/flut...
It's kind of funny they tried to fix the bug but decided not to merge it because it would introduce a breaking change, despite the fact that the bug itself already introduced one.
github.com/flutter/flut...
My point is, I'd rather see stable versions released less frequently than the current rush to release unstable versions to meet events or quarterly cycles.
May 22, 2025 at 8:33 AM
My point is, I'd rather see stable versions released less frequently than the current rush to release unstable versions to meet events or quarterly cycles.
Sadly, just introducing a HoverGestureRecognizer wouldn't make it easier. TextSpan already has onEnter/onExit, with which changing a colour on hover is still hard. Hope it will become as easy as it is with CSS, someday without a third-party package. (I think so as an author of a related package.)
April 11, 2025 at 4:43 PM
Sadly, just introducing a HoverGestureRecognizer wouldn't make it easier. TextSpan already has onEnter/onExit, with which changing a colour on hover is still hard. Hope it will become as easy as it is with CSS, someday without a third-party package. (I think so as an author of a related package.)
An even better/easier way is to use GestureDetector instead of TextSpan + TapGestureRecognizer when there is no specific reason to use TextSpan. This way, you can avoid thinking about how you dispose the recognizer.
April 11, 2025 at 3:30 PM
An even better/easier way is to use GestureDetector instead of TextSpan + TapGestureRecognizer when there is no specific reason to use TextSpan. This way, you can avoid thinking about how you dispose the recognizer.
Just FYI, the Link widget is usually better on the web.
> A widget that renders a real link on the web
pub.dev/documentatio...
> A widget that renders a real link on the web
pub.dev/documentatio...
Link class - link library - Dart API
API docs for the Link class from the link library, for the Dart programming language.
pub.dev
April 10, 2025 at 9:53 AM
Just FYI, the Link widget is usually better on the web.
> A widget that renders a real link on the web
pub.dev/documentatio...
> A widget that renders a real link on the web
pub.dev/documentatio...
Yeah it would be better to stick to the web tech you're already use to. For me, who is not a web person, Jaspr feels straightforward as it is really similar to Flutter, and I don't find it really verbose. Notations used instead of HTML are more concise than they used to be.
January 11, 2025 at 3:19 PM
Yeah it would be better to stick to the web tech you're already use to. For me, who is not a web person, Jaspr feels straightforward as it is really similar to Flutter, and I don't find it really verbose. Notations used instead of HTML are more concise than they used to be.
Do you mean the usage? It's as easy as adding `use-named-parameters: true` to l10n.yaml.
December 28, 2024 at 3:12 PM
Do you mean the usage? It's as easy as adding `use-named-parameters: true` to l10n.yaml.
The UI is so unfriendly. The list shows the customer with the "promo" status, but the next page doesn't show promo entitlements. It is also a weird flow that I need to enter the sandbox page and then uncheck the sandbox checkbox.
December 27, 2024 at 11:05 AM
The UI is so unfriendly. The list shows the customer with the "promo" status, but the next page doesn't show promo entitlements. It is also a weird flow that I need to enter the sandbox page and then uncheck the sandbox checkbox.
Some pitfalls:
a
- The converter is not used for placeholder variables
- Not warned about a wrong type there
b
- DateTime string contains microseconds. Comparing a value in a column with a millisec timestamp can lead to a bug
- QueryRow has DateTimes in UTC, while DataClass has them in local time
a
- The converter is not used for placeholder variables
- Not warned about a wrong type there
b
- DateTime string contains microseconds. Comparing a value in a column with a millisec timestamp can lead to a bug
- QueryRow has DateTimes in UTC, while DataClass has them in local time
December 24, 2024 at 11:57 AM
Some pitfalls:
a
- The converter is not used for placeholder variables
- Not warned about a wrong type there
b
- DateTime string contains microseconds. Comparing a value in a column with a millisec timestamp can lead to a bug
- QueryRow has DateTimes in UTC, while DataClass has them in local time
a
- The converter is not used for placeholder variables
- Not warned about a wrong type there
b
- DateTime string contains microseconds. Comparing a value in a column with a millisec timestamp can lead to a bug
- QueryRow has DateTimes in UTC, while DataClass has them in local time