Graham Heather Harrison wrote:
Jacque wrote:
It works the simple way for me. I just dropped the external into
that folder, restarted Rev, made a new stack, and made a call to
the external from the stack script. Worked okay.
All aboard the Merry-go-round!
That looks like the place I came
Mark Wieder wrote:
So you need to create this folder yourself. Then you need to tell rev about
it:
Go to rev's preferences under Files Memory, click the browse button next
to User Extensions, and select the folder you just created.
So you and Jacque say. But I reiterate: This does not
Graham Heather Harrison wrote:
Mark Wieder wrote:
So you need to create this folder yourself. Then you need to tell
rev about it: Go to rev's preferences under Files Memory, click
the browse button next to User Extensions, and select the folder
you just created.
So you and Jacque say. But
From: J. Landman Gay
If so, then it looks like I could
simplify my code, and just do everything in the startup handler.
That's what I do. :)
Okay, now I'm a little puzzled. I removed all the old stuff about creating a
template stack, adding the externals property to it, and then using it
Le 4 mai 2010 à 04:37, Graham Heather Harrison a écrit :
Jacque wrote:
But look at the nice thread you started.
Yes, it has been very informative… and civilised.
Note: If you reference externals or externalPackages for me or this
stack, your new External will not appear.
Sorry.
Okay, now I'm a little puzzled. I removed all the old stuff about creating a
template stack, adding the externals property to it, and then using it to
create a dummy stack. I then added the following code to my main stack
script:
on startup
if the platform is Win32 then
set the
From: Thierry D.
A guess : your external is launched from another stack.
A second guess : you have already launched your external before
starting your stack,
or say other way, the previous time you launched your external,
it didn't close
properly and keep running in the IDE.
I figured
Mark Wieder wrote:
Try this in a button:
on mouseUp
answer file where is the library file?
if it is not empty then
set the externals of this stack to it
save this stack
revert
end if
end mouseUp
That's pretty much the same as the test I asked Graham to do before,
except
Paul D. DeRocco wrote:
From: J. Landman Gay
If so, then it looks like I could
simplify my code, and just do everything in the startup handler.
That's what I do. :)
Okay, now I'm a little puzzled. I removed all the old stuff about creating a
template stack, adding the externals property to
I sent this (except for the final point) to the wrong address. So here it is to
the right one.
All together now,
No! No! A thousand times no! I'd rather die than say yes!
Mark Wieder wrote: No…NoNoNoNo…No
Thierry D. wrote: I second what Mark Wieder says
I feel as if I've run afoul of the
From: Graham Heather Harrison
. As I have read (this thread or elsewhere) the handling of
Externals is different in the IDE and standalones. From the
discussion between Jacque and Paul this is not straightforward,
and is not handled in the documentation. It would appear that the
script as
Graham Heather Harrison wrote:
Jacque, I wish using ../Documents/Revolution …/Externals was as
simple as you say. It really should be: put your external in, restart
rev, done, dusted, sorted. But no, you still have to write script in
each new stack to point to each External individually.
It
Jacque wrote:
It works the simple way for me. I just dropped the external into that folder,
restarted Rev, made a new stack, and made a call to the external from the
stack script. Worked okay.
All aboard the Merry-go-round!
That looks like the place I came in. This still does not work for
Having exhausted all conceivable testing scenarios (including suggestions from
this list, available lessons and tutorials) to get rev to recognise Shao Sean's
ssMacWindows external, I was forced to confront the Sherlock Holmesian
alternative that the problem might lie with ssMacWindows. A long
Graham Heather Harrison wrote:
Whether ssMacWindows has a problem with rev 4.0.0, or Mac OS X 10.6.3
I can't say, and I have not found a way to contact Shao Sean; there
is no link on his web site. Can anyone help me with contact
information, or who best to ask at Rev?
She reads this list so
From: J. Landman Gay
I don't think so. As far as I know, nothing's changed in the way
externals work in years. There have been some new ways of forcing them
to load (new as of a few years ago,) but the underlying principle of
it is the same as always: externals only load when a stack is
Graham Heather Harrison wrote:
Having exhausted all conceivable testing scenarios (including
suggestions from this list, available lessons and tutorials) to get
rev to recognise Shao Sean's ssMacWindows external, I was forced to
confront the Sherlock Holmesian alternative that the problem might
Paul D. DeRocco wrote:
From: J. Landman Gay
I don't think so. As far as I know, nothing's changed in the way
externals work in years. There have been some new ways of forcing them
to load (new as of a few years ago,) but the underlying principle of
it is the same as always: externals only load
From: J. Landman Gay
The dummy stack trick is just a clever work-around to allow you to load
an external on demand. It isn't required. It sounds like what changed
was the standalone builder rather than the way externals work, but I'm
not sure either how that works under the hood.
Le 3 mai 2010 à 19:56, J. Landman Gay a écrit :
The dummy stack trick is just a clever work-around to allow you to load an
external on demand. It isn't required. It sounds like what changed was the
standalone builder rather than the way externals work, but I'm not sure
either how that
Thierry, Paul,
Thierry said:
Concerning your recipie from the previous email, it works only in your context.
Pass your stack and your external to someone, and you're stuck again !
Yes, I warned about that and mentioned that a relative file path would
be necessary for portability. My example
Jacque wrote:
on mouseUp
ssSetWindowModified the windowID of this stack, true
end mouseUp
Make sure you include the ss part of the ssSetWindowModified command. (In
one of your previous posts it was omitted.)
Well blow me down! If that doesn't bilge the barnacles.
All this time I
Graham Heather Harrison wrote:
Well blow me down! If that doesn't bilge the barnacles.
I've never heard that before! That's almost as good as linguistic
psychedelics from the Thread That Shall Not Be Named. :)
One of those times when, because there is a known difficulty,
everyone
From: J. Landman Gay
Startup is the only time you can set the externals of a stack and have
it work. The handler will never trigger during development because the
IDE gets the startup message. But when running as a standalone, the
mainstack will get a startup message and the externals get
Paul D. DeRocco wrote:
From: J. Landman Gay
Startup is the only time you can set the externals of a stack and have
it work. The handler will never trigger during development because the
IDE gets the startup message. But when running as a standalone, the
mainstack will get a startup message and
From: J. Landman Gay
As someone who's just learned enough of Revolution to write one
rather basic
app, I'm having trouble understanding the documentation on the startup
message. The docs mostly seem to be about U3 drives, which is
irrelevant,
but the example implies that in a non-U3
Jacque wrote:
But look at the nice thread you started.
Yes, it has been very informative… and civilised.
Taking as much on board as I can, these would be my suggestions for someone
still on the rev learning curve, who is working on one platform (probably true
for most while learning), and
Graham-
OMG.
Where did you get these ideas?
Monday, May 3, 2010, 7:37:23 PM, you wrote:
1) Ignore whatever is in User Extensions in Preferences/Files
Memory. It will not affect you at all.
No reason why it should.
2) Put your platform External into the equivalent of
../Revolution
Graham-
Saturday, May 1, 2010, 8:56:43 PM, you wrote:
I started with the lesson I quoted but sort of diverged and only
had a small section of the code. By the time I posted the question
on revert I was more interested in just that, than the full
externals bit.
Your original message was
Graham-
Friday, April 30, 2010, 10:34:00 PM, you wrote:
In the first rev lesson on externals at
http://lessons.runrev.com/spaces/lessons/buckets/784/lessons/7116-How-to-safely-attach-an-external-to-your-stack,
after saving the stack this statement is issued:
send revert to me in 5 ticks --
Graham Heather Harrison wrote:
In the first rev lesson on externals at
http://lessons.runrev.com/spaces/lessons/buckets/784/lessons/7116-How-to-safely-attach-an-external-to-your-stack,
after saving the stack this statement is issued:
send revert to me in 5 ticks -- the equivalent of quit then
Mark Wieder wrote:
Try looking in the externals instead of the externalPackages.
It wasn't me looking in the externalPackages, Guv. Honest to God. Never went
near 'em. Swelp me.
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please
Graham-
Saturday, May 1, 2010, 5:03:01 PM, you wrote:
Mark Wieder wrote:
Try looking in the externals instead of the externalPackages.
It wasn't me looking in the externalPackages, Guv. Honest to God. Never went
near 'em. Swelp me.
Hmmm. You sure we're looking at the same lesson?
--
Jacque and Mark (W)
I started with the lesson I quoted but sort of diverged and only had a small
section of the code. By the time I posted the question on revert I was more
interested in just that, than the full externals bit.
Jacque: I was wondering in the back of my mind how rev could
In the first rev lesson on externals at
http://lessons.runrev.com/spaces/lessons/buckets/784/lessons/7116-How-to-safely-attach-an-external-to-your-stack,
after saving the stack this statement is issued:
send revert to me in 5 ticks -- the equivalent of quit then restart.
When I use this under
In the rev Preferences there is a field User Extensions which has the file
path of the folder holding user externals. I can't get a tooltip on this, so
how do I access this from a rev script?
___
use-revolution mailing list
Graham Heather Harrison,
Why would you want to access this from a rev script? Once you deploy
your software, no one is interested in your My Revolution Enterprise/
Studio folder.
What exactly do you want to do?
Inside the IDE, you can call the choosecustomizationpath command.
--
Best
Mark Schonewille wrote:
Why would you want to access this from a rev script? Once you deploy your
software, no one is interested in your My Revolution Enterprise/Studio
folder.
What exactly do you want to do?
Inside the IDE, you can call the choosecustomizationpath command.
I am
Hi Graham Heather Harrison,
If I uderstand you correctly, you want your script to find out where
the My Revolution folder resides, in case the user changed it. To get
this path, you can use the revEnvironmentCustomizationPath() function.
This function isn't documented either ;-) and this
Graham Heather Harrison wrote:
I am nowhere near deploying, just learning. This parameter is
available, but seemingly not used by rev until you rub it's nose in
it. Since I dislike doing things twice, I see no reason to repeat the
information in a rev script. And the two lessons available, get
Jacque wrote:
For now, use a hard-coded file path specific to your Mac. Save the stack,
close it, reopen it, the external should be available. This isn't a portable
solution, due to the hard-coded file path, but it will let you continue
working and learning. You can fix it later.
Fair
Graham Heather Harrison wrote:
But I am a magpie learner (and always looking for elegant
solutions), so this seemed like a good time to chase up relative file
paths. The explanations in the guide and dictionary references, like
so many others, appear to have been written for people who knew it
Sean helped me with the placement. I put it in two places with the External.txt
file that contained ssMacWindows,ssmacwindows.bundle in both locations with
the bundles.
Documents/My Revolution Enterprise/Externals/
Documents/My Revolution Enterprise/Runtime/Mac OS X/Universal/Externals/
And
I am trying to use Shao Sean's ssMacWindows, following his instructions in
RevUp Issue 79. Wasn't sure If I should place the ssMacWindows162 folder into
~/Documents/My Revolution Studio/Externals/, or unpack it there, so tried both.
The first example is to create a field with the following
Graham Heather Harrison wrote:
I am trying to use Shao Sean's ssMacWindows, following his
instructions in RevUp Issue 79. Wasn't sure If I should place the
ssMacWindows162 folder into ~/Documents/My Revolution
Studio/Externals/, or unpack it there, so tried both.
The first example is to create
Jacque wrote:
Rev can't find the external. The handler it's missing is one of the
calls in the external library.
So since I put it where instructed, and where rev Preferences says to look, why
is it missing?
Externals are a little bit advanced. They aren't hard exactly but I'm
not sure
From: Graham Heather Harrison
Does this mean that using an external is not just a case of
putting it in the appropriate library and Voila!? In that case I
will have to look at these lessons…
I don't know what the instructions you followed said, but you need to bind
the external to your app
Graham Heather Harrison wrote:
Jacque wrote:
Rev can't find the external. The handler it's missing is one of
the calls in the external library.
So since I put it where instructed, and where rev Preferences says to
look, why is it missing?
You need to tell the stack to use it. Or,
48 matches
Mail list logo
