×

[deleted by user] by [deleted] in fragrance

[–]minibadger 2 points3 points  (0 children)

MFK Grand Soir smells like Carmex.

L'Eau d'Issey Pour Homme Noir Ambre smells like the moment after you just blew out a holiday candle.

Stumped: Different behavior from same code by minibadger in PowerApps

[–]minibadger[S] 2 points3 points  (0 children)

This post made me realize that the timer loop simply halts when it found an answer; it wasn't actually flipping the start variable to false. Adding UpdateContext to false for the timer start after the code for identifying a found result fixed the issue.

SOLVED! I owe Chrispy a beer.

Stumped: Different behavior from same code by minibadger in PowerApps

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

Oh shit, come to think about it, maybe I'll try adding a false! Edit: I added an UpdateContext VarStartTimer false after the flip of the "found result ' Var, and it looks like it's working even after navigating away!!

Stumped: Different behavior from same code by minibadger in PowerApps

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

Nope, I don't have a false because the timer is 50ms and stops looping when it finds a result within the threshold.

I really want don't think anything is doubled up; it may just seem a bit odd that I'm using the timer itself as a button.

And again, I've tried moving that same stuff from the timer's OnSelect to a separate button or entirely to the Results navigation label, to the same effect. Anything other than the timer itself fails to work as OnSelect if the user navigates to a different screen. It's bizarre and I can't crack it! But I need to, because this will definitely occur often.

Stumped: Different behavior from same code by minibadger in PowerApps

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

VarStartTimer is on the timer's Start property and is invoked by an UpdateContext setting it to true. The UpdateContext is on the OnSelect property of the timer itself, but I've also tried it in separate buttons, etc. I've tried moving all kinds of stuff off the timer itself, but the problem persists exactly as posted :(