Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/02/2023 in all areas

  1. Uploaded a set of new files to https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/SciTE5-with-DynamicFunctions/ : Updated SciTE to default the file extension to the selected filetype. Update the LUA scripts to include the variables of the current file into the AutoComplete Dropdown list when they are set ($ABC = xxxx) I am planning to have a more thorough review of the AutoComplete and Dynamic include process to ensure there are no unnecessary/duplicate processes happening.
    3 points
  2. AH ...got it ... think I know what this issue is. There is a one line mod I've made that I have missed in the latest merge of the original. This is fixed in the latest SciTEx86.zip & SciTEx64.zip. Thanks for letting me know.
    2 points
  3. I can confirm that using the file from SciTEx64.zip fixes the tab problem for me too.
    1 point
  4. of these only SciTEx64.zip has a brighter tab [ ] SciTE4AutoIt3.exe 2023-10-02 15:16 6.4M [ ] SciTE4AutoIt3_Portable.zip 2023-10-02 15:16 8.8M [ ] SciTEx64.zip 2023-10-02 09:39 1.3M [ ] SciTEx86.zip 2023-10-02 09:39 1.1M from https://www.scintilla.org/SciTE.html both 32 & 64, has a brighter tab
    1 point
  5. Musashi

    Which Debugger do you use?

    There are some beneficial keyboard shortcuts for debugging. Example : Local $iCount = 0 For $i = 1 To 5 $iCount += $i * 2 Next Place the mouse cursor on the $iCount variable in the loop. Now use ALT-D (without the - character, of course ). This will automatically insert a ConsoleWrite statement. With CTRL-SHIFT-D a MsgBox is inserted analogously. With CTRL-ALT-Z all lines inserted in this way can be removed.
    1 point
  6. Sorry, I kind of took over, I should wait and see if ioa747 is truly having the same kind of issues or not. It just seems very similar.
    1 point
  7. The full version of SciTE also has a very useful trace feature with ConsoleLog, I've used it several times to track tricky bugs.
    1 point
  8. noellarkin, ConsoleWrite, MsgBox (or ExtMsgBox ) and (Debug)ArrayDisplay have always been sufficient to date. M23
    1 point
  9. + _ArrayDisplay + FileWriteLine to write some info to a log file
    1 point
  10. ConsoleWrite() works just fine for me. I never used something else.
    1 point
  11. Correct. 5.3.8 edited by you. 5.3.8 by Neil Strange?? Only on some PC's ?? Edit* and how your 4.4.6 to looks for me. Edit2* 5.3.5 by you I first noticed it when you updated to 5.3.8. Edit3* Placing the 5.3.5 Scite.exe in the 5.3.8 folder instead of the 5.3.8 Scite.exe fixes it. Not sure if that helps?
    1 point
  12. Very important optimization: make first (array) parameter as ByRef, so the whole array will not be COPIED!! orig: Func _GoogleChart($aData, $Title = "", ... optimized: Func _GoogleChart(ByRef $aData, $Title = "", ...
    1 point
  13. Check in help file ObjEvent() for COM error handling.
    1 point
  14. You can compare the script below to your original one to see the differences. If you have additional questions, feel free to ask. int IdnToAscii( [in] DWORD dwFlags, [in] LPCWSTR lpUnicodeCharStr, [in] int cchUnicodeChar, [out, optional] LPWSTR lpASCIICharStr, [in] int cchASCIIChar ); #include <WinAPI.au3> #include <Array.au3> ;IDN (International Domain Name) Flags Const $IDN_ALLOW_UNASSIGNED = 0x01, _ ;Allow unassigned "query" behavior per RFC 3454 $IDN_USE_STD3_ASCII_RULES = 0x02, _ ;Enforce STD3 ASCII restrictions for legal characters $IDN_EMAIL_ADDRESS = 0x04, _ ;Enable EAI algorithmic fallback for email local parts behavior $IDN_RAW_PUNYCODE = 0x08 ;Disable validation and mapping of punycode. Global $hDll = DllOpen("normaliz.dll") Global $sUnicodeDomain = "bücher.example.com" Global $tOutput = DllStructCreate("wchar[255]") ;Note that IDN names have a maximum length. Global $aResult = DllCall($hDll, "int", "IdnToAscii", _ "dword", $IDN_ALLOW_UNASSIGNED, _ "wstr" , $sUnicodeDomain, _ "int" , StringLen($sUnicodeDomain), _ "wstr" , DllStructGetPtr($tOutput), _ "int" , DllStructGetSize($tOutput) _ ) If @error Then MsgBox(16, "DllCall Error", "@error = " & @error) ElseIf $aResult[0] = 0 Then MsgBox(16, "Bad return code from DllCall", "Return value: " & $aResult[0]) ConsoleWrite("ERROR: " & _WinAPI_GetLastErrorMessage() & @CRLF) Else _ArrayDisplay($aResult) MsgBox(64, "Punycode value", $aResult[4]) EndIf DllClose($hDll) Click below to see the potential and/or actual issues with the script in your original post:
    1 point
  15. Check out the code from above. I added some comments.
    1 point
  16. Melba23

    Tab background color

    MadMaxx, Here is my take on how you might do it: #include <GUIConstantsEx.au3> #include <GuiTab.au3> $hGUI = GUICreate("Test", 500, 500) $hTab_1 = GUICtrlCreateTab(10, 10, 230, 90) $hTab_10 = GUICtrlCreateTabitem("Red") _GUICtrlTab_SetBkColor($hGUI, $hTab_1, 0xFFCCCC) $hTab_11 = GUICtrlCreateTabitem("Green") _GUICtrlTab_SetBkColor($hGUI, $hTab_1, 0xCCFFCC) $hTab_12 = GUICtrlCreateTabitem("Blue") _GUICtrlTab_SetBkColor($hGUI, $hTab_1, 0xCCCCFF) GUICtrlCreateTabitem ("") ; end tabitem definition GUISetState() GUISetState() While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE Exit EndSwitch WEnd Func _GUICtrlTab_SetBkColor($hWnd, $hSysTab32, $sBkColor) Local $aTabPos = ControlGetPos($hWnd, "", $hSysTab32) Local $aTab_Rect = _GUICtrlTab_GetItemRect($hSysTab32, -1) GUICtrlCreateLabel("", $aTabPos[0]+2, $aTabPos[1]+$aTab_Rect[3]+4, $aTabPos[2]-6, $aTabPos[3]-$aTab_Rect[3]-7) GUICtrlSetBkColor(-1, $sBkColor) GUICtrlSetState(-1, $GUI_DISABLE) EndFunc M23
    1 point
×
×
  • Create New...