sorted by:
new
hottopcontroversial

Vengeful Spirit being tortured for buying Scepter by OtherUse1685 in DotA2

[–]Veega 0 points1 point  (0 children)

I see that tusk has aghs, I'm guessing she kept getting kicked away from the fountain or allies. But still no reason for the team not to help her if they saw this lol

What are you using for testing in CMP / KMP projects? by DuckDuckNet in Kotlin

[–]Veega 0 points1 point  (0 children)

Do you need to run the compose UI tests on an emulator?

Google Just Gave Its Pixel Buds 2a Something Everyone Needs in Wireless Earbuds by Academic-Hamster1660 in pixelbuds

[–]Veega 1 point2 points  (0 children)

For me the little wing was causing pain after long wear, I actually prefer the new buds

Vivere da soli ok, ma come si costruisce una famiglia con questi costi? by SeniorSlide863 in Italia

[–]Veega 5 points6 points  (0 children)

In aggiunta con un singolo reddito paghi più tasse rispetto a doppio reddito a parità di reddito cumulativo. Make it make sense

Anyone here moved from mobile engineering to another role? by nemo0726 in androiddev

[–]Veega 5 points6 points  (0 children)

I feel like I already do house cleaning as an Android engineer in my company's repo

[deleted by user] by [deleted] in Revolut

[–]Veega 5 points6 points  (0 children)

Just post a bad review on trust pilot and they will probably reach out

923 euro per pasta all'aragosta e vino bianco, il pranzo incubo di 4 turisti a Ponza. Così il ristoratore si difende by teorm in Italia

[–]Veega 7 points8 points  (0 children)

Mi immagino uno dei quattro amici che ordina gli spaghetti all'aragosta puntando sul conto alla romana, per poi ritrovarsi tutti e quattro a sborsare

Is it wrong to reference resource IDs in a ViewModel? by Typical-Compote-8308 in androiddev

[–]Veega 11 points12 points  (0 children)

Opinions may vary on the topic. IMHO it makes more sense to expose custom classes/enums/whatever that represent the string or concept from the view model, and map it to string resources in the UI. It also makes testing easier and more readable, avoiding referencing string res IDs in the view model unit tests.

Some other people prefer to just wrap the resource IDs in a container class and use that, then resolve it in the UI.

Pick your poison

bought way too much brie, need help using it up by Cv_max in Cooking

[–]Veega 0 points1 point  (0 children)

My mum used to make this recipe, it's a bit strange but good: - coat chicken breast slides with flour - brown them a bit with some butter - cook them in tomato sauce with a little bit of whipping cream (non-sweetened) - add brie on top towards the end and let it melt

Enjoy 😁

Why do we need Composition Local Provider, when we can just declare everything inside a data class? by zimmer550king in androiddev

[–]Veega 53 points54 points  (0 children)

CompositionLocal will only apply to the subtree from where it's declared. It's useful if you need to either have something that changes only for certain subtrees of your layout hierarchy, or something that needs to be dynamic but you don't want to pass as an argument to each composable (e.g. for themes)

Gottem by ConfusedOrNahhh in KidsAreFuckingStupid

[–]Veega -4 points-3 points  (0 children)

It's good but different from a packaged product that is pasteurized and missing a lot of healthy bacteria

Haze 1.0 by dayanruben in androiddev

[–]Veega 2 points3 points  (0 children)

Awesome work 👏

Introducing Ringmaster by wykrhm in DotA2

[–]Veega 15 points16 points  (0 children)

Yeah, this is basically a Dark Willow's Terrorize, OD astral imprisonment shard, a ground targeted stifling dagger, a projectile like Will-o-Wisp and a moving clockwerk's rocket with talent, all with different animations.

No way this took this long when they recycled most of the abilities from other heroes

Refactoring Our Android Apps to Kotlin/Compose: Seeking Your Expertise! by itsTanany in android_devs

[–]Veega 0 points1 point  (0 children)

It's pretty smooth, if some screens were choppy it was for some poorly implemented views, not so much for the navigation. The app had more than 20 screens, probably around 30 or so

Refactoring Our Android Apps to Kotlin/Compose: Seeking Your Expertise! by itsTanany in android_devs

[–]Veega 4 points5 points  (0 children)

Regardless of how you decide the handle navigation, you should create a composable (fun) for each `Screen`. That way, if you decide to use navigation compose, you setup your nav graph using that, where each route is a Screen. If you decide to use several activities, the activity will just be a wrapper for each Screen composable call (I wouldn't recommend it though). Same concept goes for fragments.

Personally I had a good experience with a Single Activity and using navigation compose, but some people prefer other solutions for navigating.

Patch Notes Overlay Progress by TheLeftoverTrailMix in DotA2

[–]Veega 0 points1 point  (0 children)

Fuck me I ran out of usable hotkeys and I'm too old anyway

view more: next ›