On July 23, 2016 9:00:34 PM Mark Wieder wrote:
On 07/23/2016 02:48 PM, J. Landman Gay wrote:
The scriptExecutionErrors is also in LC 6.x, btw.
I've updated the LC Error Lookup stack. The revision has been uploaded
to the user Sample Stacks online. Replace your
On 07/23/2016 02:48 PM, J. Landman Gay wrote:
The scriptExecutionErrors is also in LC 6.x, btw.
I've updated the LC Error Lookup stack. The revision has been uploaded
to the user Sample Stacks online. Replace your existing copy with this
new one.
I don't quite know when the change happened,
Monte Goulding wrote:
> Support for deprecation (at least in a consistent and visually
> obvious way) has only just been added to the dictionary. If anyone
> would like to contribute to adding depredation notes to the lcdoc
> files they are quite welcome!
Thank, Monte. Fortunately it's so rare
Support for deprecation (at least in a consistent and visually obvious way) has
only just been added to the dictionary. If anyone would like to contribute to
adding depredation notes to the lcdoc files they are quite welcome!
Cheers
Monte
Sent from my iPhone
> On 23 Jul 2016, at 11:34 PM,
It has been around for a long time but it is only in the IDE and server engines
so if you need the list in a standalone you should copy it in your
savingStandalone script. The empty lines should be maintained otherwise the
error line number won't match the right line.
Cheers
Monte
Sent from
J. Landman Gay wrote:
> On 7/23/2016 3:45 PM, Richard Gaskin wrote:
>> In your copious free time would you be able to update the MetaCard
>> Setup stack as well?
>
> Is anyone still using that? Didn't we EOL it?
I'm not sure anyone ever declared it officially dead, but since the
former
On 7/23/2016 3:33 PM, J. Landman Gay wrote:
I'm not sure when the scriptExecutionErrors was implemented, but it is
also there in LC 7.x so apparently it's been around for a while.
My guess is that it's an undocumented function in the engine. I'll
update our lookup stack to use it.
The
On 7/23/2016 4:04 PM, Sannyasin Brahmanathaswami wrote:
) if the extension of the text only stack is ".livecode" then you can
boot that into the IDE or use GO or "start using"
but if you use ".livecodescript" as the extension. then you can't
actually open it in the IDE by double clicking.
I
I'm still struggling with the initialization of text only stacks/libs into the
message path
A few questions.
1) if the extension of the text only stack is ".livecode" then you can boot
that into the IDE or use GO or "start using"
but if you use ".livecodescript" as the extension. then you
On 7/23/2016 2:31 PM, Richmond wrote:
Ha, Ha, Ha: Sanskrit when written in Devanagari employs thousands of
glyphs called "conjunct
consonants" which are composed of constituent consonants in a
consonantal cluster: so my
Devawriter does "all the clever knitting".
Ah, I see. Okay. Well at least
J. Landman Gay wrote:
> Good catch, this change also breaks the Error Lookup stack that
> Richard and I made some time ago. I'm not sure when the
> scriptExecutionErrors was implemented, but it is also there in
> LC 7.x so apparently it's been around for a while.
>
> My guess is that it's an
On 7/23/2016 10:01 AM, Sannyasin Brahmanathaswami wrote:
so on hunch based on this statement, since "the
scriptExecutionErrors" was not a property of this stack, I thought
"hmmm must be an IDE global prop" and ran in the msg box
Yes! there was the errorsList, copy and paste to a custom prop in
Stick this one out to about 5 mins 40 seconds and things get really "nasty":
https://www.youtube.com/watch?v=sbKEEYeDLyc
Richmond.
On 23.07.2016 21:40, J. Landman Gay wrote:
What I'm getting at is that generally you shouldn't need to do any
unicode conversions at all anymore. So it would help
On 23.07.2016 21:40, J. Landman Gay wrote:
What I'm getting at is that generally you shouldn't need to do any
unicode conversions at all anymore. So it would help to know how you
are using the command and in what context. There isn't a need to
specify unicode text, you can just treat
did you try with the parameter from...
convert tDate from …. to dateitems
where the parameter after from is the source date format.
e.g.
put the system date into tDate
convert tDate from system date to dateitems.
I remember that i had a similar problem when working with system dates which
Yes; that really does solve a serious problem as all I have to do is go
through
searching for 'unicodeText' and replacing all the instances with 'text'.
Thanks a million.
Richmond.
On 23.07.2016 21:25, Mike Bonner wrote:
If it will still work using "set" rather than "put.. into.."
replace
What I'm getting at is that generally you shouldn't need to do any unicode
conversions at all anymore. So it would help to know how you are using the
command and in what context. There isn't a need to specify unicode text,
you can just treat everything the way we use plain ASCII.
So, what
If it will still work using "set" rather than "put.. into.."
replace unicodetext with text
so that this: set the unicodeText of fld "fPROC" to numToCodePoint(57669)
becomes this: set the Text of fld "fPROC" to numToCodePoint(57669)
Don't know if it will work, but it seems that if you can just put
I am trying to implement a generalized behavior that triggers after the
entire execution path, rather than after the immediate script, but before
the next script in the path.
Actually, having control return to a handler after "pass someHandler" would
also solve my issues.
A control might be
Richmond:
> but as I have a vast number of controls to work through
> that is still going to be extremely tedious
One click?
on mouseUp
repeat ... stacks ...
repeat ... cards of stack
repeat ... parts of card
replaceMyThings(the script of part ...)
end repeat
end
Looking up 'Wildcard' in the online Livecode Dictionary (because the
64-bit Linux version
is non-functional) one gets this:
wildcard
name
wildcard
type
glossary
synonyms
wild card,wildcard,wildcard expression,glob,globbing,globbed,globular
expansion,globular expression
Related
glossary:
That looks good: but as I have a vast number of controls to work through
that is still going to be extremely tedious.
Livecode's "Find & Replace" does that is seconds through my stack, with
its millions of lines
of code.
If I open the "Find & Replace" dialog from inside a script windows I
Nabble interprets somehow the chars "q u o t".
So replace the rubbish around "fProc".
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Find-Replace-tp4706922p4706940.html
Sent from the Revolution - User mailing list archive at Nabble.com.
A simple (quick and dirty) non-regex solution (use LC 7 or LC 8)
on mouseUp
put replaceMyThings(fld 1) into fld 2
end mouseUp
function replaceMyThings LL
set itemdelimiter to "set the unicodeText of fld "& \
quote&"fPROC"&" to numToCodePoint("
repeat for each line L in LL
The problem is that the stack using "set the unicodeText of fld "fPROC"
to numToCodePoint(57669)"
doesn't work.
Tests with "put numToCodePoint(57669) into fld "fPROC"" do work.
That's enough of a "case" for me.
Richmond.
On 23.07.2016 20:24, J. Landman Gay wrote:
I wonder if you really
I wonder if you really need to do that any more. What's the use case?
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 23, 2016 11:13:58 AM Richmond wrote:
Here's a puzzle:
Here's a puzzle:
I need to replace thousands of lines like this:
set the unicodeText of fld "fPROC" to numToCodePoint(57669)
with this:
put numToCodePoint(57669) into fld "fPROC"
the problem is that the number of the codePoint is different in each case.
Wildcards?
Richmond.
There is no real difference between the 2 (repeat until, repeat with..)
but..
if you repeat with x = 1 to 20
add 1 to x -- will only repeat 10 times because the repeat increments 1,
and the add increments another
-- pretty much the same as appending step 2
end repeat
If you were to add -1
The first case is a template where
x is an enumerator variable that is increased
(or decreased resp.) for you by LC.
It is not recommended to act on it because the
template is idiot-proof but NOT academic-proof.
In the second case x is your local variable that
you use as an enumerator.
This is
Erm . . .
So what is the difference between:
on mouseUp
repeat with x = 1 to 20
--do something
end repeat
end mouseUp
&
on mouseUp
put 1 into x
repeat until x > 20
--do something
add 1 to x
end repeat
on mouseUp
R.
On 23.07.2016 18:02, [-hh] wrote:
Richmond wrote
Roger Eller wrote:
> I have an application running on Windows 7. Windows is localized for
> Spanish language, and resides in Mexico. Convert doesn't work. In
> their default format, convert VAR to dateItems returns the original
> unchanged VAR content.
>
> This is my workaround. Is there a
Thanks Klaus! I will give it a try.
~Roger
On Jul 23, 2016 11:46 AM, "Klaus major-k" wrote:
> Hi Roger,
>
> > Am 23.07.2016 um 17:34 schrieb Roger Eller >:
> >
> > I have an application running on Windows 7. Windows is localized for
> > Spanish
Richmond wrote
> "not recommended". If someone can explain in
> a way that makes reasonable sense ...
Predict the result of the following loop and
remove or not the "shiftkey-exit":
on mouseUp
repeat with x = 1 to 20
-- add -1 to x -- not recommended
add -4/3 to x -- not recommended
Hi Roger,
> Am 23.07.2016 um 17:34 schrieb Roger Eller :
>
> I have an application running on Windows 7. Windows is localized for
> Spanish language, and resides in Mexico. Convert doesn't work. In their
> default format, convert VAR to dateItems returns the
I have an application running on Windows 7. Windows is localized for
Spanish language, and resides in Mexico. Convert doesn't work. In their
default format, convert VAR to dateItems returns the original unchanged VAR
content.
This is my workaround. Is there a better way?
put "22/07/2016
http://forums.livecode.com/viewtopic.php?f=5=27663
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
The dictionary says:
"Standard error descriptions are stored in the cErrorsList of the first card of
stack "revErrorDisplay". The error-code refers to the line number in this
custom property which contains the error description."
but the RevErrorDisplay is now a script only stack and I can't
Bless you!
Richmond.
On 23.07.2016 17:19, Mike Bonner wrote:
If you're using find and replace in the script editor, when choosing the
source either choose "current tab" or "all tabs" and the buttons will
become available.
If you're using the other find.. (from the edit menu, or while NOT in
If you're using find and replace in the script editor, when choosing the
source either choose "current tab" or "all tabs" and the buttons will
become available.
If you're using the other find.. (from the edit menu, or while NOT in the
script editor window, hit the keys to bring up search.
Type in
This does work if I choose "Current Tab" [i.e. the script I have open at
present];
but this is effectively useless as I have at least 2000 scripts to go
through.
R.
On 23.07.2016 17:05, Richmond wrote:
I have to replace a very large number of instances of
*uniencode*
with either
I have to replace a very large number of instances of
*uniencode*
with either *nothing* or a *single space* in a very large number of
faux buttons in my *Devawriter Pro*, which is currently being
dragged, "screaming", from *Livecode 4.5* to something a spot more
up-to-date.
Cracking open
Richmond wrote:
> And here is what the 7.1.4 dictionary has to say, blow an icon that
> says liveResizing IS a feature
>
> on Macintosh:
> "On Mac OS, Unix, and Windows systems, the liveResizing property has
> no effect."
>
> Ha, Ha, Ha: very nearly got a hernia laughing at that one.
>
> The BIG
I was reading an incredibly tedious book about Visual BASIC 6 last night
[ left over from my M.Sc. in "Computers and IT" from the University of
Abertay ] and
wondering about various things such as "step". Reading computer manuals
is, in my experience, really great in the same sort of way
And here is what the 7.1.4 dictionary has to say, blow an icon that says
liveResizing IS a feature
on Macintosh:
"On Mac OS, Unix, and Windows systems, the liveResizing property has no
effect."
Ha, Ha, Ha: very nearly got a hernia laughing at that one.
The BIG QUESTION has to be:
"Where
Paul_Hibbert wrote
> ... setting the liveResizing of the stack to false does exit fullscreen
> mode,
> although the stack grows in height by 22px!
The most useful bug of the year!
Works in LC 6/7/8 and also this way:
set liveresizing of this stack to the liveresizing of this stack
Sadly
This is really the same sort of thing as being unable to hit
command/control Z
when one accidently deletes something.
R.
On 23.07.2016 10:57, Peter Reid wrote:
Is there any way of supporting multi-level undo in LiveCode?
My current project provides support for the user to manipulate
I looked into it a while back. A few basic options are:
- rationalize all of the user's actions into a list of named actions, keep
track of the actions in order, and then have the engine execute the list.
if the user uses undo, just move a marker one item backwards in the list,
so that the engine
Is there any way of supporting multi-level undo in LiveCode?
My current project provides support for the user to manipulate objects (grouped
vector objects). The user can grab objects, move them around the window,
group/ungroup, align, cut, copy, paste and undo. However the undo is single
48 matches
Mail list logo