Thanks for the update; that is great news! There is a possibility I will be attending CSUN for the first time this year. If you decide to demo WE4Java at CSUN, I'd love to be there.
I kind of had the feeling the line reading for the mouse was going to get complex. :) Couldn't really see how it wouldn't and be done successfully. I'm working on the algorithm for WE4Java now. Just wanted to make sure I wasn't making this harder than it might be. :) -----Original Message----- From: Michael D. Lawler [mailto:[email protected]] Sent: Friday, January 30, 2009 3:45 PM To: [email protected] Subject: Re: We4Java 0.9.10 coming soon - A question and an observation Well here is our stamp of aproval for your current direction. Doug showed this at ATIA so we are truly excited about where you are taking this. Our line building code is actually complex and I'm certainly not the person to try to explain it. We look at clips horizontally, but we also allow for margins of error to allow for different font sizes that will change the height of the line for example so it becomes complex. At 04:16 PM 1/30/2009, you wrote: >All, >WE4Java 0.9.10 is coming out soon.. Main 2 features with this release >are better mouse tracking and the return of sound profiles. > >The Mouse tracking is improved and the top-left and route mouse to >focus hotkeys are working (hoping for others by release time). Mouse >tracking also makes use of the new sound profiles ability. It can play >different sounds when the mouse crosses window borders, enters tool >bars or menu bars, or moves from one panel of a screen into another. > >Sound profiles is the return of the sound feedback from a prior >release. WE4Java now uses the PlaySound method call for this feature >and thus, doesn't interrupt the speech. All sound profiles info is now >contained in the WE4Java.ini file. The SoundProfile= value in the >Settings section tells what sound profile to use or can be set to None >for no sound feedback. The value of the soundProfile value is really >just another section name in the ini file; so, you can either use one >of the 2 included sections; WE4JavaSounds or WESounds; or you can make >up your own. The values in the profile section (e.g., BorderCrossing=, >WindowOpen=, etc.) simply specify the name of the wav file to use; so, >you can change or remove sound for any event you like. > >Here is 1 question and 1 observation mainly for the GW folks: > >If I am coding for mouse read line, how do you normally handle tracking >across the line to see what should be read? Do you simply move the >mouse along the y axis reading as you go or do you employ some other >method? > >An observation. I have received much feedback from a number of the list >participants but not much recently from GW team members. >Perhaps, this is simply because it has taken a while to work through >the Vista issue and not a lot of new functionality has been in the last >couple of releases. I just want to make sure I am still driving this >project down a path acceptable to GW Micro. > -- Michael D. Lawler Voice 260-489-3671 Fax 260-489-2608 Internet mailto:[email protected] web http://www.gwmicro.com ftp ftp://ftp.gwmicro.com GW Micro, Inc., Development Liaison and Technical Support Supervisor
