[jawsscripts] Re: HSCDecodeHotspotColors

No, it doesn't auto ask me what phrase I want spoken.  I just typed in all 
of the code manually.
My second question is that I really want to make sure that the hotspot only 
runs if there is only two designated colors and nothing else.
----- Original Message ----- 
From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Sunday, June 14, 2009 8:37 PM
Subject: [jawsscripts] Re: HSCDecodeHotspotColors


> yep, so, you just activate the hotspot again, which presumably you've set 
> to
> an action of a left mouse click, then it wil click there, presumably if 
> set
> on the correct pixel,
> cause a new color to be displayed there, then it should auto ask you, what
> phrase would you like spoken when xxx xxx xxx color is found. and it'll 
> keep
> doing that, whenever you activate the hotspot, whilstever each click 
> action
> results in it finding a new color there it doesn't have an associated 
> phrase
> for.
> is this not what's happening for you?
> in answer to your secondary question about multiple colors, well, I'm not
> sure I understand what your exactly asking/needing here, but the short
> answer is, yes, the single vertical bar character, single not double mind
> you,
> can be used to separate RGB strings, particularly in the, "color=" field,
> where color searches are being performed in situations where the spot 
> might
> move etc, and you wanna search for a particular colored pixel in a given
> area or direction.
> However, again, I'm not exactly sure
> whether this would work in the hscDecodeHotSpotColor fields.
> I haven't actually tested them that way, rather than leaving them as the
> definition editor codes them, i.e. one line per color per 
> function/phrase.
> I guess you could test it and let us all know, if it works with vertical 
> bar
> separators in those fields, but I can personally see no advantage of doing
> that,
> other than elegance/neatness of code. Am I missing something?
>
>
> geoff c.
> ----- Original Message ----- 
> From: "GianniP46" <giannip46@xxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Monday, June 15, 2009 5:30 AM
> Subject: [jawsscripts] Re: HSCDecodeHotspotColors
>
>
>> yes, I got that far, but now I want hsc to say something else for a 
>> second
> color
>>   ----- Original Message ----- 
>>   From: Geoff Chapman
>>   To: jawsscripts@xxxxxxxxxxxxx
>>   Sent: Sunday, June 14, 2009 11:17 AM
>>   Subject: [jawsscripts] Re: HSCDecodeHotspotColors
>>
>>   Hi gian,
>>   oh man! I've been meaning to answer this queery of yours re color
>>   identification and reporting differing feedback based on state of color
> at a
>>   particular spot,
>>   and in fact started an answer to what I know was your second attempt at
>>   getting a, "how to," on this,
>>   1.5 weeks ago but never finished it! I'm soooo sorry about this man.
> I'll
>>   try and get to it tomorrow though eh. I wanna go to bed here now, but I
>>   think I may have
>>   something helpful to contribute on this for you, which is a simpler
> approach
>>   than the one that I think was suggested by doug or dennis on list last
> week,
>>   though their method might very well be more comprehensive.
>>   What's your skype User ID? maybe it'd be quicker to talk about it all
> than
>>   write it down?
>>
>>   but your key to doing this is a post processing hsc function called
>>   hscDecodeHotSpotColor.  and it should be found under the
>>   Control+Alt+Shift+f3 menu, after you've assigned your hotspot.
>>   But, first make sure that your hotspot, is over a pixel which alters
> color
>>   to reflect the state of whatever control this is, that your wanting
> feedback
>>   on when you click it.
>>   use the alt+shift+NumPad5 Keystroke, to determine this pixel's color,
> when
>>   the button or whatever it is,
>>   is in a certain state, then manually click the NumPad slash key at that
>>   location,
>>   and then checking again with Alt+Shift+Numpad 5, to check what color
> that
>>   pixel now is, in the button's new state etc, so you maybe will get to
>>   remember what color is associated with what state.
>>   then when your sure your mouse is over a pixel that will reliably
> reflect
>>   this change at your spot, then go ahead and define your spot in the
> normal
>>   way using the altControlShiftA wizard.
>>   then when your done, first insure the mouse hasn't moved from your 
>> spot,
> and
>>   then do the post processing assign command, alt+control+shift+f3.
>>   you should be offered a list of post processing functions to assign to
> your
>>   hotspot.
>>   choose hscDecodeHotSpotColor, and follow the prompts. i.e. choose the
> action
>>   you want to happen when xx color is found, then which should be I think
>>   hsdSayPhraseByColor, or something like that.
>>   then activate the spot with the keystroke you assigned to it, as
> directed,
>>   and type in the phrase to be spoken when it clikcs, and finds xx color
> there
>>   etc.
>>
>>   I hope this helps.
>>   ----- Original Message ----- 
>>   From: "GianniP46" <giannip46@xxxxxxxxxxxxx>
>>   To: "JawsScriptsList" <JawsScripts@xxxxxxxxxxxxx>
>>   Sent: Sunday, June 14, 2009 2:47 AM
>>   Subject: [jawsscripts] HSCDecodeHotspotColors
>>
>>
>>   > OK Folks,
>>   > I got this function to work after a hotspot, but I want to have two
> colors
>>   recognized and a different message for each color spoken.  The help 
>> says
> to
>>   put an F after the RGB string.  Does anyone have some examples of this
> that
>>   I can see?  I am not sure exactly what is suppose to happen.
>>   >
>>   > Gian Pedulla GianniP46@xxxxxxxxxxxxx
>>   >
>>   > LETS! GO! METS!
>>   > __________
>>   > 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
>>
>>
>>
>> --------------------------------------------------------------------------
> ----
>>
>>
>>
>>   No virus found in this incoming message.
>>   Checked by AVG - www.avg.com
>>   Version: 8.5.364 / Virus Database: 270.12.68/2175 - Release Date:
> 06/14/09 05:53:00
>>
>> __________
>> 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
>
> 

__________ 
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: