Leaderboard

I am trying to serialize all the autoit variable by >msgpack, so that I can used it in ZeroRPC (language-agnostic remote procedure call over internet). Int, string, binary are easy, but DllStruct is not. Before variable serialization become build-in function (I hope so), I have to find out my own way. Here is my attempt to guess the setup string. I am not sure did I deal with all the align and struct/endstruct correctly, please let me know if there is any bug. The output may not be the same with the original string, it is not bug. Test() Func Test() Local $Struct $Struct = DllStructCreate("align 2;byte;ptr[2]") ConsoleWrite(DLLStructAnalyze($Struct) & @LF) ; Output: byte;align 2;ptr[2] $Struct = DllStructCreate("int;struct;struct;uint64;uint;byte[5];endstruct;byte;endstruct;byte") ConsoleWrite(DLLStructAnalyze($Struct) & @LF) ; Output: int;struct;struct;uint64;uint;byte[5];endstruct;byte;endstruct;byte $Struct = DllStructCreate("int;uint64;struct;struct;uint;byte[5];endstruct;byte;endstruct;byte") ConsoleWrite(DLLStructAnalyze($Struct) & @LF) ; Output: int;uint64;struct;struct;uint;byte[5];endstruct;byte;endstruct;byte EndFunc

You cannot deal with such a runtime error and continue script, you have to code in such a way as to avoid such errors.

$filelist[0] will show the number of elements, that can be used to stop at a certain number. Also, the second call to _FileReadToArray has no variable storing it.

If $word[7] = "PRINTER***No" Then $printercount += 1 If $word[7] = "PRINTER***Paper" Then $printercount += 1 If UBound($word) > 8 If $word[8] = "3DBUILDDATE" Then $dbdate = $word[7] If $word[8] = "COUPONS" And $word[8] = "TRIGGERED" And $word[7] = "0000" Then $zerocoupcount += 1 EndIf

In your case _Excel_RangeRead returns a 2D array (because B12:V13 returns 2 rows and multiple columns). Hence you need to use MsgBox(0,"",$Output[0][0])

btw. This project is a great example and also test for the "map" beta feature. By analyzing your code, I learned a lot. Thanks for that. mLipok

How are you determining it's clicking twice? Are you in a loop with that code? Do you have it more than once in your code? To be honest, that code wouldn't run at all with the way you have it. Anyway... I suspect it's one of the conditions above I've described that is your real issue, but you can try: MouseMove(parameters here) MouseDown(parameters here) MouseUp(parameters here) Edit: The 4th parameter, as stated in the help file, is the number of clicks, you have 10 in that position. Just put 1 if you're not using the 5th parameter which is speed.

Nothing springs immediately to mind as to what might be wrong, looks fine except for I'd remove the sleep function. Leave the Local $aPos = MouseGetPos() where it is and add $aPos = MouseGetPos() in loop. Use WinMove to update its position, but only after a check to see if it has actually moved to avoid flicker.

From a little searching this is how I understand it works when recording layered windows Win 7 DWM off, capture program must use CAPTUREBLT flag with BitBlt (ScreenToGif does not seem to use this, look here) DWM on, layered windows always included (?) Based on this I assume you have DWM (Aero) disabled. It works for me and the other dev because Win 8 always have DWM on (can't be disabled). So you need to either enable DWM (enable the Aero theme) or use a recorder that specifically supports layered windows... I use OBS for game/screen recording and it does have a [Capture Layered Windows] setting which I imagine is exactly for this. But it records to mp4 not gif.

@OP Hi and Welcome to the forum! I don't know what would be easiest, getting one language to run in the others SciTE, or run both, but why can you not run both simultaneously? You might need to set check.if.already.open=0 in the user settings file, did you try that? (In SciTE, Options > Open User Options File). @Michiel There is a 64 bit SciTE?

Example: #include <GUIConstantsEx.au3> $hGUI = GUICreate("Coord Mode Test", 300, 200) GUISetCoord(10, 10) ;sets X, Y coordinates GUICtrlCreateLabel("Label", -1, -1, 100, 16) GUICtrlCreateButton("Test", -1 + 20, -1 + 30, 75, 23) GUICtrlCreateInput("Test", -1 + 40, -1 + 60, 100, 23) GUISetState(@SW_SHOW) While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit EndSwitch WEnd

I was referring to 12 KB of (compiled) C++ code. Right you are. What annoyed me most about your idea is it's really coming off as you wanting something for nothing. You really said the wrong things with your narrow focus of only wanting functionality to suit yourself. Most people who want to do something will try to learn to do it. And it's my personal agenda that AutoIt doesn't require an idiot to use it, either. I constantly harp on the other developer's not to over-simplify things so that advanced functionality can't be achieved. Until Holger's little creation here, I was very hard on JP for over-simplifying the GUI design. Quite literally, I would of rather programmed a GUI in C++ and wrote 200% more code than use AutoIt simply because AutoIt couldn't do the things I wanted. So there is a middle ground that has to be struck in the debate between "simple" and "advanced". I've never claimed to be the "code defender" or "person-in-charge" nor the "solo spokesperson". It's people like you who go off on insolent rants that give me these titles. Oh, and by the way. I had a hand in Holger's idea. Holger was stuck and couldn't finish the idea until I came up with a solution and adapted it to suit both Holger and my own needs. So yeah, I kind of did introduce the functionality since the magic that makes it call user functions is my code. I'm not trying to diminish Holger's efforts, most of the code is his and he is the one who put all the work into testing it and documenting it. However, don't assume that because only one developer is listed for a feature that they are the only one who contributed code that makes it work. Another title which I have not given myself. Would you like it if I told you to draw me a picture of my house but I limited you to only using circles? Unless I'm a Hobbit or a baby chicken, chances are, you're not going to be able to do what I ask with any semblance of accuracy. Your request follows a similar path of unreasonable and unrealistic thinking. Okay, so pretend we implement all your ideas for how to draw menu's with a very simple API. What if I don't like the way the menu's look when they are drawn this way? Will you consent to having my similar but different API included? What about when the next person comes along, and the person after that, and the person after that? And we're just talking menu's here. There are over a dozen controls in AutoIt and most of them support owner-drawing. Do you see where I'm going with this? Does this make sense to be in the core language? When you make any feature request, you make it to anybody who has access to the source, especially those of us with updated copies of the source. Should I be encouraging people to use AutoIt? Shouldn't the strengths of the language be encouragement enough? Edit: Forgot a paragraph so I added that.