gwinter

https://www.autoitscript.com/autoit3/docs/functions/FileSelectFolder.htm

@Chimp Do you have a copy of the binary-to-au3 kompressor by wakillon? All links are long dead. I've searched everywhere. Thanks in advance.

wakillon: Do you have a copy of the BinaryToAu3Kompressor? I can't find it anywhere.

Could anyone post a link to the "BinaryToAu3Kompressor"? I can't find it anywhere on the internet, and most of the links to anything on this site are dead years ago.

Just send an Enter after to submit the search, since you are sending text to the field anyways, you just hit Enter after {ENTER}. An alternative to trying to access controls and buttons on a webpage is to generate Google search links instead of using a search page.

<snip> When your app is ready, please do post the source, but at the moment the post was nothing more than a plug for your site - and so has been removed. M23

Just something I made to auto-collect Gil from FFCC and to test out a new templating system for AutoIt. The templating system is a work in progress, but it is meant to be a companion to AutoIT, which automates creation of GUI, buttons, scripts, templates, etc. It also has built-in chat and group-collaboration, an asset management system and online library for resources. -snip-

Just for to clarify for anyone: The default AutoIt function SoundPlay() is made to only play one sound at a time. When playing a new sound it automatically stops the current sound. Bypassing the SoundPlay function and accessing Sound.au3 yourself is okay, and @Melba23's script will work, however the first sound played has to have the flag set as 0 and the 2nd sound as 1, otherwise it playes the first sound and waits until the sound is finished playing, and never plays the 2nd sound. The script (or EXE) has to keep running, or the sound will stop playing. For example, if you attempt to play a sound without waiting for it to finish playing (either by SoundPlay() or _SoundPlay) and you don't make a While loop or Sleep (or some other way to keep the script from ending), then AutoIt will play the sound but end the program before it is played. So making the first sound play without waiting (flag=0) then playing the second sound waiting for it to finish (flag=1) will work, because it plays the first sound is played, then the second sound is played, then the program waits until that sound is finished before exiting the script. *There is a problem with that method though, it will only work in that order and your script will be "stuck" until that sound is finished playing. The Exit option can not even be acessed from the system tray and the script can't be exited until that sound finishes playing. @Au3Builder's answer was better in my opinion, it works well, but there can be downsides to running multiple scripts, such as focus issues. I am currently working on a related system for AutoIt, an AutoIt framework that uses a "controller-script" that operates independently of the main script(s). One of the reasons for that is to bypass some of AutoIt's limitations without having to add more UDF's, DLL's or includes to a script. Having a script that operates independently of the main scripts can be beneficial in other ways too in AutoIt, such as for "scene-management" or controlling the main application's flow. That "controller-script" is part of a larger AutoIt project I am working on to add to AutoIt's functionality, and to help Auto-It function more like a modern-day game-engine. I am researching and testing different methods of supplying audio in AutoIt, such as rewriting the core Audio.au3, using FMOD or BASS, or like @Au3Builder mentioned, using a "controller-script" to handle sound management. The final application will also include automatic script generation, "prefabs", resource-management, GUI templates, 3D templates, etc. The AutoIt-Assistant Project (final name still to be determined) will be released here and on my temporary site: http://honorsoft.tripod.com/

To Zedna, the link you posted about GUI image flickering is not related to this problem. As I said in my post it was a problem due to GUI Layers in AutoIt. The problem is fixed by putting GUICtrlSetState(-1, $GUI_DISABLE) right after creating the background made the buttons show up properly.

