Followers 0

## 10 posts in this topic

#1 ·  Posted (edited)

I don't know why there are many external files that are not existed on the pre-written functions of AutoIt software..

The examples in this page are telling to include "MsgBoxConstants.au3" but I doesn't have one:

http://www.autoitscript.com/autoit3/docs/functions/GUIGetMsg.htm

Edited by Servant

##### Share on other sites

Servant,

That file, along with a whole raft of other ###Constants files, was introduced with the new 3.3.10.# release - the idea was to reduce the size of the individual #include files by splitting the previous larger ones. So download and install the latest release (and perhaps the latest Beta) and these files will be available to you.

M23

1 person likes this

Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind._______My UDFs:

Spoiler

ArrayMultiColSort ---- Sort arrays on multiple columns
ChooseFileFolder ---- Single and multiple selections from specified path treeview listing
Date_Time_Convert -- Easily convert date/time formats, including the language used
ExtMsgBox --------- A highly customisable replacement for MsgBox
GUIExtender -------- Extend and retract multiple sections within a GUI
GUIFrame ---------- Subdivide GUIs into many adjustable frames
GUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView items
GUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeView
Marquee ----------- Scrolling tickertape GUIs
NoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxes
Notify ------------- Small notifications on the edge of the display
Scrollbars ----------Automatically sized scrollbars with a single command
StringSize ---------- Automatically size controls to fit text
Toast -------------- Small GUIs which pop out of the notification area

##### Share on other sites

Servant,

That file, along with a whole raft of other ###Constants files, was introduced with the new 3.3.10.# release - the idea was to reduce the size of the individual #include files by splitting the previous larger ones. So download and install the latest release (and perhaps the latest Beta) and these files will be available to you.

M23

Is there a way to update my AutoIt software?

If you don't know what version of AutoIt you have, then use this >>

MsgBox(4096, '', @AutoItVersion) ; 4096 = $MB_SYSTEMMODAL My version is 3.3.8.1 and as far as I know, I'd just reinstall my AutoIt a few months ago.. #### Share this post ##### Link to post ##### Share on other sites #### Share this post ##### Link to post ##### Share on other sites My AutoIt has been updated! #### Share this post ##### Link to post ##### Share on other sites #### Share this post ##### Link to post ##### Share on other sites Just want to remind you to check the history and script breaking changes before continuing forth. Second that! #### Share this post ##### Link to post ##### Share on other sites Here a small script to show installed and available AutoIt versions: ; AutoitVersion.au3 #include <Inet.au3> #include <string.au3>$pfile = StringTrimLeft(StringTrimRight(RegRead("HKEY_CLASSES_ROOT\AutoIt3Script\Shell\Run\Command", ""), 9), 1)
$bfile = _StringInsert($pfile, "\\beta", -12)
$pver = FileGetVersion($pfile)
$bver = FileGetVersion($bfile)
If @error Then $bver = "none"$a = _StringBetween(_INetGetSource("http://www.autoitscript.com/site/autoit/downloads/"), "Latest version:</strong> v", "<")
$lpver =$a[0]
$a = _StringBetween(_INetGetSource("http://www.autoitscript.com/autoit3/files/beta/autoit"), "autoit-v", "-beta-setup.exe") If @error Then$lbver = "none"
Else
$lbver =$a[UBound($a) - 1] EndIf ;~$lpver = "3.3.10.3"  ; for testing
;~ $lbver = "3.3.11.3" ; for testing$text = "AutoIt Versions" & @LF & @LF & "Installed" & @LF & "Prod: " & $pver & @LF & "Beta: " &$bver & @LF & @LF
$MsgMod = 0 If ($pver = $lpver) And ($bver = $lbver) Then$text &= "No newer versions available."
Else
$MsgMod = 48$text &= "Newer version to download" & @LF
If Not ($pver =$lpver) Then $text &= "Prod: " &$lpver & @LF
If Not ($bver =$lbver) Then $text &= "Beta: " &$lbver & @LF
EndIf

MsgBox($MsgMod + 4096, @ScriptName,$text)

My UDFs, Abbrevs and Snippets
If you like my post, just click the like button

##### Share on other sites

#10 ·  Posted (edited)

There is an online ini file if I remember correctly, where beta and stable versions are stored.

