How about attacking stack depth?
Make a series of variables for your intermediate results, and pass intermediate results from variable to variable, to lower stack depth requirement.
How about attacking stack depth?
Make a series of variables for your intermediate results, and pass intermediate results from variable to variable, to lower stack depth requirement.
Anke â Right Click/Do It for the âSelect Listâ block returns âxyzâ, for the âfragment_dataâ block returns ââ. Hmmmm
Maybe youâre failing to apply Do It to the set label.Text To block?
I'm starting to think you're kidding us. ![]()
Do you have screen session recording software like Loom (free) to show us the sequence of operations?
OK, when I âright-click-and-Do-Itâ on the split_3_btn âSet fragment_dataâ green block (ABGâs âdo it firstâ), I see no resulting comment in the Blocks Editor but the correct result (xyz) appears on my tablet! Same thing for the âSet length_dataâ block (no comment but correct display on tablet). An analogous action on the other two buttonsâ blocks has the same effect of putting the correct answer on the tablet. So what still DOESNâT work is eliciting the correct data on the tablet by pressing the actual âThree Splitâ button!? Iâve looked carefully and donât see any difference on the Designer page between the three buttons. Does this help?
I tried adding another fresh button and copying the blocks for the third split to the new button â still didnât work.
Browser ? - should be Chrome or Firefox (clutching at straws nowâŚ)
Hereâs something to investigate âŚ
Is there a time delay between assigning the fragment_data.Text value in the button Click, and the availability of the fragment_data.Text value in the following statement?
That problem would not manifest if steps were done manually.
(edit - I wonder if such behavior were a side effect of some kind of âoptimizationâ at the O/S level?)
(edit #2 - To test this hypothesis, add a local variable as the output of the long split sequence, then assign that into the fragment.Text and then assign the length of the temporary variable to the other output .Text field. This would avoid reverse flow from the GUI during an Event.)
TIMAI2 â Iâm using Chrome.
ABG â I donât understand what youâre suggesting.
Good ideas, but no luck. Button 3 still doesnât work. âDo Itâ on the local âtempâ variable generates an âUnbound Variablesâ pop-up that wants me to enter a value!? However, although âDo Itâ on the âInitialize local tempâ block fails to generate any responsive comment, the correct results now appear on the tablet display â both xyz and 3 (kinda like what weâve seen before).
Thanks Anke, but nope. As before, except now the âDo Itâ tickle doesnât even produced the correct result on the display like it did previously.
Clearly there is a mystery here and things I donât understand, but youâve cleared up my initial question. Iâm assuming from your responses and suggestions that my original program and your subsequent modification all SHOULD have worked (and indeed, they do in your hands). This issue would therefore appear to be a function of my devices â laptop, wifi, and/or tablet â and I will admit that they are all somewhat old and out-of-date. Rather than consuming any more of your time, I suggest we move on and file this under âThings that make you go Hmmmâ. I truly appreciate the time and effort you all extended to help me with this.