It's 2020, and although this is an old post, this was the only post that matched my exact problem. Although the information here is helpful to determine the problem, no solution is given. I researched and found out already that the problem is related to the rendering of GUI layers in Autoit, and I have been trying different solutions so fat without success. I am using Autoit with GDI+, and my intention is to have a GUI with background. I have been trying different GUI methods in Autoit, but there isn't a lot of information online about Autoit GUI layers or having textured buttons WITH a textured background. With ome of the GUI methods I tried, the buttons wouldn't even show up. Now, using GDI+, I have textured buttons and background, and even button hover and highlighting, but the buttons don't initially appear until you move the cursor over them. Here's what I have so far: When the window first opens... and then when the cursor passes over.. . Some online sources say it's a problem with the drawing order in AutoIt, some say that you have to show and hide the GUI controls in a certain order (including the background), and some say to use $WS_EX_LAYERED or $GUI_FOCUS to fix the problem, but so far nothing works. I do have working Autoit projects that have textured GUI's, so I just have to look in the code to see how they did it. So far, the best working example I found was from: https://www.autoitscript.com/forum/topic/166535-skin-udf/ EDIT: I was going to put an image of the buttons on the background so that they are shown, but that would require me to set up every background first. However, I figured out the problem while writing this post. SOLLUTION: Putting GUICtrlSetState(-1, $GUI_DISABLE) right after creating the background made the buttons show up properly. You would think that diasabling the background would hide it but in this case it doesn't. Create the background image control, then disable it. Here's my GUI menu code using GDI+, it doesn't have the code for button highlighting yet or the resource images, but it may help someone: ;GUI_Menu1.au3 #include <ButtonConstants.au3> #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <MsgBoxConstants.au3> #include <GDIPlus.au3> #include "NoFocusLines.au3" $fGlobal = True ; this will switch off all spots and lines for all controls ;pre-declared ;Global Const $IMAGE_BITMAP = 0 ;Global Const $STM_SETIMAGE = 0x0172 ;replacements Global $img_bmp = 0 Global $stm_setimg = 0x0172 Global $msg MainMenu() Func MainMenu() Global Const $mainWin = GUICreate("FFCC - Accumulator", 960, 565, -1, -1, $WS_EX_LAYERED) ; $WS_SIZEBOX + $WS_SYSMENU GUISetBkColor(0xE0FFFF) Global Const $idPic = GUICtrlCreatePic("Bkg1.jpg", 0, 0, 960, 544) GUICtrlSetState($idPic, $GUI_DISABLE) Global Const $Button1 = GUICtrlCreateButton("GILButton", 209, 93, 95, 63, $BS_ICON) GUICtrlSetImage($Button1, "button_GIL3.ico") Global Const $Button2 = GUICtrlCreateButton("SPButtonDis", 214, 193, 90, 63, $BS_ICON) GUICtrlSetImage($Button2, "button_SPdisabled.ico") GUISetState(@SW_SHOW, $mainWin) ; Loop until the user exits. While 1 $msg = GUIGetMsg() Switch $msg Case $GUI_EVENT_CLOSE ExitLoop Case $Button1 MsgBox(0,"DEBUG","GIL") Case $Button2 MsgBox(0,"DEBUG","SP") EndSwitch WEnd GUIDelete() EndFunc ;==>Example *Note: I will be releasing an assistant application for AutoIt soon that will help it function more like a modern-day game engine. It will include a GUI templating system that will set up GUI menus more efficiently.It will also include project templates, 3D rendering (currently using OpenGL and also Irrlicht), resource management, video support for MP4's, etc. Basically, it will be like the Unity Hub is for the Unity engine, and it will also help AutoIt to function as a game engine for PC and a project-manager for AutoIt, that incorporates commonly used resources, scripts, API's, etc. It also tracks AutoIt projects and keeps track of what resources and scripts are included in the "project". I have seen AutoIt do some amazing things, like run OpenGL at full speed, use the Irrlicht engine, function as an videogame-emulator, loading 3D models, particles and lots more. I am also working on a similar project for Godot, but I will try to finish the AutoIt Assistant project first and release it here and on my temporary site: http://honorsoft.tripod.com/honorsoft-hom

You can keep building to it, give it a context menu, add it into the Windows registry, it can make custom links to whatever and send those 'shortcuts' to anywhere (even send them online via GMail or upload-script). Just recently, I added Window's ClipBoard monitoring to MySysCONT, so it can divert email SENDTOs, quickly and silently collect a list of url's I copy, and even opening Google Chrome(while keeping it hidden) so I can access the Hangouts Extension when a phone number is copied to the clipboard. The Hangouts extension lets you make a call, but can't be opened unless Chrome is opened first, so until I can find a better way, I use AutoIt to bypass. It can mute/adjust audio before calling, etc. You are only limited by your imagination...

You can keep building to it, give it a context menu, add it into the Windows registry, it can make custom links to whatever and send those 'shortcuts' to anywhere (even send them online via GMail or upload-script).

For JonnyHotchkiss and Lilinote, and any others customizing/improving their 'Windows Experience', I came on this web page to find out more about *.lnks, and refresh my memory about how windows uses them. What I wanted to say though was don't forget that you can make your own file-type. It will function exactly how you want and be totally accessible and changeable to you. It can be as simple as a *.txt file with a new made-up extension (like MyLink.luk). I have found that it is better (and sometimes easier) to set up your own control-systems in Windows, keep Windows out of it and you won't tie up Windows by distracting it. For example, I have written Windows-Interface software that runs applications and performs Windows-related functions way faster than explorer, by average, what it takes Windows five seconds to do, my software does in 1 second. For LiliNote, it seems Windows set it up 'one link per LNK', so unless you want to start rewriting system files, you could do what I've done before, make a file that has a list of files to open, you could even include other info AU3 could read, like pictures to go along with media files or documents. I got sick of Windows taking up so much space/time with indexing, file-linking and all the other 'managerial' stuff Windows does. A lot of the times Windows seems to fail/lag at all that anyways. I ended up writing an AU3 'system manager' that would run at start-up, keep a data-base of only the files I would use (not like Windows keeping track of everything numerous times), allowing me to associate my own album art to any media file, perform custom tasks before running a specific app, open certain LNK's or URL's in custom-layout windows, etc. Anyways, back to the 'opening 2 files at once' thing, what you could do is make a file type that contains different headings using an unreserved and unused character, and even add different commands like this: ThemeLinks.luk (a new link file type *.luk) ~FilesToOpen C:\Windows\Desktop\Theme.jpg C:\Users\AppData\ThemePage.url ~FilesToDelete C:\Windows\Desktop\Theme2.jpg The above is an example of a new custom 'LNK', maybe named ThemeLinks.luk, and it is set to "Open With..." MySystemCONT.exe (which is an auto-it exe) which uses "$PassedLUK = $CmdLine[1]" to store the name(and path) of the shortcut passed (in this example '$PassedLUK = "C:\Windows\Desktop\ThemeLinks.luk". MySystemCONT does not even need to sit in the background, whenever a *.luk is opened, Explorer sends the LUK to MySystemCONT.exe, which reads it (looking for the "~" symbol) and performs whatever is listed. I added a ~FilesToDelete for example to also delete a file(if it exists) every time the LUK is opened. You could make any format or process the links however you want. I had a link that would open up all my necessary folders, software and text files for game-programming, even waiting before opening some links. Just an idea to you guys and others, to think outside of the box, or the Window.