On Wed, Aug 19, 2015 at 8:37 AM, Dr. Hawkins doch...@gmail.com wrote:
On Mon, Aug 17, 2015 at 2:53 PM, Peter Haworth p...@lcsql.com wrote:
There's pretty persuasive evidence now that the shadowed variable bug is
caused by stopping a debug run early.
I'll watch for that, then. But it
On Mon, Aug 17, 2015 at 2:53 PM, Peter Haworth p...@lcsql.com wrote:
There's pretty persuasive evidence now that the shadowed variable bug is
caused by stopping a debug run early.
I'll watch for that, then. But it absolutely has to go; it costs me at
least several minutes, and sometimes a
There's pretty persuasive evidence now that the shadowed variable bug is
caused by stopping a debug run early. Since I trained myself to let debug
run to the end of its natural course, I have not seen the problem.
Hopefully that will help the team figure out the cause and fix it.
On Mon, Aug 17,
On Aug 17, 2015, at 9:17 AM, Devin Asay devin_a...@byu.edu wrote:
On Aug 15, 2015, at 8:37 AM, Dar Scott d...@swcp.com wrote:
Hi, I’m an old-timer who has been away from the list for a while.
I’ve run into a problem and I think it is a LiveCode problem but it might be
an OS X
On Aug 15, 2015, at 8:37 AM, Dar Scott d...@swcp.com wrote:
Hi, I’m an old-timer who has been away from the list for a while.
I’ve run into a problem and I think it is a LiveCode problem but it might be
an OS X problem or some combination.
I’m using 6.7.5.
Very often the hot
Yay! That’s it. Second monitor with top above the main monitor with LiveCode
window top above the same thing.
This might be a bad fix for another bug, the one that blocks a stack from going
higher than the tool bar.
I know how it is about having work to get done and repeating little
On Mon, Aug 17, 2015 at 9:17 AM, Devin Asay devin_a...@byu.edu wrote:
I have seen this and can reproduce it reliably. On a Mac, if you have two
monitors (or more I suppose), and you open a script editor window, it
initially opens on the same screen as your LiveCode IDE; on the main
screen” as
On Aug 17, 2015, at 1:12 PM, Dar Scott d...@swcp.com mailto:d...@swcp.com
wrote:
Mark wrote,
Could be related to bug: http://quality.runrev.com/show_bug.cgi?id=15366
http://quality.runrev.com/show_bug.cgi?id=15366
http://quality.runrev.com/show_bug.cgi?id=15366
Mark wrote,
Could be related to bug: http://quality.runrev.com/show_bug.cgi?id=15366
http://quality.runrev.com/show_bug.cgi?id=15366
I wonder if it is related to bug that existed at one time where one couldn’t
drag a LiveCode window on a second monitor above the top of the main monitor.
I
I think I tried what you said. And afterward things are better.
In the message box I put
set the cursor to watch
then
set the cursor to arrow
I went back to the editor and it was working right. Maybe I did something
else, so I’ll have to see if this routine keeps working when this comes up.
Didn’t work a when it came up again. I must have done something else.
On Aug 15, 2015, at 4:12 PM, Dar Scott d...@swcp.com wrote:
I think I tried what you said. And afterward things are better.
In the message box I put
set the cursor to watch
then
set the cursor to arrow
I went
Now the editor is acting up and I’m getting about 8, -61 in that corner.
My situation is the same as Richards. It is a fixed vertical offset throughout
the time of misbehavior, but I’m not sure whether that fixed amount changes a
little from episode to episode or from stack to stack.
For
On Sat, Aug 15, 2015 at 1:04 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
That might be a clue. Retina screens have a different resolution. Maybe
the engine's calcs are off.
When this bites, the error is a fixed amount. Move the mouse three dots
down, and the point it clicks seems to
In addition to the tests that Mike suggested, it would be interesting to
see what you get back if you ask for the mouseloc in the message box
when you see the problem. Put the cursor up near the 0,0 point of the
editor so you have a visual reference.
I do like the term Gatsby bug. :)
On
Hi, I’m an old-timer who has been away from the list for a while.
I’ve run into a problem and I think it is a LiveCode problem but it might be an
OS X problem or some combination.
I’m using 6.7.5.
Very often the hot spot is off, usually about 50-100 pixels high, for one or
more windows in
On Sat, Aug 15, 2015 at 7:37 AM, Dar Scott d...@swcp.com wrote:
Very often the hot spot is off, usually about 50-100 pixels high, for one
or more windows in the IDE. I usually notice it in the editor where it is
off by 3 lines. Almost always it is just vertical.
I see this on a regular
If its a bluetooth mouse, you might disconnect, and reconnect it and see if
the problem goes away. Or try a wired mouse for a bit and see if it works
better.
I think I also read somewhere that turning off wifi for a min, then back on
can reset the connection to a bluetooth mouse. (some shared
It doesn’t feel like a 3rd party mouse issue to me, but that is only because
the problem is limited to LiveCode stack content. (I have a Macally EcoMouse
hooked up at the moment.)
This occurs in the content of some LiveCode windows. I don’t think I’ve ever
seen it outside of that. It most
makes me wonder.. There are several ways the cursor can change shape while
in use. I wonder if the ball gets dropped somewhere along the way. I've
seen my cursor get stuck occasionally in the pane resize mode, though I
can't reliably reproduce it. When this occurs its nearly always in the
editor.
On Sat, Aug 15, 2015 at 8:58 AM, J. Landman Gay jac...@hyperactivesw.com
wrote:
I haven't seen it yet. Are those who have seen it using a third-party
mouse?
I usually see it on the internal trackpad of a macbook retina
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
On 8/15/2015 2:25 PM, Dr. Hawkins wrote:
On Sat, Aug 15, 2015 at 8:58 AM, J. Landman Gay jac...@hyperactivesw.com
wrote:
I haven't seen it yet. Are those who have seen it using a third-party
mouse?
I usually see it on the internal trackpad of a macbook retina
That might be a clue. Retina
A quick test here looks ok, just as precise on my internal Retina screen and my
external non-Retina monitor.
One thing you could try is to Get Info on LiveCode, and check the box that says
Open in Low Resolution. See if that changes anything.
On Aug 15, 2015, at 4:04 PM, J. Landman Gay
I have a stack that’s doing it. The mouseLoc is like 1, 2, essentially 0,0, in
that corner. For the editor I get something like 27,-9 (menu?), but I’m not
currently having trouble with the editor.
In the stack that has trouble, I have to click well below an option menu, but I
select
I don’t have the retina for Retina. My Mac’s don’t have it. So, in my case,
that is not a factor.
I tried to make a mouseMove test. Unfortunately, I did something that fixed
it. I’m not sure, but I think the first mouseMove message fixed it. But, it
could have been random or the
24 matches
Mail list logo
