Ye and Amen!
Bob S
On Jan 18, 2017, at 09:41 , Stephen Barncard via use-livecode
> wrote:
. We have other interests and use livecode to support their complexities.
We want to get to the "thing" that accomplishes our task and
On Wed, Jan 18, 2017 at 8:56 AM, Richmond Mathewson via use-livecode <
use-livecode@lists.runrev.com> wrote:
> And all that I am twitched about at the moment is finding a properly
> documented list of the conjunct
> consonants for the Siddham writing system: suddenly my burden feels about
> 1000
If it is a line, then technically it has no beginning or end point. You must
mean a line segment or a ray. ;-)
Bob S
On Jan 18, 2017, at 09:20 , Richard Gaskin via use-livecode
> wrote:
Ali Lloyd wrote:
> Of course at some
Ali Lloyd wrote:
The reason it doesn't show up on GitHub is that it will only appear on
GitHub when there is a pull request, which is usually only when it is
fixed. What you need is
http://quality.livecode.com/buglist.cgi?list_id=67534_format=advanced_milestone=8.1.3-rc-1
Not everything in
Richmond Mathewson wrote:
> Well, even if nothing else I am beginning to understand just how
> complicated LiveCode development is . . .
Amen to that, brother.
I find that complaints about the LC engine often tend to occur in
inverse proportion to the poster's experience in multi-platform C
Ali Lloyd wrote:
> Of course at some point you have to draw a line, but the
> aformentioned bug is well beneath* it.
>
> *I'm not sure when you metaphorically draw a line, whether that line
> is meant to be horizontal or vertical, or indeed which side of the
> line you start from
We're bike
Well, even if nothing else I am beginning to understand just how
complicated LiveCode
development is . . .
And all that I am twitched about at the moment is finding a properly
documented list of the conjunct
consonants for the Siddham writing system: suddenly my burden feels
about 1000 times
The reason it doesn't show up on GitHub is that it will only appear on
GitHub when there is a pull request, which is usually only when it is
fixed. What you need is
http://quality.livecode.com/buglist.cgi?list_id=67534_format=advanced_milestone=8.1.3-rc-1
Not everything in that list actually
Hi Richmond,
Github shows all the bugs for which a PR has been submitted. So if no PR
has been submitted for a blocker, it will not show up.
The blocker Ali was referring to in his previous post is now fixed (
https://github.com/livecode/livecode/pull/5071).
However, unfortunately, yesterday we
One thing I don't understand is, if there is a blocker, why it does not
show up
on Github:
https://github.com/livecode/livecode/milestone/126
I wonder if there is a way people like me can track all the dependencies
( i.e. those mentioned
inwith GitHub and those that seem to be outwith GitHub)
Thanks for the heads-up Ali; now I know there is a blocker I will get on
with
other aspects of my Devawriter Pro and not get twitched that things are not
happening on your front as quickly as I thought they would.
Richmond.
On 1/13/17 1:02 pm, Ali Lloyd via use-livecode wrote:
We don't
We don't actually use GitHub milestones in that way, we just use them to
track which releases various pull requests have gone into. So 100% complete
just means there are no outstanding pull requests with the 8.1.3-rc-1
milestone set.
As it happens, there is only one more blocker, unfortunately it
Wow;
https://github.com/livecode/livecode/milestone/126
"no due date"
100% complete
Ouch, I can feel the anticipation in the pit of my stomach.
Err: 100% Unicode functionality?
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
13 matches
Mail list logo