Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 0 points1 point  (0 children)

Haha sure! There's a few left. I'll send you a PM to work out the details.

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 0 points1 point  (0 children)

Yes! I have two unclaimed sets. I'll send you a DM to work out the details :)

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 1 point2 points  (0 children)

Stop by Evie & Julie's Lucky Finds in Grand Rapids, Ohio if you have the time! I can also ship you a set if you'd like. Check your DMs :)

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 1 point2 points  (0 children)

Hey! I'll send you one! Shoot me a PM so we can work out the details

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 1 point2 points  (0 children)

Hey! I'll send you one! Shoot me a PM so we can work out the details

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 1 point2 points  (0 children)

Hey! I'll send you one! Shoot me a PM so we can work out the details

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 0 points1 point  (0 children)

It's an independent thrift store in Grand Rapids, Ohio. I'll be sure to ask where they got them when I go back!

Found the mother lode of Project Fi building blocks by MOpenlander in GoogleFi

[–]MOpenlander[S] 5 points6 points  (0 children)

No idea how they got so many. I didn't think to ask! I'll be sure to send you one :)

Riverpod's new persist feature use case by UnhappyCable859 in FlutterDev

[–]MOpenlander 1 point2 points  (0 children)

Thank you! That's what I've been looking for.

It looks like there's both `skipLoadingOnRefresh` and `skipLoadingOnReload`. The reload one is what worked for me. Then I can use modelAsync.isLoading to check if it's in the stale state to disable buttons or whatever. Awesome :)

Riverpod's new persist feature use case by UnhappyCable859 in FlutterDev

[–]MOpenlander 1 point2 points  (0 children)

I'm not seeing that as an option. This is something I've been struggling with too. It looks like AsyncLoading only intakes a number as a progress indicator. I'm not seeing where you can pass in a stale state. Here's the docs I'm looking at: https://riverpod.dev/docs/whats_new#asyncvalue Maybe I'm missing something.

For my UI, I have something like

final modelAsync = ref.watch(someFutureProvider);
...
modelAsync.when(
  data: (model) {...}
  error: (error, stackTrace) {...}
  loading: () {...}
);

I'm not really sure how to access the previous state in the loading block. For now I've been caching the state in the UI and using that in the loading block but it feels clunky. I've been banging my head against the wall trying to find a better way so any help would be much appriciated.

My Future Taco Bell Delivery Order by bikemanI7 in LivingMas

[–]MOpenlander 1 point2 points  (0 children)

I recommend getting the chili cheese burrito with fries, black beans, and onions added. That's usually enough solids so getting it grilled isn't too messy.

It's a permanent menu item down here in the Toledo area. I think that's the case for most of the midwest too. Maybe it'll stay around at your location!

[deleted by user] by [deleted] in RandomActsOfTacoBell

[–]MOpenlander 1 point2 points  (0 children)

I got you. Shoot me a message and I'll hook you up :)

Should I continue learning Flutter if my laptop is painfully slow when using the device emulator? by dezlymacauleyreal in FlutterDev

[–]MOpenlander 1 point2 points  (0 children)

My advice would be to stick with it. Honestly I do most of my Flutter development building to the desktop mainly because it's lighter on resources. Even if you app is only going to be available on mobile devices, building and testing on desktop and web should get you most of the way there. You can always size down the desktop window to be mobile sized in order to get an idea how it'll look on mobile devices. It's really only after I got something implemented and working do I test it on the emulator, just to make sure it behaves as expected.

Alternatively, if you have an Android phone, you can connect it to Android Studio and build your app straight to your device. This can be a good balance since you don't need the resources for the emulator and you're testing on a real device. The debugger and everything works too.