yes just worked that out, PM on the way
Thanks for the work cool dude it works, I gave it a try with all the labels I need and they all worked.
I might take CDR up on his offer
The problem I am having with your solution is you are using AutoIT to pass information to the modified RRSDK.exe and AutoIT again to get the information back.
Originally Posted by CdRsKuLL
This works well for labels that don’t change very quickly but I am working with info from the GPS which is changing all the time. So the AutoIT script sending the CPU sky high.
I think what CDR is proposing is just one .exe that AutoIT can run and the returned results can be put into an AutoIT variable.
Thanks for the work much appreciated
I am glad that the application kind of works.
Remember that what you asked for was a way of retrieving RR label info from RR and getting the returned result into AutoIt. That is exactly what I did for you.
Now you have high CPU usage from within AutoIt. That is a seperate issue and perhaps more to do with AutoIt or your scripts. Perhaps you could either post your scripts or email me them?
If you want to do all of your processing from within AutoIt then there will obviously be a certain overhead as with any scripting language, especially if your script is running and looping constantly. Have you put any code in your script that frees up the processor and/or slows down the GPS label polling interval? If you do not know, something like Sleep(1000) will pause your script for one second.
I may be wrong but from what I have understood about AutoIt you would still need some form of loop that polls any application that retrieves the GPS label information. Logic dictates that it is that loop, and the processing that you are doing with the information, that will always give you some form of performance hit. This is especially true if you are doing it frequently without relinquishing the processor.
Anyway, the point that I am trying to make is that perhaps your script can be tweaked. Other than that, perhaps you should consider putting all of the code that processes the GPS labels into the application that polls RR (currently my RR SDK). That way, you could simply start the application running and let it interface with RR with no need for AutoIt. In order for me to do this I would need to know what processing you are doing on the GPS data and which label/labels to update after that processing.
The ball is in your court. If you want me to look into this further then either post your AutoIt scripts or email them to me.
Thanks cool dude, I will continue to use you app for the labels that I only get when required, so for that I am grateful too you.
As far as processing the real-time GPS stuff I think you are right, I will have a bit of a think over the next few days and get my head clear on exactly what I am trying to do.
You know what it is like you hit a wall and then you find a solution to help you over but your mind goes crazy with all sorts of other possibilities nothing related to your initial problem
cool dude or ashgrovered, I need this app (RRSDK.exe), too. Would you mind sending it to me? Or if it's small enough, you can just post it here as an attachment.
Please find attached a zip file containing the executable. It's only 24K unzipped and 4.8K zipped! As stated before, you will need the VB6 Runtime files (or VB6) installed for it to run.
Had I have realised previously that I could have attached the file then I would have. Silly me!
I welcome your feedback.
$MyLabel = (call this magical exe)RRPATH
Originally Posted by ashgrovered
which exe is that?
Can you send me the entire code?
Ofcourse it's not impossible.
It does work now. Thanks, cool dude.
I'm glad that it's working for you. What is it you are using it for? Anything interesting?
I made it invisible because it really does not need a visual aspect to work the way that it was initially requested. I can make the window visible if anybody wants it that way. Perhaps the best way to do this is to simply allow a command line parameter switch that will turn on the windows visibility.
I do question the need to do this, although it may be usuefull for debugging the RR SDK command. That way, it would be possible to try various RR SDK commands and see what they return (if anything). When running and using RR outside of a test environment then obviously the application is better off being invisible.
redbullah, if you want the code then simply look at the sample code from RR that ashgrovered linked to. I have used the same code but I have simply stripped out the unecessary bits and added a text box to show any returned values from each RR SDK command that you send. If I make a visible command line switch then you will see this.
New Visual Version
OK, here is a a version that can show the form/window through using a command line pramater. The command line switch is "visible". If you run "RR SDK.exe" with this comand line parameter then the application will be visible. Without it the default behaviour is that the form/window is invisible.
e.g. "C:\RR\RR SDK.exe" visible
Whether visible or invisible, you will be able to see the application running in the Windows Task Manager. If it is visible then you can close it by clicking the close button. If invisible then you can close it with your script or end the process in the Windows Task Manager.