E emexes Expert Licensed User Longtime User Oct 18, 2019 #21 Erel said: Is g.INTValue an int variable? Click to expand... Star-Dust said: G is a class that contains only constants. Click to expand... And so, we still don't *know* the type of g.INTValue. Which is why it would be super-helpful to see the actual code involved, eg: emexes said: What is the type of G.INTvalue? How is it initialized to its constant value? Please post at least all the lines of the class that contain the text "INTvalue", even if they are obviously correct ;-) Click to expand...
Erel said: Is g.INTValue an int variable? Click to expand... Star-Dust said: G is a class that contains only constants. Click to expand... And so, we still don't *know* the type of g.INTValue. Which is why it would be super-helpful to see the actual code involved, eg: emexes said: What is the type of G.INTvalue? How is it initialized to its constant value? Please post at least all the lines of the class that contain the text "INTvalue", even if they are obviously correct ;-) Click to expand...
Star-Dust Expert Licensed User Longtime User Oct 18, 2019 #22 emexes said: And so, we still don't *know* the type of g.INTValue. Which is why it would be super-helpful to see the actual code involved, eg: Click to expand... INTvalues is int type. However it doesn't matter because even If I = 1 then didn't work, so the problem is not the type of G.INTvalue. I have already answered above all the questions that you ask because I did not reply to you.
emexes said: And so, we still don't *know* the type of g.INTValue. Which is why it would be super-helpful to see the actual code involved, eg: Click to expand... INTvalues is int type. However it doesn't matter because even If I = 1 then didn't work, so the problem is not the type of G.INTvalue. I have already answered above all the questions that you ask because I did not reply to you.
E emexes Expert Licensed User Longtime User Oct 18, 2019 #23 However it doesn't matter because even If I = 1 then didn't work, so the problem is not the type of G.INTvalue. Click to expand... Agreed, that does shift the probabilities. It is an interesting problem (albeit probably more fun for us than for you, assuming paid work is backing up) I have already answered above all the questions that you ask because I did not reply to you. Click to expand... Thanks, I read them all ;-) I was still keen to see the actual code that (intermittently?) experiences the problem, so whatever subtlety that is possibly causing the issue is not lost through retyping/paraphrasing/simplification, and thus enable reproduction of the problem elsewhere. But I too have paid work backing up, so: no worries either way. It'll be good for everyone using B4I to find out what the cause is.
However it doesn't matter because even If I = 1 then didn't work, so the problem is not the type of G.INTvalue. Click to expand... Agreed, that does shift the probabilities. It is an interesting problem (albeit probably more fun for us than for you, assuming paid work is backing up) I have already answered above all the questions that you ask because I did not reply to you. Click to expand... Thanks, I read them all ;-) I was still keen to see the actual code that (intermittently?) experiences the problem, so whatever subtlety that is possibly causing the issue is not lost through retyping/paraphrasing/simplification, and thus enable reproduction of the problem elsewhere. But I too have paid work backing up, so: no worries either way. It'll be good for everyone using B4I to find out what the cause is.
Star-Dust Expert Licensed User Longtime User Oct 18, 2019 #24 Unfortunately I am out of office for a week and I cannot send the code
M Markos Well-Known Member Licensed User Longtime User Oct 18, 2019 #25 That is frustrating to not be able to explore with a seemingly illogical runtime behaviour. Take my last silly advice and try a fresh iphone to test in debug mode so if the behaviour persists you can look at b4i interface version and libraries and if that is good then look at service packs for the OS. One question does this behaviour happen with other Apps or just this one. The rest is up to you to isolate the cause and hence find the solution.
That is frustrating to not be able to explore with a seemingly illogical runtime behaviour. Take my last silly advice and try a fresh iphone to test in debug mode so if the behaviour persists you can look at b4i interface version and libraries and if that is good then look at service packs for the OS. One question does this behaviour happen with other Apps or just this one. The rest is up to you to isolate the cause and hence find the solution.
Star-Dust Expert Licensed User Longtime User Oct 18, 2019 #26 It also happened with another App but it did it a few times and then the defect disappeared. The strange thing that does not do it in release mode. Anyway I will do the test with another iphone as soon as possible
It also happened with another App but it did it a few times and then the defect disappeared. The strange thing that does not do it in release mode. Anyway I will do the test with another iphone as soon as possible
E emexes Expert Licensed User Longtime User Oct 18, 2019 #27 Markos said: Take my last silly advice Click to expand... emexes said: But your idea could be right. Click to expand... I don't remember any silly advice
Markos said: Take my last silly advice Click to expand... emexes said: But your idea could be right. Click to expand... I don't remember any silly advice
E emexes Expert Licensed User Longtime User Oct 19, 2019 #28 Star-Dust said: The strange thing that does not do it in release mode. Click to expand... That comment triggered a memory of being caught out by compiler optimizations that reorder instructions. That can make things seem weird if you are using breakpoints or stepping, or have code that is optimized out, eg an assignment to a variable that is not later used. Also, For and While loop tests often get moved to the "other end" of the loop. Viewing the intermediate Objective C code might give a clue too.
Star-Dust said: The strange thing that does not do it in release mode. Click to expand... That comment triggered a memory of being caught out by compiler optimizations that reorder instructions. That can make things seem weird if you are using breakpoints or stepping, or have code that is optimized out, eg an assignment to a variable that is not later used. Also, For and While loop tests often get moved to the "other end" of the loop. Viewing the intermediate Objective C code might give a clue too.
