
OregonJohn
Members-
Posts
17 -
Joined
-
Last visited
OregonJohn's Achievements

Seeker (1/7)
0
Reputation
-
"Multi RDP connections" That's what I do. I have three different XP machines running AutoIt3 scripts interacting with the front end of the same program. I have a third XP machine (oldie) that runs a RDP of all three machines running scripts ... I call it my RDP monitor machine. As an aside, I have one of those XP machines providing two RDP sessions for the RDP monitor because I want two active scripts running on two separate programs. I wish XP provided the ability to run separate desktop instances on the same machine. I tried using virtual desktops (like Dexpot) but the windows the script was watching for kept coming to the main desktop and interrupted the activity on the main desktop.
-
ctrl break stopping my compiled script
OregonJohn replied to OregonJohn's topic in AutoIt General Help and Support
Thanks to both of you, BogQ and Rover. Opt("GUICloseOnESC", 0) worked, funny how it worked on Break as well as ESC. I didn't try the other, went for simple. thanks again. John. -
By accident I discovered that ctrl-break not only stops a script being written and tested with tools/go, but even the compiled script is affected. I tried this on a variety of script and always got the same results. ctrl-break is used so seldom by normal users that it is probably not a big deal, but it is a nuisance. I would like to stop ctrl-break from acting on my compiled scripts. I tried the following from the help file "GuiCreate" example and ctrl-break stops the compiled version: #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> Example1() ; example 1 Func Example1() Local $msg GUICreate("My GUI") ; will create a dialog box that when displayed is centered GUISetState(@SW_SHOW) ; will display an empty dialog box ; Run the GUI until the dialog is closed While 1 $msg = GUIGetMsg() If $msg = $GUI_EVENT_CLOSE Then ExitLoop WEnd GUIDelete() EndFunc ;==>Example1 I tried Break(0) ;Disable break But that didn't seem to work. Anyone have an idea on how to stop ctrl-break from stopping my compiled script?
-
Thanks for the response Spiff59. I reduced my script down to the most basic component, one piece at a time, until I got to this: #AutoIt3Wrapper_Outfile=StudyAid.exe $GUIMain = GUICreate("StudyAid", 135, 100) GUISetState(@SW_SHOW) MsgBox(0, "", "Exit") Exit And when compiled it still showed that extra window. Then I uninstalled and reinstalled both the latest AutoIt3 and Scite, and renamed the folder remaining after uninstall, on the off chance it's something sitting a folder somewhere.. I still get that extra window when I compiled the most basic version shown above. Note: I did stop a build process (using XP Task Manager) that was taking a very long time to complete sometime prior to this extra window appearing. My best guess at this point is that ending those processes left some residue somewhere. Not the brightest thing to do, now I see in retrospect, but it was taking 10 minutes and I'd never seen any of my scripts take that long to build (using tidy and obfuscator). Oh, and just so we know, the compiled StudyAid works just find on any other computer I run it on.
-
Using a DONGLE to protect my software..?!
OregonJohn replied to SYRAU3's topic in AutoIt General Help and Support
I'm using LimeLM, a relatively new service for licensing. They are helpful in getting their coding into your script. Otherwise, i agree with all the others that there is no ultimate way to protect the software itself. Locks on doors only protect against non-professional thieves. -
I've been working on a timer gui for about four months now. I'm actually finished with it and have a fix for the issue I'm going to bring up, but I'd like to know if anyone else has happened across this. I've been naming my application "ReadAid.exe" for the past many months. All the builds went just fine and produced GUIs that I've come to expect. Just recently, if the final name is compiled as, or is renamed as, "ReadAid.exe" (the name I've used for the past many months) I get this strange extra window when I run the executable and the first GUI starts. If I run "StudyAid.au3" with any name it runs just fine. If I rename the executable anything but "ReadAid" then the first GUI starts just fine, otherwise I get this weird extra window. Here's the extra window, as you can see the icon for my app shows up. There is no other content in the window. I included the folder so you could get an idea of size. If I close the extra window it closes the whole app. I deleted all of the executables and shortcuts in my computer that have the name "StudyAid.exe". I copied the text of the script and pasted it into a new Scite file. I think the problem might be in some residual code left somewhere, or maybe something left over in the compile program. The script itself is really long, and not terribly pretty, and not really relevant (as far as I can see) to the problem. No big deal if no one knows what it is, because I decided to rename my application ReadAid2.exe which completely solves the problem.
-
Thanks HeidiR, I needed to not use IE.au3 because it wouldn't get past the obfuscator. Then I saw your post and saw I didn't even need it. Mostly, I just want to have some nice html displayed instead of extended labels to explain how to do something. So I wrote an html file that goes along with the script. It could be a local file or a web page, but here's how I made it work for me: #include $HTML = "http://google.com" GUICreate("Test html", 400, 410) ;Create frame for html to show Local $oIE = ObjCreate("Shell.Explorer.2") GUICtrlCreateObj($oIE, 10, 10, 380, 280) $oIE.navigate($HTML) ;End create frame for html to show GUISetState(@SW_SHOW) While 1 $msg = GUIGetMsg() If $msg = $GUI_EVENT_CLOSE Then ExitLoop WEnd GUIDelete()
-
GUICtrlCreateListView & DriveMapAdd Help
OregonJohn replied to surreal's topic in AutoIt General Help and Support
I know this is an old thread, but surreal's questions and sample code helped me. I was working on a script to list the folders in XP's Application Data directory, select them and then eventually copy and transfer them to Win7. Here's a snip of my solution, I don't use all of it in my final code but I sampled some possibilities. If $msg = $btnAppData Then Local $item_count = _GUICtrlListView_GetItemCount($lstvAppData) Local $is_checked For $i = 0 To $item_count - 1 If _GUICtrlListView_GetItemChecked($lstvAppData, $i) = True Then If $is_checked = "" Then $is_checked = _GUICtrlListView_GetItemText($lstvAppData, $i) Else $is_checked = $is_checked & @CRLF & _GUICtrlListView_GetItemText($lstvAppData, $i) EndIf EndIf Next If MsgBox(1,"","You have selected:" & @CRLF & @CRLF & $is_checked) = 2 Then Exit $is_checked = StringSplit($is_checked,@CRLF) _ArrayDisplay($is_checked) EndIf -
ScriptKitty's version worked best for me, but I was getting weird results if the new minutes were :00. A look at the returned array showed me that my $NewTime and $OldTime were coming from the script with the date included, so the hour ($old[1]) included the date and messed up the calculations. I solved the problem by using StringRight on the $old[1]. I replaced: $Oseconds=$old[3]+($old[2]*60)+($old[1]*3600) $Nseconds=$new[3]+($new[2]*60)+($new[1]*3600) with StringRight($xxx[1],2) to eliminate the hours --- now the script works everytime $Oseconds=$old[3]+($old[2]*60)+(StringRight($old[1],2)*3600) $Nseconds=$new[3]+($new[2]*60)+(StringRight($old[1],2)*3600) I love AutoIt3!
-
Win 7 "Help" in Scite not working
OregonJohn replied to OregonJohn's topic in AutoIt General Help and Support
It solved itself. After having opened Help manually, and doing a few searches by hand, I just tried F1 one last time and Help opened in the way we all expect. Strange but true. Hope this helps someone. John in Oregon -
I love being able to highlight a term and hit F1 to get help on the term. In Windows 7 it just doesn't happen. I installed AutoIt and extended Scite on two different Win 7 machines and neither one will bring up help either from the menu or from F1. I only found "scite problem with help on windows 7 64 bit" in the forums. The answer for that (in Option/Open au3.properties i modify line #7) didn't apply to me. The Win 7 64 bit install already had that directory, and the Win 7 32 bit install had the correct directory. Anyone have any other ideas of how to fix that? John in Oregon
-
I found what I needed with _GetDiskNimberForDrive Forum thread Post #9
-
I tried it. No go. I inserted the following into your script: _ChangeDriveLetter("W", "T") MsgBox(0,"","error is number " & @error) I got error 5 -- Unable to delete mount point. Drive W can be changed to T in Computer Management, so there's no apparent block. I have XP Pro SP3 So sad, because I could have really used it. I can use DiskPart to change the drive letter but I don't have the disk number, just name and letter. I can't find any way to convert the name or letter to a disk number.
-
Can anybody help me with convert a function to au3
OregonJohn replied to sunless's topic in AutoIt General Help and Support
I also thank you, though so many years have gone by who knows if you'll ever see it ... hopefully the thought counts! -
How to select the first file in a folder
OregonJohn replied to dunk6's topic in AutoIt General Help and Support
I've struggle with these "find first file" routines myself. I keep at it and now I use it a lot, though I still struggle. The search returns $file You call a function using $file and probably $StartDir While 1 $file = FileFindNextFile($search) If @error Then ExitLoop CopyMyFile() WEnd Func CopyMyFile() FileCopy($StartDir & "\" & $file,"c:\" & $file) The loop will continue passing $file to the function until there are no files left in $StartDir. With more searching you will find that it can be made to search sub-directories as well. Hope that gives you the clues you need...