Forgot to mention that this does currently rely on QuickTime, I have run into a
few problems with the latest DPs of LC 6.7 & 7.0 - need a bit more time testing
them.
Paul
On 2014-07-28, at 11:11 PM, Paul Hibbert wrote:
> You can import a PDF into LC by using a player control instead of an ima
You can import a PDF into LC by using a player control instead of an image
control.
I'm working on a small app that imports Jpegs, Gifs, PNGs, Tiffs, PSDs EPSs &
PDFs and all work just fine, just use an image control for the first three, or
a player control for the remaining four. Take a snapsh
As GIMP (open Source) can import a page of a PDF document as an image
might that capability not be built into Livecode in due course?
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe
**LiveCode Crowdfunding HTML5 Web App Deployment** -- The
cross-platform development environment LiveCode, perhaps the most
successful of HyperCard’s successors, can deploy apps to Mac OS X,
iOS, Windows, Android, and several flavors of Unix. LiveCode’s
developer, RunRev, raised nearly $84
Oh, yeah, and Tao refers to just that - Tao, i.e. the way. With each
development tool there are caveats, provisos, and surprises that come up.
In a discussion several years ago for one of those tools, the president of
the company explained away several really annoying side-effects as "The Tao
of"
On Sun, Jul 27, 2014 at 4:58 PM, Peter Haworth wrote:
> I'm amazed that there can be an RFC for this. As is evident from the
> posts, it's a matter of personal preference and which mail system you use.
>
There are several. Before the Eternal September, incorrect formatting was
one of many thin
I think actually its more equivalent to evaluating an expression. It still has
to parse the parameter, otherwise value(2+3) wouldn't work. That has nothing to
do with pointers. A DO statement has to handle verbs too, so its more work.
.Jerry
On Jul 28, 2014, at 4:57 PM, Mike Kerner wrote:
> C
Craig,
This is equivalent to dereferencing a pointer, which is what I was
referring to. After reading the explanation in the dictionary, this is not
what I expected. When I said value(b), I expected LC to just dumbly return
"a", but was sort-of hoping that I'd get "1", so part of me is giddy, and
Mike Kerner wrote:
> OMG AND IT'S SCREAMING FAST COMPARED TO DO. AAAUGH!
Most things are.
The "do" command has to do the equivalent of what happens when you
compile a script, in addition to executing it.
There are some extremely rare cases where "do" is useful, but most uses
I c
Mike.
Oh. Now I see what you mean.
This is not pointers and handles, though I think it is adorable you
characterized it that way. It is xTalk string evaluation gone wild.
When you say:
value(c)
LC evaluates a naked "a" --no quotes. The literal has been supplanted
So when you get t
OMG AND IT'S SCREAMING FAST COMPARED TO DO. AAAUGH!
On Mon, Jul 28, 2014 at 5:33 PM, Mike Kerner
wrote:
> Stop it. Now you're just making me mad. I just discovered this, and now
> I'm getting hazed with it.
>
> Well played, sir. Well played.
>
>
> On Mon, Jul 28, 2014 at 5:26 PM
Stop it. Now you're just making me mad. I just discovered this, and now
I'm getting hazed with it.
Well played, sir. Well played.
On Mon, Jul 28, 2014 at 5:26 PM, Mark Wieder wrote:
> Mike-
>
> You can also get tricky and do things like:
>
> on mouseUp
>local a, b
>
>put "hello" int
Mike-
You can also get tricky and do things like:
on mouseUp
local a, b
put "hello" into a
put a & "()" into b
put value(b)
end mouseup
function hello
return "goodbye"
end hello
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livec
Nope.
try it.
I'll spare everyone else the suspense. You get "1". Hello dereferencing
pointers.
I also did this:
put 1 into a
put "a" into b
put "b" into c
put value(c)
which gives me "a", which I half-expected, but if I put value(value(c)) I
still get "1", so now I can also build handles as w
Well, it all started in 1987.
("a"), and (quote & "a" & quote) are not the same thing at all. One is a
literal and the other is a variable.
put 1 into a
put "a" into b
put value(b)
You could have just "put b". But in any case, the variable "a" was created and
loaded with a "1". Then the v
If someone is going to tell me that I just forgot this, and it's well-known
behavior, I'm going to have a small cow, because I was of the impression
that we were pointer-less. Maybe not.
put 1 into a
put "a" into b
put value(b)
Welcome to the Tao of LiveCode. Again. G. All those
On 28/07/14 18:32, Muaadh Salih wrote:
Before I report this as another bug in this dp version could any colleague
replicate the following and confirm that the is correct ? Please :
the potential bug in
ID
,
Windows 7 , Livecode 7 dp 7
Open new main stack OK
choose menu -->
Obje
Hi Muaadh,
It looks like there are many similar crashes, related to creating new
controls from the menu or the tools palette.
We reported this bug
http://quality.runrev.com/show_bug.cgi?id=12893
last week and RunRev has added a few duplicate bugs to our report, which
seem to be related. The p
Before I report this as another bug in this dp version could any colleague
replicate the following and confirm that the is correct ? Please :
the potential bug in
ID
,
Windows 7 , Livecode 7 dp 7
Open new main stack OK
choose menu -->
Object>
new control >
field --
19 matches
Mail list logo
