Rick,
It still looks to me as though you are creating a new object (with the "new
initProc" statement), which immediately handles the initialization you want,
but then just as soon goes out of context becaust you aren't assigning it to
a global variable. I think therefore, you've still got every
Woops! Meant to say, "and NOT a full fledged solution."
Aaron
On 6/22/2012 11:38 AM, Aaron Smith wrote:
I'm sure there's more bulletproofing that needs to be done to make
sure that the accessible is valid before using it (ie.If Not accObj Is
Nothing Then). Understand that, this being the scrip
I'm sure there's more bulletproofing that needs to be done to make sure
that the accessible is valid before using it (ie.If Not accObj Is
Nothing Then). Understand that, this being the scripting list, I was
providing a simple proof of concept, and a full fledged solution to
Foobar's accessibili
Ok, when i did this the list view works but when i go to alt f 4 out of the
my documents where i have the portable version of foobar 2000 i get another
error message but can not copy it it goes away to quickly what can i do?
- Original Message -
From: "Aaron Smith"
To:
Sent: Friday, J
That means that the text you copied didn't work wrap correctly. Just
delete the line that starts with OutputDebugString, and the line that
has just & vbCrLf. Once those two lines are gone, that should take care
of it.
Aaron
On 6/22/2012 10:23 AM, Life My Way wrote:
Ok, this is what i get usi
Ok, this is what i get using the virtual view script to copy it.
Foobar media player.vbs - Microsoft VBScript compilation ...
Line 9 Column 1
ยท& vbCrLf
Expected statement
< 0x800A0400 >
Ignore Error Stop App Edit App View Help Restart App
- Original Message -
From: "Aaron Smith"
To:
Cc:
Hi Rick,
As I had sent you a threading issue, what you are seeing is all about
timing and who is getting in first. Also as Chip had pointed out, by the time
the second event has happened, are we out of scope? Has everything changed? All
when the second event comes along in the Queue, for y
Sure. What was the error you received?
Aaron
On 6/21/2012 8:17 PM, Life My Way wrote:
Arron, when i tried and place this script into window eyes i get an error
message not sure what it is though that it will not work. can you check it
out please?
- Original Message -
From: "Aaron Smith"
Hi Steve:
The AddHandler statement uses a Delegate and is set up by the Compiler.
I have used native Delegates in my script but I dont think I tried using them
with the Keyboard event handlers.
Hay, it is something to try and I'll do it and post up if that works later
today or tomorrow.
I
Hi again Guys:
I went back to Aaron's original sample to start from a solid base.
I just flipped the AddHandlers and found that makes a diference in which
handler function in my script gets executed and which is not executed.
I define a keyboard object as follows in the global module:
Public WithE
Rick,
If memory serves, the VB .net example on App Central employs delegates. I'm not
currently in a position to review it, but it's well worth a look if you haven't
gone through it already.
Steve
Original Message
From: RicksPlace
Sent: Fri Jun 22 03:34:37 EDT 2012
To: gw-
Hi Guys:
I found an Excel example of using what appears to be delegates and set up my
code to match the delegate portion of the code using the WindowEyes handlers
exposed in the error message noted in the prior post.
The underlying target application, vb.net 2010 express, still seems to lock up
Hi Guys: I tried to setup a standard Delegate, could be a error in my code but
got this message.
Value of type
'VBNet2010WETester.LaunchApp.KeyDownDelegate'
cannot be converted to
WindowEyes.KeyEvents_OnKeyDownEventHandler
Is there some documentation on the
WindowEyes.KeyEvents_OnKeyDownEventHa
13 matches
Mail list logo
