Hi Graham,
Thank you for the update. Sorry to hear about the flood, I know from personal
experience what that’s like so I really wish you and your family well, and that
you can get your home and life back in to normal very soon..
Paul
> On May 14, 2020, at 03:17, Graham Samuel via
Hi Paul
Sorry for the delay in replying but my house has just been inundated (it
happened on Monday and we are still clearing up! Worst flood in more than 40
years in my French village). Anyway, the bug is registered as 22730. The
problem is acknowledged - as I said in my submission, I’m not
Good point Ben, looks like that was my mistake. I don’t remember where I
learned to use "if tError then”, but what I forgot was that it should have been
testing for a false condition, so “if not tError then” does show the error when
one occurs and skips when no error occurs.
Fixing this
On 2020-05-11 18:18, Graham Samuel via use-livecode wrote:
As I tiny bit of background, the script tries to parse a string that
represents a longitude, copied from a web site. It certainly has some
weird characters in it, but I thought I’d got round then. FWIW, the
string is
004° 31′ 50″ W
I
I set this hare running initially. I really do think there is a bug, because
the thing works when stepped through but not if it’s allowed to run without
interruption. In the stepped-through activity it’s easy to see that tMins does
have a value. In my example it’s 31, or maybe it’s a string of
And re this part:
>> Interestingly this
>>
>> on mouseUp pMouseButton
>> try
>> put (tMins/60) into tMins
>> catch tError
>> if tError then answer "An Error Occurred;" && tError & return &
"tMins =" && tMins
>> end try
>> end mouseUp
>>
>> does NOT through an error or a catch
Hi Andy,
Yes, tMins has to have a value or the statement makes no sense because LC has no
context for what you are trying to do. LC doesn’t know if tMins is a string or
something else.
Rick
> On May 11, 2020, at 4:24 AM, AndyP via use-livecode
> wrote:
>
> I seem to have my posts dropped
Do you have an earlier line where you have set tMins? If it has never been set,
would you export tMins/60 to work?
Aside from that, there was a change in LiveCode 7 or 8, where you could no
longer create a variable on the first line that it is used. You need to have
declared it earlier on.
>
I seem to have my posts dropped at the moment hence this,
I'm seeing the same error
with
on mouseUp pMouseButton
put (tMins/60) into tMins
answer tMins
end mouseUp
button "Button": execution error at line 2 (Operators /: error in left
operand), char 1
Interestingly this
on mouseUp
How does tMins acquire the data? Are you certain it contains what you expect
when you aren’t stepping through the code (and slowing things down)? perhaps a
“put tMins" or “answer tMins” would expose something. (Probably not, but we are
curious!)
—
Scott
> On May 10, 2020, at 12:52 PM, Tom Glod
try putting a space between the left and right of the / and see if you
still get it.
On Sun, May 10, 2020 at 1:10 PM Paul Hibbert via use-livecode <
use-livecode@lists.runrev.com> wrote:
> No replies so far, so I had a few minutes spare and tried to recreate this
> problem, but couldn’t. No
No replies so far, so I had a few minutes spare and tried to recreate this
problem, but couldn’t. No matter what I put into tMins first, even an empty
variable still returned 0, so my suggestion would be to wrap the script in a
try - catch to see what’s going on with the left operand (tMins)
I’m using LC 9.6.0 dp4 and 9.5.1 - this issue is seen in both versions.
I have a script with a very simple statement:
put (tMins/60) into tMins
tMins contains a number, and as expected I get a numeric result, for example if
tMins is 31, I get 0.516667
but ONLY when I step through the script
13 matches
Mail list logo
