Timeline
Feb 28, 2021:
- 4:31 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) closed by
- Completed: Added by revision [12494] in version: 3.3.15.4
- 3:59 PM Ticket #3804 (_GUICtrlMenu_CreateMenu() example) closed by
- Completed: Added by revision [12493] in version: 3.3.15.4
Feb 26, 2021:
- 7:13 AM Ticket #3702 (Make Execute capable of processing declarations) closed by
- Rejected: no answer so I assume I am right!!! so I close it
Feb 24, 2021:
- 10:09 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- ..also, to avoid all those #include, this next example may be a better fit […] by adding GDIPlus_GetSysColor() as an internal function.
- 9:49 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- ...actually my request is because I use https://www.autoitscript.com/forum/files/file/489-my-fine-tuned-high-contrast-theme/ and I don't have black as default text, so, to have a proper default we'd have to lookup the default color by If $iARGB = Default Then $iARGB = _WinAPI_SwitchColor(_WinAPI_GetSysColor($COLOR_WINDOWTEXT)) + 0xFF000000 so the modified example is […]
- 9:24 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- All "Brush" in GDIplus use ARGB. It should not be a "got ya". The function can exclude the Alpha aspect altogether and pass a $iRGB, but the extra $iARGB is from _GDIPlus_BrushCreateSolid(). On the other hand, an alpha of 0x00 is like .. will show nothing. So adding the 0xFF would aid a scripter that did not read the included help ( that by then will have a use example ). I vote for "no alpha force" to keep it in line with _GDIPlus_GraphicsDrawStringEx() where the _GDIPlus_BrushCreateSolid() calls for ARGB.
- 5:54 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- Thanks, so I think If alpha = 0 then we need to force alpha = 0xff right?
- 3:37 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- yes. I only added the default for _GDIPlus_BrushCreateSolid(), and this function calls for it. In my testing below, it shows to work with Alpha other than FF […]
- 12:07 PM Ticket #3807 (GUISetIcon does not display the correct icon in task bar) updated by
-
Owner, Status changed
Thanks, fix set to Jon
Feb 23, 2021:
- 1:16 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
- Hi, Do you understand why it is working only if alpha channel is set to FF 0XFF0000 does not work with the AutoIt Example
Feb 22, 2021:
- 1:54 PM Ticket #3807 (GUISetIcon does not display the correct icon in task bar) created by
- #include <GUIConstantsEx.au3> Example() Func Example() Local $hGUI …
- 1:20 PM Ticket #3805 (Missing letter t at the end of $tagRID_DEVICE_INFO_KEYBOARD definition) closed by
- Fixed: Fixed by revision [12491] in version: 3.3.15.4
Feb 21, 2021:
- 3:00 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) updated by
-
Version changed
Automatic ticket cleanup. - 2:19 PM Ticket #3806 (_GDIPlus_GraphicsDrawString() with color) created by
- _GDIPlus_GraphicsDrawString() is a wrapper for …
Feb 19, 2021:
- 7:26 PM Ticket #3805 (Missing letter t at the end of $tagRID_DEVICE_INFO_KEYBOARD definition) created by
- In file WinAPISys.au3. Currently it is : Global Const …
Feb 18, 2021:
- 4:29 PM Ticket #3116 ($WIN_STATE_* Constants Does Not Exist in AutoItConstants.au3) updated by
- Still not there in SciTE Version 3.6.6
Feb 11, 2021:
- 9:00 PM Ticket #3804 (_GUICtrlMenu_CreateMenu() example) updated by
-
Version changed
Automatic ticket cleanup. - 8:55 PM Ticket #3804 (_GUICtrlMenu_CreateMenu() example) created by
- _GUICtrlMenu_CreateMenu() can be a blocking function, or not but, to …
Feb 6, 2021:
- 8:27 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) updated by
- Replying to Jpm: > Hi, > You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). > The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. > in specific case an extra delay of 10 is added when the focus is not at the right place > so there is not bug Actually, that's not the issue which I am addressing. I am very aware that MouseClickDelay does affect the delay AFTER the click, but not the delay DURING the click. The fact that the delay DURING the click cannot be changed for ControlClick is the issue itself, in other words the bug is not fixed, the MouseClickDownDelay still refuses to affect the delay DURING the click of ControlClick
- 8:25 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) updated by
- Replying to Jpm: > Hi, > You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). > The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. > in specific case an extra delay of 10 is added when the focus is not at the right place > so there is not bug
- 7:58 AM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) closed by
- No Bug: Hi, You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. in specific case an extra delay of 10 is added when the focus is not at the right place so there is not bug
Feb 4, 2021:
- 7:32 PM Ticket #3793 (Add project explorer and open folder options in scite) updated by
- This is a Plugin for Notepad++. I am using the standard SciTE.exe & SciLexer.dll published by Neil as a base. NotePad++ is also using SciLExer.dll for the Syntax Highlighting, but is a total different Editor. Jos
- 6:48 PM Ticket #3793 (Add project explorer and open folder options in scite) updated by
- I saw Notepad++ which uses the same text edit control as Scite have it: https://github.com/funap/npp-explorer-plugin Do by "standard option" you mean that you have not modified the source code of Scite itself for AutoIt and it's stock Scite with with simply AutoIt specific conf?
- 4:18 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) created by
- I recently opened up a post discussing how the "MouseClickDelay" …
Feb 3, 2021:
- 7:59 PM Ticket #3802 (Window is not activated by a partial title) closed by
- No Bug: This is not a support forum, so please visit our support forums for questions and only post here when you have a confirmed bug. Thanks, Jos
- 7:12 PM Ticket #3802 (Window is not activated by a partial title) created by
- A C# / .Net 5.0 console project. […] The output: […] Why …
- 8:49 AM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) updated by
- A simpler solution is to use the unique file identifier via GetFileInformationByHandle. It is Available in Windows XP.
Feb 2, 2021:
- 11:42 PM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) updated by
- Vista is older than Windows 7. I assume you meant Windows XP? The lowest Windows version the current AutoIt3 version supports is Windows XP. It is true that GetFinalPathNameByHandleA is not supported in Windows XP, however there is a way to get the same result on Windows XP: https://stackoverflow.com/questions/65170/how-to-get-name-associated-with-open-handle/5286888#5286888
- 10:35 AM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) closed by
- Wont Fix: Sorry to close this ticket as this function is only available starting Vista/Server 2008. We still want AutoIt to be used with Windows 7 …
Feb 1, 2021:
- 9:23 PM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) created by
- It would be nice if AutoIt used something like …
Jan 31, 2021:
- 5:28 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Replying to Ant: > Yes. They work fine when dropped into the SciTE4AutoIt set-up. > > No problem! It's just frustrating knowing the answer's out there. Thanks for persisting and for going to the trouble of accommodating earlier processors. :) Thanks for letting me know. :)
- 4:08 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Yes. They work fine when dropped into the SciTE4AutoIt set-up. No problem! It's just frustrating knowing the answer's out there. Thanks for persisting and for going to the trouble of accommodating earlier processors. :)
Note:
See TracTimeline
for information about the timeline view.
