One simple way to make this slightly nicer would be to make sure all your
initialisation happens in a separate handler eg (doLibraryInitialization),
and use your script local lock in the libraryStack handler
> local sIHaveBeenInitialized
> on librarystack
> if sIHaveBeenInitialized is empty
Thanks all! He's almost 10lb already, but still no sign of sleeping 4 hours
let alone through the night ;-)
On Fri, May 12, 2017 at 7:12 AM Kay C Lan via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On Fri, May 12, 2017 at 5:45 AM, Dr. Hawkins via use-livecode
>
ide an object, for roughly the same reason.
If you're making precision changes to an object's rect that require seeing
the selection handles within the rect, it seems to me you'd be much better
off adjusting the rect via the message box or using the alignment tools.
On Tue, Mar 28, 2017 at 5:08 PM Ali Ll
The code hit-detects as if the handles were square, so the hit-detection
area is actually bigger than it used to be.
On Tue, Mar 28, 2017 at 4:51 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Ali Lloyd wrote:
>
> > Instead of declaring that thi
Instead of declaring that this is how it should be, it's much better to
provide examples and justification. I just checked, and every application I
have on this computer does selection handles with the center of the handle
on the boundary of the object.
On Tue, Mar 28, 2017 at 3:04 AM Craig
Hi Terry,
This is a known issue, flagged in the release email (but not the release
notes unfortunately). Here is the bug:
http://quality.livecode.com/show_bug.cgi?id=19399
On Fri, Mar 17, 2017 at 7:04 AM Terry Judd via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Is it just me or is
These issues sound like they are to do with Script Debug Mode. Please check
if this is turned on in the Development menu.
Mike, this sounds like it was probably your issue too, especially if
trashing your prefs fixed it, as Script Debug Mode on is the default.
It *does* sound like there may be a
Richmond,
In general that is the case, yes. When for example 8.1.3 GM has been
released, we merge the branches all the way up so that the develop branch
(from which DPs are released) contains everything from that branch. In some
cases there may be things that are in earlier releases but not in a
The dialog asking if you want to start a remote debug session should occur
as soon as you launch the app, so if that isn't happening then something is
not working with the socket, I would imagine. Perhaps try with the phone
actually connected by USB to the Mac and see if that works?
On Fri, Feb
Not as far as I know- if the search for inclusions wasn't working I would
expect it to be an ide bug... does it work in a desktop standalone?
On Tue, 21 Feb 2017 at 17:32, Ben Rubinstein via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Immediately after sending the below, I decide to
Try clicking the cog in the top right, and changing the 'Tab Display Style'
to Labels - it should be clearer what the various sections are!
On Fri, Feb 17, 2017 at 7:57 PM Jerry Jensen via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Got it. It is better, if not terribly obvious.
>
Is it this bug?
http://quality.livecode.com/show_bug.cgi?id=18994
It would help if you posted a crash log too, we might be able to fix it
just from that.
On Fri, Feb 10, 2017 at 11:19 PM Dr. Hawkins via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I opened and tried to build my
Heh, I somehow missed the para where you made this comment already Brahma!
Sorry.
On Sun, Feb 5, 2017 at 6:21 PM Ali Lloyd <ali.ll...@livecode.com> wrote:
> On the subject of building UI from script, I generally think it boils down
> to whether you already have a good resizeS
On the subject of building UI from script, I generally think it boils down
to whether you already have a good resizeStack handler implemented. If you
do, you've done all the hard work already - you can just create all the
objects with their required properties before the card opens and delete
Hi Brahma,
Goes without saying perhaps but it would be extremely helpful if you could
articulate *why* you find this information harder to come by in the current
dictionary. Thanks!
On Thu, 26 Jan 2017 at 20:37, BNig via use-livecode <
use-livecode@lists.runrev.com> wrote:
> @Bernd: is your
The executionContexts is what you're looking for.
On Thu, Jan 19, 2017 at 4:29 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Whoops! Caller is not a property. I guess I don't know.
>
> Bob S
>
>
> On Jan 19, 2017, at 08:23 , Bob Sneidar via use-livecode <
>
a Beta
> version of my next release (presumably it would be fairly daft to
> release a finished
> version, rather than a Beta version, on the basis of a LiveCode rlease
> candidate).
>
> 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
Filed: http://quality.livecode.com/show_bug.cgi?id=19082
On Wed, Jan 11, 2017 at 1:08 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I use this ALL the time. sqlYoga uses special arrays for Record Objects,
> and the elements of one of these arrays can *only* be
The `dispatch function` form of the dispatch command indeed does not appear
to be documented.
On Tue, Jan 10, 2017 at 9:10 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Sannyasin Brahmanathaswami wrote:
>
> > Sometimes you want to do a "remote" call to a function
0xFF001 appears to be an invalid unicode character, residing in the private
use area. When I try
> set the text of the selectedText to numToCodepoint(0xff001)
The text is replaced by a character that LiveCode appears to think is RTL,
and the cursor splits as it does when placed 'ahead' of an RTL
a list.
However, ["a", "b", "c"] *does* contain ["a", "b"] as the latter occurs as
a 'substring' (in the sense of the wikipedia links I posted).
On Wed, Jan 4, 2017 at 1:39 PM Mike Kerner <mikeker...@roadrunner.com>
wrote:
> WHAT?
> There
Peter has pointed out that I am technically using the word 'subsequence' in
error, and should probably have used 'substring' instead!
(cf https://en.wikipedia.org/wiki/Subsequence vs
https://en.wikipedia.org/wiki/Substring)
On Wed, Jan 4, 2017 at 10:16 AM Ali Lloyd <ali.ll...@livecode.com>
'contains' and 'is in' are implemented exactly the same in LiveCode Script,
so there shouldn't be any difference. However there is an interesting
subtlety that emerges when you consider what these two bits of syntax
should do, which explains why they are different in LCB.
When we say 'A contains
It's not hard to fix. One way would be to add a function
function escapeRegExp(str) {
return str.replace(/[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g, "\\$&");
}
to dictionary_functions.js
and add the line
pTerm = escapeRegExp(pTerm);
to the dataSearch function here:
Or try this if the script is not supposed to have any non-ascii characters:
local tLineCount, tCPCount
repeat for each line tLine in
I've no idea what the problem could be, but when things like this happen to
me I copy the routine and continually delete lines until either I discover
what I did wrong, or have a very minimal test case.
On Tue, Dec 6, 2016 at 9:30 PM Dr. Hawkins wrote:
> I have a (much
If anyone particularly wants this feature, it would make a nice and fairly
easy community contribution as it only requires changes in the 'revMenuBar'
script only stack.
You would just have to add the appropriate menu items in
revMenuBarObjectContextMenu (probably using the pSelectable parameter
Ah yes, I had unthinkingly just corrected the folder parameter to
standaloneSaved, but I will have to do it in the array data for backwards
compatibility I suppose.
On Tue, Nov 15, 2016 at 8:51 PM Richard Gaskin <ambassa...@fourthworld.com>
wrote:
> Ali Lloyd wrote:
>
> &
I was thinking a parameter array would be better than many additional
params. That way, additional info is cheap.
So currently the proposed params are:
- current build platform
- current build target/architecture (to disambiguate between 32 bit/64
bit/both)
- total number of standalones to build
messages. i.e
>
> savingStandaloneForWindows
> savingStandaloneForOSX
> savingStandaloneForiOS
> savingStandaloneForAndroid
> savingStandaloneForHTML5
> ...
>
> Or something like that. That way if you only meed to make a specific
> scripted stack modification for Android, you only need
Hi all,
Various tweaks to the standalone builder seem to have broken the way the
savingStandalone message is supposed to work
http://quality.livecode.com/show_bug.cgi?id=18778
I have submitted a pull request that fixes it - the only wrinkle might be
that it reintroduces the following bug:
File one if that's ok - I only looked in response to your message!
On Fri, Oct 28, 2016 at 12:17 AM Richard Gaskin <ambassa...@fourthworld.com>
wrote:
> Thanks, Ali.
>
> Should I file a bug report, or is this fix already in progress?
>
> --
> Richard Gaskin
> Fou
Looks like i introduced it here
https://github.com/livecode/livecode-ide/pull/1427/files
openField used to check the mode of the stack before marking edited, it
seems.
On Thu, Oct 27, 2016 at 9:52 PM Richard Gaskin
wrote:
> Any of you seeing inappropriate prompts to
Reading the source document will tell you what's missing:
https://github.com/livecode/livecode/blob/develop/docs/dictionary/message/preOpenControl.lcdoc
There are quite a few bad references of the form
that should be . I will try and write a little
script at some point to clean all of those
Send params are evaluated in the current context, so you can put variable
names in the list and it will work, eg:
local tRGB
put "25,25,25" into tRGB
send "doSomethingWithColor tRGB" to stack "Color Manager"
On Tue, Oct 18, 2016 at 8:55 AM Sannyasin Brahmanathaswami
wrote:
>
It's not actually correct that they were introduced in LC8 -- the
properties have been there since at least 6.0.1 (
https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343)
and probably before.
Previously the home stack would set the custom property of the error
It's 'scriptExecutionErrors'
On Thu, Oct 13, 2016 at 4:22 PM stephen barncard <
stephenrevoluti...@barncard.com> wrote:
> On Thu, Oct 13, 2016 at 8:17 AM, Graham Samuel wrote:
>
> > put the number of lines of the executionerrors
>
>
> double-take :this looks like
On Wed, Sep 14, 2016 at 7:37 PM Richard Gaskin
wrote:
> But for the Dictionary specifically, even though I have no technical
> problem preventing me from using the Dictionary I shared Jacque's
> preference for a different design (for me the biggest feature is among
>
This is a problem we have with any language that uses the 'c' format
specifier for date format - i.e. stand alone day of week (see here for
example:
http://cldr.unicode.org/translation/date-time#TOC-Stand-Alone-vs.-Format-Styles
)
There is a bug report already here:
Also what version are you using? I vaguely recall a similar issue having
been fixed.
On Fri, 26 Aug 2016 at 17:11, Jeanne A. E. DeVoto
wrote:
> Have you set the itemDelimiter to tab, or is it the default comma?
>
> Can you post your code, along with the contents of the
> I would not have thought that caseSensitive should matter, since these
> are bytes not characters - or is that being naive of me ?
This is correct.
> Would caseSensitive make it faster ?
No, provided the internal representation remains binary, which will be true
provided you are using
Hermann,
Symmetric chunks of the type you describe have issues when the delimiting
rules are more complex - for example when the item delimiter is 'ab', the
number of items in 'ab' is not an invariant of its read order, unless you
reverse the characters in the delimiter too. When the item
If you have or could make a sample stack that demonstrates this slowdown,
it would be useful for us to have a look at.
On Fri, Aug 19, 2016 at 12:23 AM Peter Bogdanoff wrote:
> >> Livecode’s find command in LC8 is really, REALLY slow when you're doing
> multiple (thousands)
You can use the global property
the scriptExecutionErrors
To obtain this list. Note that this does not work in a standalone so if you
need it you'll have to set a custom property on an included stack or
something like that.
On Thu, 4 Aug 2016 at 10:29, Lyn Teyla wrote:
>
Speaking as the person who most likely caused the change, I'm pretty sure
that wasn't intentional. Definitely worth filing a bug report.
On Tue, Jul 12, 2016 at 11:02 PM Devin Asay wrote:
> I just noticed this change today as I was moving a project to LC 8.
>
> On Mac OS X,
> I wonder how a 45 degree progress bar could be made?
A progress bar widget with arbitrary rotation would be relatively easy,
perhaps a good first widget project, should anyone be looking for such a
thing.
There's even some code for a progress bar widget lying around in the
LiveCode GitHub
> in 8.1.0 (dp 1) the new “Inclusions”-tab in the standalone settings is
disabled,
> so I can’t select anything there.
I suspect you may have the "search for inclusions" radio button selected
instead of the "select inclusions" one, in the General tab.
On Mon, Jun 20, 2016 at 1:44 PM Ton Kuypers
Pull request submitted:
https://github.com/livecode/livecode-ide/pull/1224
On Wed, Jun 8, 2016 at 7:35 AM Peter TB Brett
wrote:
>
>
> On 08/06/2016 06:33, jameshale wrote:
> > Ok it is up.
> >
> > http://quality.livecode.com/show_bug.cgi?id=17816
> >
> > over to your
If you are having issues with the tutorial it would help a lot if you could
say:
1) What platform you're on
2) What stage of the tutorial you got to before it got stuck
3) How you're stuck specifically
- Does the instruction window not appear at all?
- Is the instruction window hidden behind
Hi James,
Q1 - yes, that's fine by me, as long as you've signed the CLA
http://livecode.com/store/account/contributor-agreement-signup
(I'm not going to make too much of a habit of committing things on other
people's behalves, but the datagrid docs are important and I really
appreciate the time
Thanks very much!
On Mon, Jun 6, 2016 at 1:18 PM Paul Dupuis <p...@researchware.com> wrote:
> On 6/6/2016 3:37 AM, Ali Lloyd wrote:
> > Paul, since I have committed the datagrid docs on your behalf, qould you
> > mind signing the contributor licence agreement please?
> &
PM, Monte Goulding wrote:
> >> On 6 Jun 2016, at 8:29 AM, Ali Lloyd <ali.ll...@livecode.com> wrote:
> >>
> >> Thanks for this Paul, I have taken the liberty of tweaking it slightly
> more
> >> and submitted a pull request:
> >>
> >> https
Thanks for this Paul, I have taken the liberty of tweaking it slightly more
and submitted a pull request:
https://github.com/livecode/livecode-ide/pull/1218/files
Now all we need to do is convert the guide to markdown ;-)
On Sat, Jun 4, 2016 at 8:26 PM Paul Dupuis wrote:
You should also be able to do
> *put* the keys of (the dragData) into dragKeys
On Fri, May 27, 2016 at 4:05 PM Matt Maier wrote:
> I think it should be "the keys of the dragData of something" or just "the
> keys of dragData".
> On May 27, 2016 17:58, "David Bovill"
Hi Bill,
I've already submitted a bug report for this, should you wish to track its
progress. http://quality.livecode.com/show_bug.cgi?id=17544
On Wed, May 25, 2016 at 11:34 PM William Prothero
wrote:
> Jacqueline:
> Thanks for that hint. However, I have an application
That is a correct description of how it currently operates, although the
'thought experiment' of having 1000 widgets is valid - we are aware that it
would be a problem but it is not current a priority. I hope that at some
point we will able to remove all but the entry content from the dictionary
Having fairly recently done a PhD in set theory, I can confirm that the
independence of the continuum hypothesis has not been refuted!
On Mon, May 23, 2016 at 2:50 AM Mick Collins wrote:
> (Try again, apologies for accidentally sending)
> ... typo
> When you said
> "
Hi Klaus,
Although we currently have no plans to do that ourselves, it shouldn't be
too hard to turn the string that's used for the tree view into a property
of the widget, since it is almost completely independent of the rest of the
code.
You'd just need to define a new member variable (say
Hi Ton,
The graph widget layout code is rather complicated because of the
relationship between the available space for the graph and how much space
is needed for the axis labels. It is mainly for space saving reasons that
the drawYLabels handler does the following:
put the rounded of tNumber
gt; this array has a name : MyContents
>
>
> How can i set the arrayData to the tree widget ?
>
> set the arrayData of widget « X » to MyContents ?? doesn’t work ...
>
> Thanks
>
> Greetings.
>
> > Le 16 mai 2016 à 17:41, Ali Lloyd <ali.ll...@livecod
me, or indeed we.
On Tue, May 17, 2016 at 9:52 AM Ali Lloyd <ali.ll...@livecode.com> wrote:
> That should work, yes! Could you post more than just the one-line snippet?
> That way me might be able to see what is going wrong.
>
>
> On Mon, May 16, 2016 at 9:23 PM Yves COP
There were several fixes applied to the custom properties editor which is
very similar-it appears we (I) forgot to also apply them to the array
editor. This is very easily rectified. Sorry for any inconvenience.
On Sun, May 15, 2016 at 9:30 PM Dave Kilroy
wrote:
>
The old style 'contents' pane will be reinstated in (probably) the next RC:
https://github.com/livecode/livecode-ide/pull/1159
On Sun, May 8, 2016 at 3:31 PM RM wrote:
> If one enters multi-line text, then clicks on another tab in the Props
> palette, then clicks on
Currently there is not, no.
It would be quite easy to add, as the row height is completely abstracted
in the code as a private variable mRowHeight, which is initialised to 21 in
the OnCreate handler and never changed.
So I believe all that would need to be done is to add a new property and
make
Hi Andrew,
We did indeed consider if the screenshots should be updated. Here is a bug
report:
http://quality.livecode.com/show_bug.cgi?id=16610
which led to the changes that need to be made being detailed in GitHub
issues:
Hi Bill, I believe this is an instance of this bug:
http://quality.livecode.com/show_bug.cgi?id=17256
The fix for this is awaiting merge.
https://github.com/livecode/livecode-ide/pull/1154
On Mon, May 2, 2016 at 10:46 PM William Prothero
wrote:
> I think the problem
I suspect
put the keys of (the properties of the templatefield)
is what you want.
On Thu, Apr 28, 2016 at 4:21 PM Richard Gaskin
wrote:
> Sannyasin Brahmanathaswami wrote:
> > Hmmm I could have sworn this worked years ago:
> >
> > put the keys of templatefield
>
Mark - my comment refers to an earlier line in the description section.
Your change to the list of references is correct, but the format of the
reference within the description (I.e. The bit between < and >) is
entryName(optionalType) rather than what it is at the moment, entryName
optionalType
Not a feature, and I can't reproduce it here. Is it Linux-specific?
On Wed, Apr 13, 2016 at 10:12 PM Paul Dupuis wrote:
> On 4/13/2016 4:13 PM, Richard Gaskin wrote:
> > RECIPE:
> > 1. Make a new stack
> > 2. With the Browse tool active, in the Message Box run:
> >
> >
.com
>
>
>
> On April 13, 2016 2:18:20 AM Ali Lloyd <ali.ll...@livecode.com> wrote:
>
> > I think the problem with in those two entries is that
> clipboard
> > (property) is in the references, but it there is no clipboard property,
> > only a cli
se the tool all the time can improve it, then making
> updating the docs this difficult is not going to do that. b) Trying to
> keep all the branches straight, and the complexity this adds is only going
> to make it more difficult, still.
>
> On Wed, Apr 13, 2016 at 3:16 AM, Ali
I think the problem with in those two entries is that clipboard
(property) is in the references, but it there is no clipboard property,
only a clipboard function. So removing that from the references should fix
it.
On Wed, Apr 13, 2016 at 6:57 AM J. Landman Gay
wrote:
On Mon, Apr 11, 2016 at 9:55 PM J. Landman Gay
wrote:
> BTW, I downloaded the elusive viewer stack but it's leaving out most of
>
the keywords when it opens the text in a browser. I can't tell if it's a
>
bug in the text itself or in the viewer. Anyone know?
>
I've
Jacque, you may want to read this blog post
https://livecode.com/putting-the-you-in-documentation/
On Wed, Apr 6, 2016 at 7:25 PM J. Landman Gay
wrote:
> On 4/6/2016 1:45 AM, Monte Goulding wrote:
> > I hadn’t seen the contributing to the docs guide so even though I
>
behavior" to (localPath() &
> "main-stack-scripts/generic-mobile-functions_behavior.livecode")
>
> end assignBehaviors
>
> OTOH: if you assign the behavior via the inspector to the script-only
> stack it *does* work..
>
> So there must be a syntax for that th
The fix for this issue is done and will be available in the next release of
LC 8.
On Sun, Apr 3, 2016 at 8:25 PM Sannyasin Brahmanathaswami
wrote:
> FYI for anyone struggling with the "lost reference" issue in LC8 where
>
> -- you click on something in the Project browser a
> It's a pain to open the object inspector and copy the behavior reference
> then use the message box to to "open script of…"
This is no longer necessary in the latest DPs of 8.0 - the behavior
property in the property inspector has an 'edit script' button.
On Fri, Apr 1, 2016 at 3:21 PM Peter
I would have to answer 'not at the moment' to all of the above! They are
all possibilities, but we will probably have to gauge interest to decide
where we take it next.
I'm not sure the interactive tutorial format will lend itself well to
explaining how to create interactive tutorials, but I
I'm somewhere between pretty sure and absolutely certain this is nothing to
do with the fact that it is a button. Try
edit script of button id 1161 of stack "oldStack"
in the message box. Probably there is no button with that id, or no stack
"oldStack" in memory.
On Fri, Apr 1, 2016 at 7:41 AM
Or more accurately
on preOpenStack
local tBehaviorLongID
put the long id of stack "" into tBehaviorLongID
set the behavior of field "FieldWithBehavior" of me to tBehaviorLongID
end preOpenStack
On Thu, Mar 31, 2016 at 11:31 PM Ali Lloyd <ali.ll...@livecode.com
My solution to this:
Stack "MyTestStack" has a field, which is assigned stack
"MyBehaviorStack" as its behavior property.
Stack "MyBehaviorStack" is a separate stack file.
would be to also include the behavior *setting* in the preOpenStack handler
of "MyTestStack".
on preOpenStack
set the
NB the behavior entry in the dictionary has been rewritten and will be
correct in the next release of 8.0. You can check out the raw text of it
here if you want:
https://github.com/livecode/livecode/blob/develop/docs/dictionary/property/behavior.lcdoc
On Wed, Mar 30, 2016 at 2:53 PM Richard
> True - but sadly there's no effective way to filter those 523 entries to
> see only the ones that are relevant to a List type.
One way to do this is to click the 'lists' filter in the tags section.
On Sun, Mar 27, 2016 at 5:33 PM Alex Tweedly wrote:
>
>
> On 27/03/2016
Hi Bill,
Could you be more specific? The dataGrid pane of the property inspector is
just the bit that was in the Basic pane of the old property inspector under
the
Data Grid: ---
section.
The Columns pane was missing and will be there in the next build
I think some of your issues may be because you have the property inspector
set to Property Labels -> Name of LiveCode property rather than Description
of Option. I'll add a bug report to make sure the latter option is selected
during the tutorial.
The double click on the inspector icon is
Ah, the start center does (intentionally) close when you open a stack. But
you can get it back from the Help menu.
Note that most of the IDE functionality is disabled during the tour, so you
won't actually be able to copy stuff to another stack.
On Fri, Mar 18, 2016 at 9:30 PM RM
I find I get the best results from export snapshot by using the following
form:
export snapshot from rect (the rect of tObjectLongID) of tObjectLongID ...
So you might try
export snapshot from rect (the rect of widget "Chart") of widget "Chart" of
this card to tVar as PNG
If that doesn't give
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #22 here: https://goo.gl/DsmClz
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
There is an outstanding bug report about the missing property inspector
pane for the data grid in LC 8 (
http://quality.livecode.com/show_bug.cgi?id=16748). It will be fixed some
time in the next couple of weeks.
On Wed, Feb 24, 2016 at 11:02 PM wrote:
> No, I am stuck in v.6.7
The tools palette settings menu pops up when you click the 'cog' icon at
the top right of the tools palette.
On Tue, Feb 23, 2016 at 10:59 AM RM <richmondmathew...@gmail.com> wrote:
>
>
> On 22.02.2016 22:38, Ali Lloyd wrote:
> > Do you have widgets ticked in the
Do you have widgets ticked in the show controls submenu of the tools
palette settings?
On Mon, Feb 22, 2016 at 7:48 PM RM wrote:
>
>
> On 22.02.2016 21:40, RM wrote:
> > Well; there's a funny thing . . . when I started up LiveCode 8.0 DP 15
> > it offered to upgrade
I have seen something like this too, but haven't yet got a recipe - looks
like a redraw issue though. Perhaps to do with setting the rect under lock
screen, or changing the tool under lock screen/messages or something like
that.
On Sun, 21 Feb 2016 at 03:51, Sannyasin Brahmanathaswami
Hi Bill, you may be pleased to know that the property inspector editor for
the behavior property has been 'beefed up' for 8.0 DP 15:
https://github.com/livecode/livecode-ide/pull/840
On Wed, Feb 17, 2016 at 2:54 PM William Prothero
wrote:
> Folks:
> This is not a really
It *should* be checking the scripts of all stacks, substacks, cards and
controls for any lines containing any of
libUrl,cachedURL,cachedURLs,ftp,http,https,load,post,resetAll,URL,URLStatus
Check out the command revSmartChecking in stack revSaveAsStandalone.
It does sound like a bug - what version
The label text of the menu buttons actually does go bold, but it seems to
be an unfortunate feature of the system font on OSX (Yosemite onwards) that
it either changes imperceptibly or not at all when bolded. I have noted it
as something we should deal with.
Or possibly 6.6.4.
On Mon, Feb 8, 2016 at 10:10 PM Ali Lloyd <ali.ll...@livecode.com> wrote:
> It was 6.7 GM, I believe.
>
>
> On Mon, Feb 8, 2016 at 9:15 PM Devin Asay <devin_a...@byu.edu> wrote:
>
>> Can anyone tell me the first version of LC where script-on
The app browser is in the plugins menu.
On Mon, Feb 8, 2016 at 10:38 PM Ali Lloyd <ali.ll...@livecode.com> wrote:
> None of these have been changed in LC 8 as far as I know - Cmd + E and
> Alt + Cmd + click reliably open the script editor for the selected and
> clicked object resp
None of these have been changed in LC 8 as far as I know - Cmd + E and
Alt + Cmd + click reliably open the script editor for the selected and
clicked object respectively for me. I presume you are on OSX?
What keyboard shortcuts open the card / stack script? How are you trying to
open a contextual
It was 6.7 GM, I believe.
On Mon, Feb 8, 2016 at 9:15 PM Devin Asay wrote:
> Can anyone tell me the first version of LC where script-only stacks
> appeared? Was it one of the v. 8 DPs?
>
> Devin
>
>
> Devin Asay
> Office of Digital Humanities
> Brigham Young University
>
>
101 - 200 of 308 matches
Mail list logo