[ddots-l] Re: hsc build 198 did not fix my issue and I am still not able to read certain things in sonar.

  • From: "Charles Marston" <rumbero73@xxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Sun, 26 Sep 2010 09:49:04 -0400

Thank you.



From: Phil Muir 
Sent: Saturday, September 25, 2010 5:31 PM
To: ddots-l@xxxxxxxxxxxxx 
Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


Yes, you can remove Window Classes or, comment them out and that's the correct 
way to do this.  Always remove Window Classes if I get issues like that.  or, 
change the line so that it looks like this:

WindoClass=*




Regards, Phil Muir
Accessibility Training
Telephone: US (615) 713-2021
UK +44-1747-821-794
Mobile: UK +44-7968-136-246
E-mail:
info@xxxxxxxxxxxxxxxxxxxxxxxxxxx
URL:
http://www.accessibilitytraining.co.uk/ 





--------------------------------------------------------------------------------
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of D!J!X!
Sent: 25 September 2010 22:24
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


This means that the window classes for the program are dynamic and not static, 
meaning that they're not hard coded into the program, but instead, the program 
assigns the classes to the windows at runtime or when the program creates them. 
This is 1 of the principals of jaws scripting, always look for static 
information to rely on for window manipulations; in the case of hsc, this is 
why you normally use a part of the window title that is static to all windows 
of that plug-in, for example, remove any project name or numbers that change 
and keep the basic title so that hsc always looks for that along with other 
details.
I'm not sure if hsc gives you the option, but if it does, then for that 
particular plug-in, don't use the window class as a requirement for the set.

HTH, D!J!X!


--------------------------------------------------------------------------------
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Charles Marston
Sent: Saturday, September 25, 2010 4:59 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


Phil:
I don't know if this is a related issue.  I installed HSC 198, which is the 
first version that I have ever used.  I have JAWS 11, and the latest version of 
CT and Sonar.  I created some hot spots for SanpleTank.  They worked find as 
soon as I created them.  However, after I closed the program and opened it 
again, non of the hot spots worked.  I got the same error message as reported 
in the messages below.  When I used the debug feature, it told me that the 
problem was the window class.  It expected IKM1450097, but it found instead 
IKM1370093, or something like that.  After consulting the manual, I used the 
editor feature and changed the window class number.  Again, the spots worked 
just fine after the fix, however, they did not worked after I closed and 
reopened the program.  The confusing thing is that the debug feature gave me 
the same message about expecting IKM 145... and finding instead IKM 137...  I 
checked the settings for the spot using the editor feature, and the window 
class number was correct.  Still the spots were not working.
After reading somemore of the manual, I went ahead and placed an asterisc to 
the left of the window class line to have HSC ignore that parameter.  Now the 
spots are working just fine.
Has anybody else gotten the same message about the window class not being 
correct?  Did I take the right corrective measure?



From: Phil Muir 
Sent: Saturday, September 25, 2010 6:07 AM
To: ddots-l@xxxxxxxxxxxxx 
Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


Not seeing that here at all.  HSC is working as advertised.  Think there's 
something goofy going on on your system as you are the only one who's reported 
that particular issue.  Time for a reinstall I think.




Regards, Phil Muir
Accessibility Training
Telephone: US (615) 713-2021
UK +44-1747-821-794
Mobile: UK +44-7968-136-246
E-mail:
info@xxxxxxxxxxxxxxxxxxxxxxxxxxx
URL:
http://www.accessibilitytraining.co.uk/ 





--------------------------------------------------------------------------------
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Omar Binno
Sent: 25 September 2010 10:43
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


Correct, Steve. Also, with Sonar 8.5, it seems that you can't use a lot of the 
hsc shortcut keys. You have to activate a particular command by getting to it 
from the menus.
  ----- Original Message ----- 
  From: Steve Wicketts 
  To: ddots-l@xxxxxxxxxxxxx 
  Sent: Saturday, September 25, 2010 4:56 AM
  Subject: [ddots-l] Re: hsc build 198 did not fix my issue and I am still not 
able to read certain things in sonar.


  Cameron,

  Forgive me if I'm stating the obvious with HSC, have you used it before, as 
  I always go to synth rack (Alt 8) arrow down to the particular synth I 
  want,press P and then start using hot spot clicker.

  Steve W

  From: "Cameron" <cameron@xxxxxxxxxxxxxxxxx>
  To: <ddots-l@xxxxxxxxxxxxx>
  Sent: Saturday, September 25, 2010 4:56 AM
  Subject: [ddots-l] hsc build 198 did not fix my issue and I am still not 
  able to read certain things in sonar.


  > Hello everyone.  I installed hsc build 198 this evening and it did not fix
  > my issue.  I am still getting the window not found, hot spot failed 
  > message
  > whenever I try to use hsc sets with any of the soft synths included with
  > sonar 8.5 producer.  I made sure the proper hsc set was loaded, and I also
  > tried picking things from the list instead of using the hsc command and I
  > just get the same error message.
  >
  > On Sunday, I'm going to have a friend help me install a seperat partition 
  > on
  > my system drive that will be for sonar only.  until then, is anyone else
  > experiencing this?
  >
  > I don't get it.  I'm using the latest hsc sets, latest version of jsonar,
  > latest version of jaws ten, all my display settings are correct, yada yada
  > yada...  and there don't appear to be any dialogue boxes etc blocking the
  > dimension pro window for example, at least nothing that the virtual viewer
  > or jaws cursor can see.
  >
  > I can see the presets box with the jaws cursor and the pc cursor in
  > dimension pro, rapture le, etc so why doesn't the virtual mouse click that
  > hsc does work?
  >
  > Also, for some reason, jaws is not reading things in lists and it's not
  > reading page tabs in dialogue boxes etc.  it just says tab, when it should
  > say general or drivers etc.
  >
  > This is only happening in sonar though, even after a total reinstall of
  > everything.
  >
  > Anyone have any explanations or further suggestions?
  >
  > This happens with both JSonar and the latest version of ct.  I've tried
  > both.
  >
  > Thanks,
  >
  > Cameron.
  >
  > PLEASE READ THIS FOOTER AT LEAST ONCE!
  > To leave the list, click on the immediately following link:
  > ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
  > If this link doesn't work then send a message to:
  > ddots-l-request@xxxxxxxxxxxxx
  > and in the Subject line type
  > unsubscribe
  > For other list commands such as vacation mode,
  > click on the immediately following link:
  > ddots-l-request@xxxxxxxxxxxxx?subject=faq or
  > send a message, to
  > ddots-l-request@xxxxxxxxxxxxx
  > and in the Subject line type
  > faq
  >
  >
  > __________ Information from ESET NOD32 Antivirus, version of virus 
  > signature database 5477 (20100924) __________
  >
  > The message was checked by ESET NOD32 Antivirus.
  >
  > http://www.eset.com
  >
  >
  > 


  __________ Information from ESET NOD32 Antivirus, version of virus signature 
database 5477 (20100924) __________

  The message was checked by ESET NOD32 Antivirus.

  http://www.eset.com




  PLEASE READ THIS FOOTER AT LEAST ONCE!
  To leave the list, click on the immediately following link:
  ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
  If this link doesn't work then send a message to:
  ddots-l-request@xxxxxxxxxxxxx
  and in the Subject line type
  unsubscribe
  For other list commands such as vacation mode, 
  click on the immediately following link:
  ddots-l-request@xxxxxxxxxxxxx?subject=faq or
  send a message, to 
  ddots-l-request@xxxxxxxxxxxxx
  and in the Subject line type
  faq

Other related posts: