Leaderboard

This statement will only delete line 2 ... not the whole file! You must have done something wrong somewhere. Jos

Did you search? I did >>

Version 0.9 BETA is finnaly online! ATTENTION: Please do not wonder if you updated ISN AutoIt studio from an older version that appears the initial configuration assistent! This is normal because the data is stored differently from version 0.9! But with the initial configuration assistent you can apply easily your old configuration, projects, templates to the new version. Changelog 0.9 BETA (translated by google translator) -> ISN AutoIt Studio: <- ----------------------------------- - Fix: bug fixes in the context menu of the Script Editor - Fix: Fix closing of a project - Fix: If the script editor "$" are the key variables in the project (if enabled) now min. Read 10x faster than before - Fix: create a new macro can now be Canceled - Fix: Fix for storing comments in the script tree - Fix: Various bug fixes - NEW: Added editor mode (The AutoIt Studio is similar to the SciTE4AutoIt3 editor) -> No project is required! -> In the editor mode, however, certain features (eg. project properties or autocomplete for global variables) not to dispose! -> The project tree is used as a file explorer. So you can quickly and easily open files - NEW: Hotkeys for ISN AutoIt Studio can now be changed by the user - NEW: terms like "Slot Rule" and "project" rule were changed into macro or macro slot. (Makes more sense since it is illogical to define rules in the editor mode project although it is garkein project more ...) - NEW: Welcome revised - NEW: projects, settings, templates, now is not saved directly in the program directory but (by default) under My Documents (My Documents) ISN AutoIt Studio - NEW: New Ersteinrichtungsassistent - NEW: ISN AutoIt Studio can be integrated into the context menu of Windows Explorer so fast and easy to open files in the editor mode au3 - NEW: au3 files can now be directly linked to the ISN (editor mode) - NEW: au3, isn and isp files now when launching ISN as parameters - NEW: list "Recent Items" expanded (The list now shows files in the editor mode) - NEW: (empty) list of "Recent Items" in the program settings can now be reset - NEW: More elements in the program settings - added> Advanced. - NEW: Files in the ISN AutoIt Studio can not be opened (not using plugin) will now pass through to Windows ShellExecute (eg useful for PDF files.) - NEW: Added French language, thx to Marcles (currently still follows for version 0.88 BETA program, update ...) - NEW: In the project tree can now be created right-click a copy of the selected file - NEW: Revised project management (eg project templates can now be renamed) - NEW: Revised Project Properties - NEW: In the dialog box "Create new project" can now also be created a Blank Project - NEW: ISN AutoIt Center will now automatically check for online updates (default is every 14 days) - NEW: In the "File" menu now is the point to find "Recent Files". Here are the 10 most recently used files in the project (or editor mode) are displayed. - NEW: function "Save as ..." in the "File" menu - NEW: The "DebugtoMsgBox" and "DebugtoConsole" set in the "debugging" found under "Tools"! (Or, in the context menu of the Script Editor) - NEW: In the "Tools" menu now is the point to find the "Create UDF header" (As a writer, the author of the project we automatically inserted in the script tree and if a comment is found that the same is also included.! - NEW: function "duplicate row" added in the script editor - NEW: The Projektdeteils can be exported in the project management and the project properties as a csv file. - NEW: The script editor now supports the new color scheme for au3 code (you can switch between old and new in the program settings.) - NEW: "Create New File" sub can now choose whether the new file to be created should be empty (default) or from a template - NEW: New Song Credits - NEW: If the script editor "$" button you can now choose whether the entire project or only in the current script looks for variables - NEW: If the script editor "$" button in the status bar shows the progress in reading the variables shown - NEW: In the "Tools" menu then the item "AutoIt3Wrapper GUI" can be found. So you can easily manage your wrapper script commands. The changes are automatically reflected in the ISN! - NEW: In the "Help" menu is now a menu item called "donations". This allows you to project the ISN AutoIt studio support something. All "donors" come on request in the credits. THANK YOU!! - NEW: New Macro: Run Command -> Executes command using Execute out. With Execute can eg. arbitrary functions from the ISN AutoIt Studio (see source code) to run! (Please use only if you know what you're doing!) - NEW: script elements in the tree will have a comment now shown bold - NEW: New file icon for isp files. - NEW: In the program settings now, the character set (encoding) for the script editor to be selected (eg. UTF-8) - NEW: The "Organize Includes" is now in the menu to find the "tools" - NEW: Revised Start logo - NEW: Several small changes -> ISN form Studio 2: <- ----------------------------------- - Fix: Various bug fixes - NEW: In the "Text / Data" is now the "..." Button opens a window into the clear text can be entered. Even with line breaks! (Useful eg. At labels) - NEW: available to order with in the GUI now displays a grid - NEW: Use CTRL + A can now all controls are quickly marked - NEW: Controls can now be locked in the "Control Editor" in order to protect against most changes - NEW: The order of the controls can now be set arbitrarily -> Homepage (www.isnetwork.at.pn): <- ----------------------------------- - NEW: In the menu of the ISN AutoIt Studios can be found under downloads then select "change language files". Here all the changes in the language packs (. Lng files) from version to version will be logged. So it is easier for translators to get their language up to date as they see exactly what items have changed from the previous version.

incepator, I would do it like this: #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <File.au3> Global $aRecent, $aMenu_CID[1] = [0] $sRecent = @ScriptDir & "\recently.txt" $Form1 = GUICreate("Form1", 615, 438, 192, 124) $Menu1 = GUICtrlCreateMenu("File") $MenuItem2 = GUICtrlCreateMenuItem("Add Keywords", $Menu1) $Menu2 = GUICtrlCreateMenu("Recent files", $Menu1) $MenuItem5 = GUICtrlCreateMenuItem("Clear List Recent", $Menu1) $MenuItem6 = GUICtrlCreateMenuItem("Exit", $Menu1) GUISetState(@SW_SHOW) If FileExists($sRecent) Then _FileReadToArray($sRecent, $aRecent) If IsArray($aRecent) Then For $i = 1 To $aRecent[0] $aMenu_CID[0] += 1 ReDim $aMenu_CID[$aMenu_CID[0] + 1] $aMenu_CID[$aMenu_CID[0]] = GUICtrlCreateMenuItem($aRecent[$i], $Menu2) Next EndIf Else $write = FileOpen($sRecent, 1) FileClose($write) EndIf While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE, $MenuItem6 Exit Case $MenuItem5 $write = FileOpen($sRecent, 2) FileClose($write) GUICtrlDelete($Menu2) $Menu2 = GUICtrlCreateMenu("Recent Files", $Menu1, 1) Global $aMenu_CID[1] = [0] Case $MenuItem2 $open_file = FileOpenDialog("Add Keywords List", @ScriptDir & "\", "Txt (*.*)", 1) If Not @error Then $write = FileOpen($sRecent, 1) FileWriteLine($write, @CRLF & $open_file) FileClose($write) $aMenu_CID[0] += 1 ReDim $aMenu_CID[$aMenu_CID[0] + 1] $aMenu_CID[$aMenu_CID[0]] = GUICtrlCreateMenuItem($open_file, $Menu2) EndIf Case Else For $i = 1 To $aMenu_CID[0] If $nMsg = $aMenu_CID[$i] Then $sText = GUICtrlRead($aMenu_CID[$i], 1) ConsoleWrite($sText & @CRLF) ExitLoop EndIf Next EndSwitch WEnd Any questions? M23

I fully understand the logic with BitOR() and the potential issues when the constants aren't correct, but assuming we did a proper job creating these constants, there should be no need to be anal about it: #include <WindowsConstants.au3> ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $WS_CLIPCHILDREN = ' & $WS_CLIPCHILDREN & @crlf) ;### Debug Console ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $WS_OVERLAPPEDWINDOW = ' & $WS_OVERLAPPEDWINDOW & @crlf) ;### Debug Console ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : BitOR($WS_OVERLAPPEDWINDOW, $WS_CLIPCHILDREN) = ' & BitOR($WS_OVERLAPPEDWINDOW, $WS_CLIPCHILDREN) & @crlf) ;### Debug Console ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $WS_OVERLAPPEDWINDOW +$WS_CLIPCHILDREN = ' & $WS_OVERLAPPEDWINDOW + $WS_CLIPCHILDREN & @crlf) ;### Debug Console Jos

Since there _is_ fully compliant Unicode support built into every Windows system in a very efficient way, I don't see why we shouldn't make use of it. For instance, every Explorer windows sort contents (folders, links, files) in Unicode order compliant with UCA for your locale setting and in pseudo-real time. The only catch is how to access that set of functionnalities effectively.

Either way, array created in the timer or outside, the difference isn't all that great. It's still slow no matter how you time the reverse function.

czardas, I came across this post when doing some research about _strrev >> http://stackoverflow.com/questions/52002/how-to-check-if-the-given-string-is-palindrome (funny!) #include <Array.au3> Local $aString = StringSplit('StringReversed, see how it'' backwards now.', '', 2) ; I don't know the Constant.au3 value for this. StringReverseChrArray($aString) _ArrayDisplay($aString) Func StringReverseChrArray(ByRef $aString) ; Converted from this: http://marc.info/?l=php-general&m=120422082915762 Local $sChr = '', $i = 0, $j = UBound($aString) - 1 While ($i < $j) $sChr = $aString[$i] $aString[$i] = $aString[$j] $aString[$j] = $sChr $i += 1 $j -= 1 WEnd EndFunc ;==>StringReverseChrArray I believe what she says is true, she's a very smart lady indeed.

#include <GUIConstantsEx.au3> #include <ListViewConstants.au3> #include <StaticConstants.au3> #include <WindowsConstants.au3> #include <GuiListView.au3> $Form1 = GUICreate("Form1", 633, 447, 193, 125) $ListView1 = GUICtrlCreateListView("From|To||", 136, 72, 170, 150, BitOR($LVS_REPORT,$LVS_SINGLESEL,$LVS_SHOWSELALWAYS,$WS_VSCROLL)) GUICtrlCreateListViewItem("60 wide|not 60 wide||", $ListView1) GUICtrlCreateListViewItem("1234567890|1234567890", $ListView1) _GUICtrlListView_SetColumnWidth($ListView1, 0, 60) _GUICtrlListView_SetColumnWidth($ListView1, 1, 60) _GUICtrlListView_SetColumnWidth($ListView1, 2, 1) _GUICtrlListView_SetColumnWidth($ListView1, 3, 1) GUISetState(@SW_SHOW) While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit EndSwitch WEnd This should do what you're looking for. Try setting the width after you've filled the listview.

There's a very simple solution to all this: Don't use global variables. That's not entirely true because AutoIt more or less forces you to use global variables for a lot of stuff. However, proper hiding the variable behind an API makes them safe.