Peter W A Wood wrote
> Thanks Klaus. Co-incidentally, Bernd also pointed this out to me. It seems
> the LiveCode community in Germany may be small but you’re all very smart
> (and helpful).
>
> Peter
Hi Peter,
Klaus is the smart German, I learned this from Klaus and also mentioned that
in the com
> On 2 Sep 2015, at 00:15, Klaus major-k wrote:
>
> Hi Peter,
>
>> Am 01.09.2015 um 15:23 schrieb Peter W A Wood :
>>
>> Peter
>>
>>> On 31 Aug 2015, at 23:40, Peter TB Brett wrote:
>>> If you go into the dictionary in the IDE, there's a drop down menu at the
>>> top left.
>> Not in LiveC
OK, now I understand my confusion.
I have been comparing the NEW dictionary to the OLD (V7 and before) where
the listing of terms was BETTER presented (at least in my opinion).
In the OLD dictionary the listing of items was a table with three columns
the first of which was termed "Keyword"
This
There are at least three bug reports on the dictionary size, geometry, and
behavior on resizing, and they have been accepted.
On Tue, Sep 1, 2015 at 1:11 PM, BNig wrote:
> Klaus major-k wrote
> > Hi Peter,
> >
> >> Am 01.09.2015 um 15:23 schrieb Peter W A Wood <
>
> > peterwawood@
>
> > >:
> >>
Klaus major-k wrote
> Hi Peter,
>
>> Am 01.09.2015 um 15:23 schrieb Peter W A Wood <
> peterwawood@
> >:
>>
>> Peter
>>
>>> On 31 Aug 2015, at 23:40, Peter TB Brett <
> peter.brett@
> > wrote:
>>> If you go into the dictionary in the IDE, there's a drop down menu at
>>> the top left.
>> No
Probably instead of dots we would just display the whole syntax then, since
delete element *Start* to *Finish* of *Target *
would be just as illustrative but showing the parameter names as well.
I guess ideally it would be something snappier, in the same way that in the
script dictionary we have
N
Hi Peter,
> Am 01.09.2015 um 15:23 schrieb Peter W A Wood :
>
> Peter
>
>> On 31 Aug 2015, at 23:40, Peter TB Brett wrote:
>> If you go into the dictionary in the IDE, there's a drop down menu at the
>> top left.
> Not in LiveCode 8 DP 4 it seems.
resize the dictionary window a couple of ti
In the .mlc file an example syntax definition is of the form:
"delete" "element" "of"
where the verbs, for want of a better term, are quoted.
Why can't these be the name that is shown in bold at the top of the entry?
So in the above example the entry would have at the top
*delete element
Peter
> On 31 Aug 2015, at 23:40, Peter TB Brett wrote:
>
> If you go into the dictionary in the IDE, there's a drop down menu at the top
> left.
Not in LiveCode 8 DP 4 it seems.
Regards
Peter
___
use-livecode mailing list
use-livecode@lists.ru
The fact that the example for the localdate doesn't actually include "local
date" is indeed confusing, and a bug.
I wonder if a judicious choice of parameter name would help with the
multiple entries for the same syntax. If we had *LeftList *is *RightList*,
etc. would that be ok?
The reason they
Have to agree with Mike on this.
I too find the LCB APIs confusing in having "names" of things that are not part
of the syntax.
The fact that the example for the localdate doesn't actually include "local
date" is even more confusing.
Just looking at some entries is see "ListIsList" which is an o
gt; > local date, but in the example, local is colorized as a modifier
> > and
> > >> > date
> > >> > > > as a keyword, and the same occurs with time - it is shown as
> local
> > >> > time,
> > >> > > > but again, local is col
r and time as a keyword,
> >> but
> >> > > > neither time nor date are documented per se, which makes me wonder
> >> what
> >> > > > syntax is really available, and if there are other modifiers.
> >> > > >
> >> > > &
;
>> > > > The example incorrectly sets the timezone as UTC0, when what it
>> should
>> > be
>> > > > doing is determining the timezone either by comparison to UTC or
>> some
>> > > other
>> > > > means, and then setting. I'd l
as UTC0, when what it
> should
> > be
> > > > doing is determining the timezone either by comparison to UTC or some
> > > other
> > > > means, and then setting. I'd like to beat the rest of the community
> to
> > > the
> > >
#x27;d like to beat the rest of the community to
> > the
> > > punch and submit the fix to Git, but I don't want to waste my time if
> the
> > > syntax is deprecated on arrival.
> > >
> > >
> > > On Mon, Aug 31, 2015 at 11:40 AM, Peter TB Brett <
> &
to waste my time if the
> > syntax is deprecated on arrival.
> >
> >
> > On Mon, Aug 31, 2015 at 11:40 AM, Peter TB Brett <
> peter.br...@livecode.com
> > > wrote:
> >
> >>
> >>
> >> On 31/08/2015 16:38, Mike Kerner wrote:
> &
of the community to the
> punch and submit the fix to Git, but I don't want to waste my time if the
> syntax is deprecated on arrival.
>
>
> On Mon, Aug 31, 2015 at 11:40 AM, Peter TB Brett > wrote:
>
>>
>>
>> On 31/08/2015 16:38, Mike Kerner wrote:
&
16:38, Mike Kerner wrote:
>
>> Does anyone know how to find the LCB API's? I was trying to fix a bug in
>> the new clock widget over the weekend, but the various functions that it
>> calls are not documented anywhere that I've looked, so far.
>>
>
> If you go in
On 31/08/2015 16:38, Mike Kerner wrote:
Does anyone know how to find the LCB API's? I was trying to fix a bug in
the new clock widget over the weekend, but the various functions that it
calls are not documented anywhere that I've looked, so far.
If you go into the dictionary
Does anyone know how to find the LCB API's? I was trying to fix a bug in
the new clock widget over the weekend, but the various functions that it
calls are not documented anywhere that I've looked, so far.
--
On the first day, God created the heavens and the Earth
On the second day, G
21 matches
Mail list logo