Er...I guess you used 4096 because I did, but I only used it because I knew the OP didn't have MsgBoxConstants.au3, so $MB_SYSTEMMODAL wouldn't have been found. Edited by guinness #### Share this post ##### Link to post ##### Share on other sites ## Create an account or sign in to comment You need to be a member in order to leave a comment ## Create an account Sign up for a new account in our community. It's easy! Register a new account ## Sign in Already have an account? Sign in here. Sign In Now Followers 0 • ### Similar Content • By rudi Hello. I'm too stupid to see my mistake: To investigate the internal "dictionary" of TIFF files I'd like to read in the files in binary mode and to check, if there are more than one pages "in" this TIFF. Notepad++, "View as Hex" is presenting the first bytes as "49 49 2a 20 08 20 20 20 12" for the TIF attached to this posting The "TIFF Header Format" is easy: Offset 00h, 2 Byte = Byte Order, "II"=intel, "MM"=motorola. (I = 0x49) --> II Offset 02h, 2 Byte = Version Nr. Offset 04h, 4 Byte = pointer to first IFD entry Description of TIFF header: https://www.awaresystems.be/imaging/tiff/faq.html#q3 Howto read and analyse the binary content correctly? This is my messy, not operational code:$sampleTiff="H:\daten\tif\11\11\111111.TIF" $h=FileOpen($sampleTiff,16) $content=FileRead($h) ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $content = ' &$content & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console FileClose($h)$type=VarGetType($content) ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') :$type = ' & $type & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console$ToString=BinaryToString($content) ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') :$ToString = ' & $ToString & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console ConsoleWrite(@CRLF & @CRLF)$content=StringTrimLeft($content,2) ; cut off the leading "0x" ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') :$content = ' & $content & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console for$i = 1 to 8 step 8 $next=StringMid($content,$i,2) ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') :$next = ' & $next & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console$Chr=BinaryToString($next) ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') :$Chr = ' & $Chr & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console ConsoleWrite(@CRLF & "---" & @CRLF) Next Regards, Rudi. 111111.TIF • By Skeletor MS Splash Screens The office 2016/17 office suite has made many people turn heads with its functions and especially their splash screen. I now present to you, the MS Style Splash Screen. For Rookies, Novices and anyone who wants a ready made splash screen for your gui application. You can now download it and also try it out yourself. You have three colors to choose from: Blue Red Green All three colours are from the famous programs. I also included the KODA form to you can have freedom with this splash screen. Note: the KODA form does not have the three colours as well as the correct blue. Have fun and enjoy. Note: I will update the splash to add the automated 3 dots animation at a later stage. • By Skeletor A gui splash screen. Themed after the famous MS Office Suite. Three colours to choose from, Red, Blue and Green. You can change the labels to your own application. Also bundled with this is the KODA form. So you can open up and see the basic structure of this splash screen. Splash Screen GUI.zip • By BlazerV60 Hello all, I've been trying to figure out how to launch Google Chrome in the background (hidden) but it doesn't seem possible. I've tried the following methods: ShellExecute("C:\Program Files (x86)\Google\Chrome\Application\chrome.exe", "", "", "", @SW_HIDE) Also I've tried: ShellExecute(@ComSpec, "/c start chrome.exe","","",@SW_HIDE) Lastly I tried: RunWait('"'&@ProgramFilesDir&'\Google\Chrome\Application\chrome.exe" --silent-launch',@ScriptDir) But all of them launch my chrome browser without hiding it. Does anyone know a workaround for this or if AutoIT just can't Chrome? Bonus points if you know how to make it launch chrome hidden and make it go to https://www.autoitscript.com Thank you, Brian • By SteveJM I have a working program currently driven largely through menu selections. I would like to add a toolbar where most of the tollbar button actions are basically the same as menu items, but quicker to access. I have been wading around in toolbar examples, MSDN pages etc, it's clearly going to be a bit of a slog to get everything right, including tooltips etc. I thought I would start with something simple to prove the principle. Using bits from the help file examples I have a small program that successfully displays a toolbar. However, what seemed like the most elegant way to deal with the button commands does not seem to work. My understanding was that a toolbar button fires a WM_COMMAND message, with the command Id set by the second parameter in the call to _GUICtrlToolbar_AddButton ($hWnd, $iID,$iImage)
so I though it would be a good idea to set this Id to the same value as my menu item Id; then it would run the same task which is what I wanted. This did not work. I am using message loop mode and would like to stick with this because some of my scripts run hardware at the same time as the gui; it is easier if I don't have to worry about code being interrupted with the hardware in an unknown state . So I added a handler for WM_COMMAND, with some cribbed display code to try and see why. The toolbar button defintely fired a WM_COMMAND message and the Id looked the same, so no explanation there.
I guess the issue is with GUIGetMsg() which may be constructed to ignore all but a limited number of control handles, i.e. those made with the GuiCtrlCreate... commands; this is speculation.
I would dearly love to find a tidy way to get around this. Having some controls handled in the message loop and some in a WM_COMMAND handler, performing the same task, feels ugly. I would be very grateful for further insight from someone experienced with handling a toolbar. Perhaps I should be trying to fire the menu item. I have attached a code snippet to try and illustrate the issue.

ToolbarTrial.au3