Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/03/2015 in all areas

  1. There are three ways you can posts scripts, these are: Inline code Attachments Download system Each has different advantages and disadvantages. In general you should use: Inline code - for short code snippets Attachments - for more complicated code larger than a page. Downloads system - for projects or complex libraries Inline Code Best for entering short snippets of code Easiest for other users to see May be accidentally modified by forum upgrades or when re-editing your post - it's happened before... Inline code is entered using the "Add Code" button in the toolbar and after posting appears with syntax highlighting like this: ; This is some AutoIt code MsgBox(4096, "Message", "Hello there!") Code over around 50 lines will appear in a scrollable box. At this point it becomes more difficult for other users to work with and you should consider an attachment instead. Attachments Best for long pieces of code, entire programs, or multiple files Unlikely to be accidentally lost or modified by forum upgrades or when re-editing your post Counts against your global attachment allocation Can be seen in the "username / My Attachments" part of your profile, along with the number of downloads Multiple attachments can be added to a post. As attachments are stored as complete files in the filesystem, they are more robust than inline code snippets. Downloads System Best for very long and complicated projects or libraries that are of significant use to the community Uses a different part of the forum that is optimised for file downloads and features screenshots, change logs, download counts, etc. Does not count against your global attachment allocation This can be accessed here: Downloads System.
    1 point
  2. 5/3/2015: Uploaded a new SciTE4AutoIt3.exe installer with an updated SciTE v3.5.4 release. These are the major changes: - See details below. Enjoy, Jos Addition/Changes/Fixes in the current installer: -------------------------------------------------------------------------------------------------- 5/3/2015 *** Merged the SciTE v 3.5.4 by Neil Hodgson with our own version of SciTE. (Jos) Added utf8.auto.check which will autodetect UTF8 encoded files without BOM and files containing Highvalue ASCII characters and setting the correct encoding. We have set the default to 4 which means that the encoding is set to UTF8 without BOM for any script containing normal ASCII characters. #~ Enhance function of auto checking utf8: providing two methods #~ utf8.auto.check=1: detect utf8 and add BOM automatically #~ utf8.auto.check=2: detect utf8 and do not add BOM #~ utf8.auto.check=3: detect ascii high characters and if none found set default encoding to UTF8 and add BOM utf8.auto.check=4: detect ascii high characters and if none found set default encoding to UTF8 and do not add BOM *** Updated Au3Stripper v15.503.1200.0 (Jos) - 14.801.2025.1: Fix for AdlibUnRegister() without parameter avoid warning and hardcrash. - 14.801.2025.2: Fix handling ".\" relatives paths in #include statements. *** Updated AutoIt3Wrapper v15.503.1200.0 (Jos) - 14.801.2025.1: Fix for #2851 -> au3records returning some SciTE console info that shouldn't be there. - 14.801.2025.2: Added support for UTF8 without BOM scripts to be able to update the version and GUI information. - 14.801.2025.3: Decode %xx% in the OutputFile Directives - 14.801.2025.4: Make single line script with directive work - 14.801.2025.5: Added check for AUT2EXE failure adding FileInstall() files. and set return code to 1. - 14.801.2025.6: Fix error trigered by "#AutoIt3Wrapper_Run_Debug_Mode=Y " when script contains Switch-Case-EndSwitch - 14.801.2025.7: #AutoIt3Wrapper_Res_Fileversion_AutoIncrement=Y will now also increment #pragma compile(Fileversion, 0.62) statements. Also now support for: #AutoIt3Wrapper_Res_Fileversion_AutoIncrement=Y #AutoIt3Wrapper_Res_Fileversion=0.62.0.4 #AutoIt3Wrapper_Res_ProductVersion=%fileversion% - 14.801.2025.8: Added: #AutoIt3Wrapper_Res_HiDpi= ;(Y/N) Compile for high DPI. Default=N (Idea: unexpectedpanda) - 14.801.2025.9: Fixed regression in .7 - 14.801.2025.10: Fixed missing info in the HiDpi data - 14.801.2025.11: Added 2 keywords for AutoIt3Wrapper.ini which can set the Restart and StopExecuting Hotkeys in AutoIt3Wrapper: (mLipok) [Other] SciTE_STOPEXECUTE=^{END} SciTE_RESTART=^!{END} *** Updated Tidy v15.503.1200.0 (Jos) - Fixed regression for #include-once statements - Fixed Spacing for #include statements - Fixed bug with #tidy_On/#Tidy_Off - Fixed hardcrash with longfilenames. - Changed SortFunc option from 15 to 65 characters of the FuncName to sort on. *** Updated SciTEConfig v15.503.1200.0 (Jos) - 14.801.2025.1 Fixed issue with setting CallTip dynamically. - 14.801.2025.2 Added About button. - 14.801.2025.3 Fix UserCallTip Manager big (Melba23) - 14.801.2025.4 added Alpha level for Selected line background and changed the logoic for displaying the Alpha value label. - 14.801.2025.5 Added checks for SciTEUSer info to Option "Run AutoIt3/SciTE Check". showing SciTEUser file location at the bottom. (mLipok) - 14.801.2025.6 Added option to open AutoIt3Wrapper.ini and Tidy.Ini -------------------------------------------------------------------------------------------------- ==> ScitillaHistory page containing all SciTE/Scintilla updates. ==> Visit the SciTE4AutoIt3 Download page for the latest versions ==> Check the newly formatted the online documentation for an overview of all extras you get with this installer.
    1 point
  3. iamtheky

    When an Array isn't full

    I now read back, and you want to play with arrays. However, 7 is not returned in that resulting array so that loop would never result with it. $VariableToBeCut = "1234567" msgbox(0, '' , StringRegExpReplace($VariableToBeCut, ".{3}" , "")) something like this for ubound is what i would imagine $VariableToBeCut = "12345678" $aArray = StringRegExp($VariableToBeCut, ".{2}", 3) msgbox(0, '' , $aArray[ubound($aArray) - 1])
    1 point
  4. Hi, C&P - Failure.... should be $segments[$m] = StringReplace ($segments[$m], @CRLF, " ") $segments[$m] = StringReplace ($segments[$m], @LF, " ") $segments[$m] = StringReplace ($segments[$m], @CR, " ")
    1 point
  5. What exactly isn't working as expected? When I run your script, each button is selected (highlighted in green) as I would expect.
    1 point
  6. water

    $GUI_EVENT_DROP not working

    What do we learn from this thread? CAREFULLY read the help file Almost always the needed information is already there
    1 point
  7. ​After starting I get an error "winmgmt failed." and the combo box seems not to be filled properly: After clicking on CIMv2 button the combo added the CIMv2 WMI Namespace to the end of the combo. With CIMv2 it seems to work but the color of the HTML rows/columns in rotated mode is ugly. Last but not least the Look on WWW generated site seems not working.
    1 point
  8. If $obrazok2 = "" Then ; empty
    1 point
  9. JLogan3o13

    need help OBJ/COM

    By reading https://msdn.microsoft.com/en-us/library/office/ff194068.aspx
    1 point
  10. Melba23

    Forum Upgrade Status

    Because of a forum bug, members have temporarily been prevented from deleting their own posts - so think twice before you hit "Submit Reply". M23
    1 point
  11. Hi all! After long time of silence in this topic I'm put my customized version of original Herons DBUG. Added: - sorting in variables list by any column and drag in any order. - by default 1D and 2D arrays showing in list (1D as [1 2 3 4 5 ... N] 2D as ["row1:column1 value" "row1:column2 value" "row1:column3 value" ... "row1:columnN value"]...[rowN:columnN value ], 3D and more dimensional arrays not showing - extended information toggle button [..] (useful for variables with type arrays, dllstruct or object) Changed: - DBUG window now has a minimal size, you cannot change it vertical and horizontal size to zero. - previously when you edit variable name or insert new one in edit mode when you click with mouse out of edit field name changed on name where you click (sorry for my english), use Enter (or Esc) for complete editing and Ctrl+Z for Undo. Use arrows button for scrolling left or right in edit mode. - clear and execute command buttons now docking around of appropriate edit field - command result window is now disable for input All modifications has a ; valdemar1977 comment at the end of line. How to use DBUG - put Dbug.au3 to Autoit include directory or user include directory (setup user include in SciTe settings - "Tools"->"SciTe Config"->"General 1"->"User Include Folder") - put IMAGES folder in Autoit home (location of AutoIt3.exe file) - add #include <Dbug.au3> in your code (or #include "FULL_PATH_TO_FILE\Dbug.au3" if you put it anywhere) - use ;STOP DBUG for excluding some part of you code from debugging, ;START DBUG will resume debug. Thank you Heron again! Dbug.zip
    1 point
  12. argumentum

    More then 10 Regwrite

    If Not $returnValue Then $ThereWasAnError = 1 MsgBox(64, "TestWare - Error", "There was an error writing to the registry."&@CR&'at $i = '&$i&' where:'&@CR& _ 'RegWrite("'&$myRegpathArray[$i]&'", "'&$myRegValueArray[$i]&'", "'&$myRegtypeArray[$i]&'", "'&$myRegDataArray[$i]&'")' _ ) EndIf ...that way you have a better debug
    1 point
  13. Process + Thread + DLL Functions UDFs Fully tested on O/S's from Windows 2000 -> Windows 7, in both 32-bit and 64-bit modes. *Note: the dropdown box in the GUI has issues in Windows 2000 - workaround - type 1st letter of process. Also, RemoteThreads may not start if Terminal Services is not installed on Win2000. This is a compilation of all my Process, Thread, and DLL functions (and now Driver functions) into a number of UDF modules. Most every and anything useful can be done with these functions. The best part is the GUI interfaces (ProcessFunctionsTest, ThreadFunctionsTest) which let you experiment with what functions do without even touching a line of code. And whats that? Oh yes - it creates Threads. Even 'Wow64' threads, which requires a new way of thinking =) Bundled with the core Process, Thread, and DLL UDF's are numerous support functions, examples, and even a DLL Injection module. A comparison program 'ProcessListPropertiesTest' is also included for comparison against PsaltyDS's _ProcessListProperties UDF). The GUI's pictured above are the best way to explore the possible uses of the Process + Thread functions included, but the functionality extends beyond those default function calls. For example, there are more filters for the 'List' functions, plus other functionality that is not exposed in the GUI examples. There's also the DLL Functions which aren't even touched on (but are made use of nonetheless). *For another example use of the Process Functions UDF see the ProcessGetWinPEImportExports UDF. Below is a list of all the functions available (check the function headers for more info): ProcessFunctions UDF's Thread Functions UDF's DLL Functions UDF's DriverList.au3 UDF: ; _DriverList() ; Returns a list of Drivers that were loaded by the O/S This is now a very comprehensive suite. Most everything a programmer or user would find useful is included. If by chance you can think of *any* other (useful) functions to add to this project, however, let me know. For those that need to measure a Process's CPU Usage, please see my PDH Performance Counters UDF, another comprehensive UDF suite. Special note: For most all _Process* functions that require a 'QUERY' info handle, use the constant $PROCESS_QUERY_LIMITED_INFO, which is set based on O/S. There's only one exception to this that I can think of: _ProcessMemoryVirtualQuery() which requires full Query access no matter what O/S (0x400). Thread* functions can make use of 2 constants which are set based on O/S - $THREAD_QUERY_LIMITED_INFO and $THREAD_SET_LIMITED_INFO. Experiment with the GUI's on Vista+ O/S's to see what's the minimum req's. Download the Source and/or GUI Exe's from my site Optional addition: Special NomadMemory UDF designed to work with ProcessFunctions: NomadMemoryPF.au3 Ascend4nt's AutoIT Code License agreement: While I provide this source code freely, if you do use the code in your projects, all I ask is that: If you provide source, keep the header as I have put it, OR, if you expand it, then at least acknowledge me as the original author, and any other authors I creditIf the program is released, acknowledge me in your credits (it doesn't have to state which functions came from me, though again if the source is provided - see #1)The source on it's own (as opposed to part of a project) can not be posted unless a link to the page(s) where the code were retrieved from is provided and a message stating that the latest updates will be available on the page(s) linked to.Pieces of the code can however be discussed on the threads where Ascend4nt has posted the code without worrying about further linking.UPDATES:
    1 point
  14. Hi usera, Search the helpfile for the MouseClick() function. Here is how you would use it to left click once at the middle of the screen: MouseClick("left", @DesktopWidth / 2, @DesktopHeight / 2) -smartee
    1 point
×
×
  • Create New...