B Collins wrote:Here is the code that works
I'm using
Modifier.border(width: Dp, color: Color, shape: Shape)
Modify element to add border with appearance specified with a width, a color and a shape and clip it.
B Collins wrote:
...
Someone any idea?
Tim Holloway wrote:
About the only time I've really felt the lack, in fact, was vocoder stuff. Last time I tried to do a "Battlestar Galactica" Cylon, I couldn't do live input. Had to record and modulate via a DSSI plugin. Vocoder support in software on Linux hasn't been anyone's priority interest.
Tim Holloway wrote:
All based on a $35 device that pulls under 5 Watts of power with a 16GB SD card in it.
B Collins wrote:Hi
I have an activity with four composables in a colum - a text composable, a radiogroup a Textfield and a button
I would like to access the actual states of all three (text/radiobutton/textfield) to send them via the button with Intent/putExtra to another Activity
But it doesn' t work - can't access the variables/states
Ive created for example for the textfield
oder in the radioGroup
If I try to access them from the button composable it says unsolved Reference ...
if I put them outside the composable (a scope higher) it says "composables invocation can only happen from the context of the composable function
if I put it in the surface block - then I got a unsolved reference for e.g. textState
I just want the value and not want to change them - need I state hoisting for it? - or works it another way?
Some help of how to do it would be great
B Collins wrote:Don't understand what you mean
No value passed for parameter 'gameList'" but why
Weyard Wiz wrote:
Giovanni Montano wrote:
This time I see -1 displayed the first time so its working this way now.
glad to see it helped, I guess the changes suggested worked, just android studio lately has some cache problems, so changes are not always picked up immediately, at this regard i suggest you to often to seek for the IDE option`invalidate cache and restart`, you showed some persistence and logical reasoning that could land you to become a senior in few years.
Junilu Lacar wrote:Here's what I find slows you down:
1. Lack of clarity on what needs to be done
1a. No concrete examples
1b. No clear acceptance criteria
2. Lack of understanding of how it is to be done
2a. Lack of mastery of tools
2b. Lack of domain knowledge
3. Waiting for feedback on what you've done.
3a. Manual testing
3b. Asynchronous communication
There are more...
Doc Norton wrote:
Giovanni Montano wrote:The concept of velocity is also linked to estimation. Bad estimations bring low velocity, the scrum master should be more responsible for that. So i would focus on estimation metrics, asking why a ticket evaluated as half a day systematically becomes 3 days, and how to solve this. A qualitative insight will do more than a metric in my opinion
"Bad estimations bring low velocity" - I do not understand the thinking behind this sentence. Can you elaborate?
"I would focus on estimation metrics" - can you give an example of an estimation metric you would use?
Junilu Lacar wrote:
Giovanni Montano wrote:The concept of velocity is also linked to estimation. Bad estimations bring low velocity, the scrum master should be more responsible for that. So i would focus on estimation metrics, asking why a ticket evaluated as half a day systematically becomes 3 days, and how to solve this. A qualitative insight will do more than a metric in my opinion
When you say "bad estimations", what makes them bad?
"how to solve this" -- what's the problem that needs to be solved here? Are the estimates themselves the problem? Are you thinking along the lines of "making better estimates" or something else?
What kind of qualitative insights do you have in mind?
Sami radwan wrote:I see. But that seems to be an advanced topic for a beginner. So as beginner all my objects should be declared final? For example, In Kotlin language I see most tutorials when they creating objects they use val not var which means that the reference is final even in introductory tutorials.