On 13 Nov 2014, at 20:09, J. Landman Gay jac...@hyperactivesw.com wrote:
On 11/13/2014, 2:27 AM, Mark Schonewille wrote:
Really, why wouldn't it be realistic to pay a bunch of students for a
few hours of beta-testing (or should I say alpha-testing) some time in a
development cycle?
There's
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Neil Roger
Sent: Thursday, November 13, 2014 2:59 PM
To: How to use LiveCode
Subject: Re: hair-pulling frustration
Hi Richard,
I've
OK, so you mean this:
revDataFromQuery(,,17,SELECT * FROM vader_darth__001_dna;)
revDataFromQuery is a function, you need to either put it or get it or
set a cprop to it. If I type the above statement into the message box I
get exactly the same error as you whether there's a semicolon or
The way I see things, RunRev is not an overly large company. To remain solvent
(something that benefits us all) they probably have to prioritize what they can
and cannot do. In House testing of every possible scenario cannot be one of the
do’s. Frankly I am thrilled at the progress made since
On Fri, Nov 14, 2014 at 9:21 AM, Peter Haworth p...@lcsql.com wrote:
revDataFromQuery(,,17,SELECT * FROM vader_darth__001_dna;)
Somehow, an earlier version of my reply was sent. Here's what I meant to
send.
Knowing that you used the message box makes a big difference, Everyone who
has
On 11/14/2014, 11:58 AM, Peter Haworth wrote:
My feeling is that something changed in the message box parsing routines
and the semicolon is being taken as a separator between two statements.
A semicolon in any script is interpreted as a line ending, except when
within quotation marks. If the
On 11/13/2014, 10:26 PM, Geoff Canyon wrote:
On Thu, Nov 13, 2014 at 3:10 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
I blame myself for the omissions (except when Richard G. forgives me.) :)
Bless me Richard, for I have sinned. It has been two weeks since my last
bug report. Since
Hah hah! I would have used “For all permutations” instead!
Bob S
On Nov 14, 2014, at 10:47 , J. Landman Gay
jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote:
LOL! Okay.
Our Kevin, who art at RunRev,
Hollowed be thy frame
By coding done
Yet still undone in engine,
As it is in
Right, it looks like something in the message box message box
interpretation scripts changed between the various releases I tested.
I guess I should file a bug report.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin
On 11/14/2014, 1:39 PM, Bob Sneidar wrote:
Hah hah! I would have used “For all permutations” instead!
Ooh. Like. It is revised:
Our Kevin, who art at RunRev,
Hollowed be thy frame
By coding done
Yet still undone in engine,
As it is in IDE.
Give us this day our weekly upgrade
And forgive us
On Fri, Nov 14, 2014 at 10:38 AM, J. Landman Gay jac...@hyperactivesw.com
wrote:
A semicolon in any script is interpreted as a line ending, except when
within quotation marks. If the example failed (where the semicolon is
within the quotes) then that would be a problem with the scripts that
Can you send us the relevant script lines? So far, it has worked in my
script with or without semicolons in various versions from 5.5 and up in my
testing so there must be something different in your script and mine.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser
If this were a realistic option, Edinburgh would have permanent testing
staff. The language, syntax and interaction permutations are simply too vast
for any automated testing whether by machine or human. As Richard G says,
ensure your own software is robust with each new version and log any
Really, why wouldn't it be realistic to pay a bunch of students for a
few hours of beta-testing (or should I say alpha-testing) some time in a
development cycle? I'm sure they could detect the bugs that every other
developer would detect right-away, but without frustrating those
developers
Hello,
I do agree that more testing (non automatic testing) should be made before
releasing a commercial product.
But I’m not sure RunRev will listen.
When the CEO says:
I really would urge everyone in our community to move to 7 as soon as
possible. We spent 18 months building it and
I'll give you 2 cents for that, Éric. I also don't think that RunRev
will listen. Yet, I think a company should not rely on its user base for
testing. A company can't blame its user base for not testing, if
something appears not to work, but a user base can blame the company for
delivering
Geoff Canyon wrote:
I'm just expressing frustration about barriers to reporting bugs.
For example, a login is required to file a bug...
...as it is for this list, which the bug system is being compared to.
Just about any publicly-accessible venue that displays user-generated
content will
HI Richard,
I have a suggestion for this, having just read the entire thread.
I too find it hard at times to get the time to even write here let alone
fill out a report on Bugzilla. And then to go through the process of
creating a recipe or sample stack. The reason for this is obvious, that
like
Éric Miclo wrote:
I do agree that more testing (non automatic testing) should be made
before releasing a commercial product.
But I’m not sure RunRev will listen.
When the CEO says:
I really would urge everyone in our community to move to 7 as
soon as possible. We spent 18 months building
Sean Cole wrote:
I have a suggestion for this, having just read the entire thread.
How about this approach (which is nothing new - Apple use a similar
system and I personally have had much success with it). In the
LiveCode app itself (both Commercial and Community) in the Help menu
should be a
On 13/11/14 18:22, Richard Gaskin wrote:
snip
Software is complex stuff.
I don't think it was a mistake for Tim Cook to suggest we upgrade our
Apple devices to the latest software version which later bricked some
phones, and I don't think it was a mistake for Kevin to suggest that
we use
On 11/13/2014, 1:50 AM, Geoff Canyon wrote:
if the requirements are causing Jacque to fail to
report a bug, that's a huge issue.
Well, to be fair, it doesn't always prevent me from reporting things. If
I have time I do create an example stack, especially if my current work
can't proceed
On 11/13/2014, 2:27 AM, Mark Schonewille wrote:
Really, why wouldn't it be realistic to pay a bunch of students for a
few hours of beta-testing (or should I say alpha-testing) some time in a
development cycle?
There's no way a few hours would catch much in a system as complex and
large as
On Wed, Nov 12, 2014 at 11:22 AM, Peter Haworth p...@lcsql.com wrote:
On Tue, Nov 11, 2014 at 3:13 PM, Dr. Hawkins doch...@gmail.com wrote:
SELECT * FROM sometable; worked before the change with SQLite. Now,
it
is necessary to remove the semicolon.
I just tried this using LC 5.5.4
On 11/13/2014, 12:20 PM, Richmond wrote:
I believe there needs to be:
1. a set list of incentives on offer for bug detection.
I wonder if it would be possible to extend a user's license for a short
period after a certain number of verified bug reports has been submitted.
For community
Hi Richard,
I've attempted to replicate the semicolon issue without any success.
This could be why we have not come accross it during testing in-house.
The script that I tested with is-
global gConnectionID
on mouseUp
global gConnectionID
if gConnectionID is not a number then
On Thu, Nov 13, 2014 at 11:09 AM, Dr. Hawkins doch...@gmail.com wrote:
revDataFromQuery(,,17,SELECT * FROM vader_darth__001_dna;)
yields
Message execution error:
Error description: value: error executing expression
Hint: )
While if I leave out the semicolon, it gives me all the data in
On Thu, Nov 13, 2014 at 1:06 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
On 11/13/2014, 1:50 AM, Geoff Canyon wrote:
if the requirements are causing Jacque to fail to
report a bug, that's a huge issue.
Well, to be fair, it doesn't always prevent me from reporting things. If I
have
On 11/13/2014, 2:32 PM, Geoff Canyon wrote:
I didn't mean to imply that the system is preventing you from entering any
bugs; I'm saying that given your many years of experience and dedication to
the platform if the system prevents you from entering even a single bug,
that's bad.
The thing is,
[mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Neil Roger
Sent: Thursday, November 13, 2014 2:59 PM
To: How to use LiveCode
Subject: Re: hair-pulling frustration
Hi Richard,
I've attempted to replicate the semicolon issue without any success.
This could be why we have not come accross
Richmond wrote:
What might do some good is point out to RunRev that when they
released their Open Source version of LiveCode they undertook
to be more touchy-feely and more responsive to their users
. . . and, just possibly, they may be falling short of this.
Perhaps. What should
Note to self :
I am *not* getting involved in this thread.
I am *not* getting involved in this thread.
I am *not* getting involved in this thread.
I am *not* getting involved in this thread.
I do *not* have time to read, never mind get involved in, this
thread. :-)
OK.
On Thu, Nov 13, 2014 at 11:58 AM, Neil Roger n...@livecode.com wrote:
Both the inclusion and exclusion of the semi-colon return data as
expected. If possible, could you supply a stack for me to test with and I
will happily look into this further.
I'll see what I can pop together.
And now, I
Alex Tweedly wrote:
It would seem touchy-feely for there to be more response on this list
from RR.
I tend to feel the same, but as with so many things it's a balancing act
- after all, one of the reasons we want them here is to tell them to go
away so they can spend their time fixing bugs.
I just tried it under 7.0 and same result - no problems with or without the
semicolon. There must be something else going on in Dr Hawkins code.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin
On Thu, Nov 13, 2014 at 4:32 PM, Peter Haworth p...@lcsql.com wrote:
I just tried it under 7.0 and same result - no problems with or without the
semicolon. There must be something else going on in Dr Hawkins code.
The ones I posted today were typed into the message box!
--
Dr. Richard E.
On Thu, Nov 13, 2014 at 3:10 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
I blame myself for the omissions (except when Richard G. forgives me.) :)
Bless me Richard, for I have sinned. It has been two weeks since my last
bug report. Since then I wrote three undocumented functions and one
I agree. I have always felt that RunRev should occasionally hire one or
two people for beta-testing. They could test new releases before they
are labelled pre-release. This would cost only a little money and safe
hundreds, if not thousands of people lots of frustrations.
--
Best regards,
Jacque,
I teach a class for free and if one student doesn't understand one word,
I spend some extra time with that student to make sure he or she
understands it. If I didn't do this, I would lose the students one by
one and in the end I'd be the only one understanding the lesson. So, I
guess
On Tue, Nov 11, 2014 at 11:15 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
An unresponsive IDE was mentioned. The editor and the IDE can both become
frozen if you are debugging and you try to do something else without
exiting debug mode. Not only can you not type into the editor, which
On 11/12/2014 04:25 PM, Mark Schonewille wrote:
Jacque,
I teach a class for free and if one student doesn't understand one
word, I spend some extra time with that student to make sure he or she
understands it. If I didn't do this, I would lose the students one by
one and in the end I'd be
Let me just say that for some folks who do not have enough time to report bugs,
they certainly have found an abundance of time to post their frustrations to
this list! Just sayin’.
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
On 12/11/14 19:50, Bob Sneidar wrote:
Let me just say that for some folks who do not have enough time to report bugs,
they certainly have found an abundance of time to post their frustrations to
this list! Just sayin’.
Bob S
___
Ooo! Bi*chy :)
On Tue, Nov 11, 2014 at 3:13 PM, Dr. Hawkins doch...@gmail.com wrote:
SELECT * FROM sometable; worked before the change with SQLite. Now, it
is necessary to remove the semicolon.
I just tried this using LC 5.5.4 (prior to the SQLite library change) and
LC 6.6.2 (after the SQLite library
Can't quite agree with that simplistic analysis. There are many Commercial
users who test the dp and rc releases, especially if they contain fixes for
bugs they reported.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin
On Wed, Nov 12, 2014 at 11:50 AM, Bob Sneidar bobsnei...@iotecdigital.com
wrote:
Let me just say that for some folks who do not have enough time to report
bugs, they certainly have found an abundance of time to post their
frustrations to this list! Just sayin’.
It takes far less time to send
Geoff Canyon wrote:
It takes far less time to send an email than it does to file a bug.
If you just want to type, the difference is negligible.
If you want to actually see the bug fixed, the ROI for filing a bug
report is much higher. ;)
--
Richard Gaskin
LiveCode Community Manager
Any positive value is higher than zero, so sure. I'm just expressing
frustration about barriers to reporting bugs. For example, a login is
required to file a bug, and the bug submission form all but requires an
example stack. I understand the desire to get clear, actionable bug
reports, and I
WINE has an interesting release model: https://www.winehq.org/
Every 2 weeks, dead on time, they release another beta version,
and whenever (and 'whenever' can mean anything between 2 weeks to 2
years) they
release a stable version.
The beta versions are labelled like this: 1.7.1, 1.7.2 and
I can't help but wonder what it would take to get runrev to follow normal
practice and actually get something to alpha level before calling it a
developer preview, beta by a release candidate (ok, that still wouldn't
be normal), and working rather than early beta before release.
If I sold
On 11/11/14 21:25, Dr. Hawkins wrote:
I can't help but wonder what it would take to get runrev to follow normal
practice and actually get something to alpha level before calling it a
developer preview, beta by a release candidate (ok, that still wouldn't
be normal), and working rather than early
Dr. Hawkins wrote:
OK, I'll stop venting, but the amount of time I'm losing to bugs that never
should have seen a public preview is getting increasingly frustrating.
I agree, which is why it benefits no one more than ourselves to test our
work with pre-release versions.
The SQLite issue may
On 11/11/14 21:55, Richard Gaskin wrote:
Dr. Hawkins wrote:
OK, I'll stop venting, but the amount of time I'm losing to bugs that
never
should have seen a public preview is getting increasingly frustrating.
I agree, which is why it benefits no one more than ourselves to test
our work with
Hi Dr. Hawkins,
The whole computer industry is changing too rapidly now.
Their is no such thing as “stable” as a result.
What everyone wants is a “stable” OS, a “stable” language, a
“stable” database, and stable hardware platforms to go with it all.
If we had all of that, we’d already have a
On Tue, Nov 11, 2014 at 11:55 AM, Richard Gaskin ambassa...@fourthworld.com
wrote:
Dr. Hawkins wrote:
OK, I'll stop venting, but the amount of time I'm losing to bugs that
never
should have seen a public preview is getting increasingly frustrating.
I agree, which is why it benefits no
On Tue, Nov 11, 2014 at 11:25 AM, Dr. Hawkins doch...@gmail.com wrote:
In addition to the others I've mentioned here an in other recent posts, the
recompile of sqlite is not quite compatible with the old, and behaves
differently. For example, a semicolon at the end of an entry without
On Tue, Nov 11, 2014 at 11:55 AM, Richard Gaskin ambassa...@fourthworld.com
wrote:
The SQLite issue may be more related to the new SQLite code base than with
LiveCode. I can't say specifically - Mr. Haworth, what do you find with
that?
Just asked for an example and will check it out.
Pete
Richmond wrote:
On 11/11/14 21:55, Richard Gaskin wrote:
I agree, which is why it benefits no one more than ourselves to test
our work with pre-release versions.
That is, of course, very true.
Another idea that might not be bad, is to slow down the releases so
there is more time for
On 11/11/14 22:59, Dr. Hawkins wrote:
snip
I really can't give up any significant portion of my coding time to do
livecode's work for them; these are things that are so basic that they
never should have seen a release to the public.
I'm afraid, Richard Gaskin et al, the above is going to be
On 11/11/14 23:16, Richard Gaskin wrote:
Richmond wrote:
On 11/11/14 21:55, Richard Gaskin wrote:
I agree, which is why it benefits no one more than ourselves to test
our work with pre-release versions.
That is, of course, very true.
Another idea that might not be bad, is to slow down the
On 11/11/2014, 3:16 PM, Richard Gaskin wrote:
So while we can't be expected to test everything, if we only test our
own apps with new builds that's usually all we need for our own work.
Collectively, if we call just ensured that new features get implemented
in ways we need, we'll all have what
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 11:55 AM, Richard Gaskin wrote:
I agree, which is why it benefits no one more than ourselves to test
our
work with pre-release versions.
Two problems, though:
1) One can *either* stay with 5.5, *or* use any of the new features.
Without maintaining
On 11/11/14 23:34, Richard Gaskin wrote:
snip
Being in touch with them fairly regularly, I can say with confidence
that it's not like they're all sitting at the beach drinking Mai
Tais. Heck, it's Edinburgh - is it even sunny enough to go to the
beach? :)
snip
While I know they are not
J. Landman Gay wrote:
What usually stops me is the need to create a separate, stripped-down
stack to demonstrate a more complicated bug. I completely understand
the need for this, especially in my case where the original stack is
huge and complex, and I wouldn't expect RR to plow through all
On 11/11/2014, 3:23 PM, Richmond wrote:
Several times I have stated that in my opinion RunRev are being swept
along into a sort of feature bloat which prevents them
from sorting out little 'niggles' in existing features. I se no reason
to change that opinion.
Suppose while teaching English,
The student example
Your comment is interesting BUT;
Instructors need to test the curricula before, during and after the
instruction.
The question is, is it the instruction, the testing or the student having
the problem. It all comes back to the testing. The teacher who does not
test the
Richmond wrote:
Obviously Dr Hawkins is not over-enamoured of the Open Source
theory: LiveCode is paid for in a different way [the I'll
scratch your back if you'll scratch mine way] than the
'standard' commercial way [I pay you, and you do ALL the work].
I think you and I may be a rare breed.
On Tue, Nov 11, 2014 at 1:09 PM, Peter Haworth p...@lcsql.com wrote:
I rarely, if ever, try to execute multiple SQL statements in one
revDatabasexxx so haven't seen that particular problem. Could you give an
example? I'd like to check it out as I don't want to get hit by the same
bug.
I
On Tue, Nov 11, 2014 at 1:34 PM, Richard Gaskin ambassa...@fourthworld.com
wrote:
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 11:55 AM, Richard Gaskin wrote:
I agree, which is why it benefits no one more than ourselves to test our
work with pre-release versions.
Two problems, though:
1)
On Tue, Nov 11, 2014 at 1:23 PM, Richmond richmondmathew...@gmail.com
wrote:
Obviously Dr Hawkins is not over-enamoured of the Open Source theory:
LiveCode is paid for in a different way [the I'll scratch your back if
you'll scratch mine way] than the 'standard' commercial way [I pay you,
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 1:34 PM, Richard Gaskin wrote:
I'd like to raise these concerns with Ben and Kevin at my next
meeting.
It would be very helpful if you could point me to the bug reports that
describe these issues.
That's the problem. These are at a level that
On Tue, Nov 11, 2014 at 4:38 PM, Richard Gaskin ambassa...@fourthworld.com
wrote:
Any other specific issues you feel are show-stoppers may well be worth
looking into, and I'd be happy to help if I can. But to do that I'd need
to know what they are.
That the IDE doesn't work?
I filed those
Folks:
Just to chime in on this. I’ve been using version 7.0 for a couple of months.
No problems. I’m not using many of the new features like unicode, but have
found the IDE working fine for my purposes, so far. The slowdown in some
operations has affected me, though. Picking out a byte from a
Hi Richard,
on Tue, 11 Nov 2014
Richard Gaskin wrote:
[snip]
On the other issues, can you share the
bug report numbers so we can follow them?
Does exist an automatic way to post
every new bug report in this mail list?
Could bugzilla do this?
In this way, every bug will be noticed and
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 4:38 PM, Richard Gaskin wrote:
Any other specific issues you feel are show-stoppers may well be worth
looking into, and I'd be happy to help if I can. But to do that I'd
need
to know what they are.
That the IDE doesn't work?
I'll run a search
On Nov 11, 2014, at 4:38 PM, Richard Gaskin ambassa...@fourthworld.com wrote:
Any other specific issues you feel are show-stoppers may well be worth
looking into, and I'd be happy to help if I can. But to do that I'd need to
know what they are.
Hi Richard,
Thanks for taking this on.
On Nov 11, 2014, at 5:24 PM, Richard Gaskin ambassa...@fourthworld.com wrote:
There was a recent comment about shadowed name warnings in the Facebook group
recently, but that seemed related to turning on the feature to warn about
those (Prefs - Script Editor - Strict Compilation Mode). The
On 12/11/2014 11:00 am, Dr. Hawkins doch...@gmail.com wrote:
LiveCode's developer previews simply execue (nightly snapshot that
executed), the RC are alpha quality, the 5.5 series are late beta, and the
6.x and 7.x releases are early beta.
I think that¹s a bit harsh. There are problems with
On Tue, Nov 11, 2014 at 5:24 PM, Richard Gaskin ambassa...@fourthworld.com
wrote:
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 4:38 PM, Richard Gaskin wrote:
Any other specific issues you feel are show-stoppers may well be worth
looking into, and I'd be happy to help if I can. But to do
On Tue, Nov 11, 2014 at 5:31 PM, Terry Judd terry.j...@unimelb.edu.au
wrote:
On 12/11/2014 11:00 am, Dr. Hawkins doch...@gmail.com wrote:
LiveCode's developer previews simply execue (nightly snapshot that
executed), the RC are alpha quality, the 5.5 series are late beta, and the
6.x and 7.x
OK, I'll try with and without multiple statements in both versions.
I do want to double check that you're not trying to access an SQLite
database over a network because you WILL have major problems if you are :-)
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser
Mark Talluto wrote:
Thanks for taking this on. These are stopping us from using 7 either
in shipping
applications and in some cases development:
Move command renders graphics improperly when screen has been recently
locked
http://quality.runrev.com/show_bug.cgi?id=13961
Player object
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 5:24 PM, Richard Gaskin wrote:
The first one ('97) was especially interesting because in all the
years
I'd been using LC I'd never used that particular feature. The
description
of that feature on p68 of the User Guide does seem to match your
On Tue, Nov 11, 2014 at 5:49 PM, Peter Haworth p...@lcsql.com wrote:
OK, I'll try with and without multiple statements in both versions.
Now, to make matters worse, it appears that I've been using 7.0.0, not
7.0.1-RC-1 for an unknown period of time--it has managed to set itself as
the default
On Tue, Nov 11, 2014 at 6:21 PM, Richard Gaskin ambassa...@fourthworld.com
wrote:
Dr. Hawkins wrote:
On Tue, Nov 11, 2014 at 5:24 PM, Richard Gaskin wrote:
The first one ('97) was especially interesting because in all the years
I'd been using LC I'd never used that particular feature. The
Dr. Hawkins wrote:
Now, to make matters worse, it appears that I've been using 7.0.0,
not 7.0.1-RC-1 for an unknown period of time--it has managed to
set itself as the default version more than once on this machine.
If that's on a Mac, I don't believe there's anything a developer can do
-
Dr. Hawkins wrote:
To start with, Peter Hayworth filed *Bug 10511*
http://quality.runrev.com/show_bug.cgi?id=10511 in 2006
. . . but wee discuss this every three or fourt months on
this list.
I recall only vague descriptions with no clear outcome, and that
amazingly long bug report
For greater control over app versions I put all the ones I use in my
Dock and launch them explicitly from there.
I¹m sure you¹re not alone there. I have six versions of LC in my dock that
I use for different projects and for testing. I have many more than that
in my Applications folder.
Terry...
On 12/11/14 07:46, Terry Judd wrote:
For greater control over app versions I put all the ones I use in my
Dock and launch them explicitly from there.
I¹m sure you¹re not alone there. I have six versions of LC in my dock that
I use for different projects and for testing. I have many more than
On 11/11/2014, 7:24 PM, Richard Gaskin wrote:
The second one ('98) was one that could benefit from others here who've
used the debugger more than I have (Jacque, that means you g). I'm
not sure if it's a bug or merely needs more explanation in the docs.
For reference:
On 11/11/2014, 11:46 PM, Terry Judd wrote:
For greater control over app versions I put all the ones I use in my
Dock and launch them explicitly from there.
I¹m sure you¹re not alone there. I have six versions of LC in my dock that
I use for different projects and for testing. I have many more
On 11/12/2014, 1:15 AM, J. Landman Gay wrote:
That said, right-clicking on an existing and active breakpoint *does*
put up the expected popup, the one that gives you debugging options. So
I don't see any problems here.
I take that back, I didn't test far enough. The popup appears and the
92 matches
Mail list logo
