The debugging feature of breakpoints still does not (reliably) work.
I did find something that might be a clue though:
When there is a one-line if statement like above, the following break point doesn't break.
if you write:
it does break.
However, in my code breakpoints usually DON'T break at all ...
UNLESS:
when the program is compiling, click the break point (red dot) on and off repeatedly while the compile runs. If you do this, it will (likely) break.
Usually, if it breaks on one line (due to clicking as per above), it will break on ALL break point lines.
Erel, I hope this helps as having the un-reliability on these break points is a pain...
Thanks
Rusty
I did find something that might be a clue though:
B4X:
If x = true then y = y + 1
'breakpoint on next line
If z = true then
...do something
else
...do something else
end ifWhen there is a one-line if statement like above, the following break point doesn't break.
if you write:
B4X:
If x = true then
y = y + 1
End If
'breakpoint on next line
If z = true then
...do something
else
...do something else
end ifHowever, in my code breakpoints usually DON'T break at all ...
UNLESS:
when the program is compiling, click the break point (red dot) on and off repeatedly while the compile runs. If you do this, it will (likely) break.
Usually, if it breaks on one line (due to clicking as per above), it will break on ALL break point lines.
Erel, I hope this helps as having the un-reliability on these break points is a pain...
Thanks
Rusty