[jawsscripts] Re: Launching a Script From a frame
- From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Fri, 21 Aug 2009 23:56:40 +1000
Hi Steven.
man did you not see the response I posted to this a few days ago? did it
not answer this question adequately for you?
I'll repost below in hopes that perhaps you missed the first one, or, if
not, perhaps you would post back what further information you feel is
lacking in it,
in order to do what your requesting below.
It is written relatively rambingly, and perhaps not clearly enough.
***
Martin, mightn't it be simpler, for him to do it the other way?
I think for kinda hnewbys scripters I mean, like it sounds like Stephen
might kinda be? and which I am also?
> else he'd have to have knowledge of Scheduling functions would he not?
> which is another level of complexity.
>
> sounds to me like Stephen's taking the path I took, which is to stretch
> frames manager to it's ultimate, then kick in with scripts to make up the
> shortfall, which is not the way I know that most programmers tend to
do things. they tend to disregard frames and frames manager
> entirely, and do everything with scripts. But, this requires much more
> knowledge in my view of the scripting language and functions etc.
>
> by all means try martin's suggestion Stephen, but, for what it's worth,
> personally I'd be trying to do it the reverse way, i.e. assign what's
called an "onText event," to the frame your dealing with, in frames manager.
> and, then, for what frames manager calls the, "action," for that OnText
> event, from the 25 choices it'll give you,
> you should assign/choose, "Run Script event." which, mind you, is
different than, "run script." in here.
> the action, "run script event," really means to run a function, which is
not assigned to a key.
you can of course, choose runScript, if the script/function you've designed,
to do this extra work your talking about, is assigned to a key, and is thus
really a script, rather than a function.
If you choose RunScript, then hitting enter will present you with a list of
Scripts, from which you can choose and hit enter, rather than having to type
the name of the function directly in an edit box type arrangement, as you
must do with the RunScriptEvent option.
Assuming you do wish to run a function, rather than a script,
when you choose the action of RunScriptEvent, and hit enter, it'll then
present you with an
> edit box, in which you must then paste the name of your function, the one
> your building to do the other work/checking of your grabbed value from the
frame,
etc.
However, when writing it, don't put the parenthisies after it's name, as you
normally have to in script manager, as
> you'd know.
>
> of course this action can only run a function which doesn't contain
> parameters in here by the way, so this excludes some functions obviously.
> I mean, the function name you wish to have run here, when the text in the
> frame changes, must not have anything in the parenthisies after it's name,
as it is defined in the script manager.
>
>
Have you done much work/investigation in the actual properties dialog
> of frames you've defined, using frames manager yet?
>
> Do you have knowledge of how to do what I've suggested above?
> It's bed time for me here so I won't be able to explain it all blow by
blow now tonight, but, from your feedback to this, I guess we will know
whether
> you will be aware of where to begin investigation, or, to ask more
questions if you need more
> indepth information.
>
> in short though, firstly, you build the function in script manager that's
gunna do
> the grunt work/checking for you,
> then you altTab back to the application, go into frames manager,
> with insert+top Row 9, then tab around till you find your frame that
you've obviously set up to trigger upon text changing etc.
> hit altEnter to go into it's properties, and in here you'll find 4 tab
> controls. shif+Tab as usual to get to them so you can right/left arrow
> among them.
> you should become thoroughly familiar with frames if you feel you wanna
> begin utilizing them in your work, though many scripters will tell you
it's better to avoid them because of their tendencies to be very screen
> resolution dependent, and of course window size dependent as well.
But I personally have found them most practical and useful, so long as the
system your running them on is relatively static.
so anyway, inside the frame's properties dialog box,
find your third tab along, which is your events tab.
> then tab once, and you'll be on the list of events already assigned, that
were assigned their auotmatically when you initially defined your frame to
> watch for this text change, or whatever.
> there might only be one or two events there. so then you hit alt+a, to
add a new event, and you'll start the, "create event," wizard. you'll get
4
> choices initially, OnFocus, OnFrameKey, On Play Action, and OnText. as
you arrow among them, you'll get little auto explanations for each one.
choose the onText event, and hit enter.
> then you'll be asked to select the attributes or specific text to serve as
a filter to trigger the action your about to assign.
> if you want it to trigger upon any change at all, then just hit enter
here. but, if you want only certain atributes to trigger this action, or
certain specific text to trigger it, i.e. when some certain number appears
in that frame or
> whatever, so long as of course you know it'll only appear once etc, then
> hit alt+t to jump to the edit box for this purpose,
and specify that text
> here. be aware it's case sensitive as well. then hit enter.
> then you'll be in the, "event scope," part of the wizard. you can
> investigate this, but I almost always leave this at it's default, which is
> to, "recognize this event all the time."
> hit enter.
> then you'll be in perhaps the main aspect of the event assignment
procedure,
which is called frame actions. and
> you'll be focused on a 25 entry list of actions you can assign to this
> ontext event. as I say above, choose Run Script Event, not Run Script I
> reckon, so long as what you've got to assign is a function, and not a
script
> assigned to a key. else which of course you'd choose Run Script instead.
> hit enter.
> then you'll have your edit box into which you must type or paste the name
of the function that you're wanting the onText change in the frame,
to launch for you. it must obviously have no errors, and must not be writte
with it's parenthisies after it.
> then hit enter. that concludes the event assignment wizard.
> now you should be back in your third events tab of your frame properties,
and on
the list of events assigned to that frame. you can arrow up and down and
check
that your new onText event/action is really there, and, very handily I
believe this feature is, I'm
> extremely greatful to whomever had the foresight to put this in here, you
> can then flip the whole event on/off with space bar, as desired. great
for debugging and testing things.
> so then tab around to ok and hit enter.
> then hit escape to leave frames manager,
> and when it asks you to save, hit Y for yes.
>
> that should do it.
>
----- Original Message -----
From: "Steven Hicks (HICKSSM)" <Steven.HicksSM@xxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, August 21, 2009 11:01 PM
Subject: [jawsscripts] Launching a Script From a frame
> Hi friends,
> not sure if this is possible but I have a frame set up to monitor an area
of the screen.
> The frame executes when the screen area changes.
> would it be possible to launch a script when the frame is executed e.g.
when the screen area changes, I would like to copy the value to a variable
and do some checks on it.
>
>
> --------------------------------------------------------------------------
---------------
> The information in this e-mail and any attachments is
> confidential and is intended for the attention and use of the
> named addressee(s). It must not be disclosed to any other
> person without our authority. If you are not the intended
> recipient, or a person responsible for delivering it to
> the intended recipient or are aware that this e-mail has been
> sent to you in error, you are not authorised to and must not
> disclose, copy, distribute, or retain this message or any part of it.
>
> We sweep all outgoing messages for the presence of computer
> viruses. However, we cannot accept any responsibility for any
> loss or damage to your systems due to viruses or malicious
> code not detected.
>
> The statements and opinions expressed in this message are
> those of the author and do not necessarily reflect those of the
> organisations within the Cornwall & Isles of Scilly Health
> Community.
>
> This email may be disclosed under the Freedom of Information
> Act 2000 or the Environmental Information Regulations 2004.
> --------------------------------------------------------------------------
---------------
>
> __________
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> http://www.freelists.org/list/jawsscripts
>
__________
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: