Timeline



Aug 3, 2018:

6:09 PM Ticket #3647 (Ghost border artifact with _GDIPlus_ImageResize) updated by anonymous
See also (somewhat) related ticket # 3650
6:08 PM PaintScreenshot.png attached to Ticket #3650 by anonymous
6:08 PM TestResult.png attached to Ticket #3650 by anonymous
6:08 PM TestImage.png attached to Ticket #3650 by anonymous
6:07 PM Ticket #3650 (Image size off-by-one error with_GDIPlus_ImageResize) created by anonymous
The function _GDIPlus_ImageResize creates images that seem to have an …
4:59 PM Ticket #3647 (Ghost border artifact with _GDIPlus_ImageResize) updated by anonymous
Some obligatory test code: #include <GDIPlus.au3> _GDIPlus_Startup() Local $hImage = _GDIPlus_ImageLoadFromFile(@ScriptDir & "\TestImage.png") Local $iWidth = _GDIPlus_ImageGetWidth($hImage) Local $iHeight = _GDIPlus_ImageGetHeight($hImage) Local $hBitmap = _GDIPlus_ImageResize( _ $hImage, $iWidth * 4, $iHeight * 4, _ $GDIP_INTERPOLATIONMODE_HIGHQUALITYBICUBIC) _GDIPlus_ImageSaveToFile($hBitmap, @ScriptDir & "\TestResult.png") Sleep(500) _GDIPlus_BitmapDispose($hBitmap) _GDIPlus_ImageDispose($hImage) _GDIPlus_Shutdown()
4:48 PM Ticket #3647 (Ghost border artifact with _GDIPlus_ImageResize) updated by anonymous
More good info about this issue here: https://photosauce.net/blog/post/image-scaling-with-gdi-part-3-drawimage-and-the-settings-that-affect-it here
4:43 PM Ticket #3647 (Ghost border artifact with _GDIPlus_ImageResize) updated by anonymous
Or to put it another way, in order to prevent the edge from doing interpolation against the default background, provide the DrawImage method with an ImageAttributes instance which has WrapMode set to TileFlipXY.
4:00 PM Ticket #3649 (Add the word glob to docs for search engines) updated by TicketCleanup
Version changed
Automatic ticket cleanup.
3:30 PM Ticket #3649 (Add the word glob to docs for search engines) updated by anonymous
This would also be applicable on the docs for the FileFindFirstFile and FileFindNextFile functions.
3:18 PM Ticket #3649 (Add the word glob to docs for search engines) created by anonymous
People coming from other languages may search for the words "glob" or …
8:53 AM Ticket #3648 (_ISPressed not working with "GUI_WS_EX_PARENTDRAG") created by Memnon
https://www.autoitscript.com/forum/topic/195130-gui-with-_ispressed-and
2:56 AM Ticket #3647 (Ghost border artifact with _GDIPlus_ImageResize) created by anonymous
The function _GDIPlus_ImageResize creates images that exhibit the …

Aug 1, 2018:

12:25 PM Ticket #1130 ($tagNMLVKEYDOWN stuct not working in x64 OS) closed by J-Paul Mesnage
Duplicate: It has been fixed for the next Beta on my birthday …
9:00 AM Ticket #1130 ($tagNMLVKEYDOWN stuct not working in x64 OS) updated by TicketCleanup
Milestone changed
Automatic ticket cleanup.
8:59 AM Ticket #1130 ($tagNMLVKEYDOWN stuct not working in x64 OS) reopened by Melba23

Jul 27, 2018:

5:31 AM Ticket #1130 ($tagNMLVKEYDOWN stuct not working in x64 OS) updated by supersonic
It seems that this ticket still needs some attention. Using AutoIt V3.3.14.5 running in 64 bit $tagNMLVKEYDOWN (-> VKey) returns always 0. Please re-check :) For a solution/workaround please see: https://www.autoitscript.com/forum/topic/195016-lvn_keydowntagnmlvkeydown-does-not-work-in-64-bit/

Jul 20, 2018:

7:04 PM Ticket #3627 (Feature Request: AutoItWinGetHandle()) updated by BrewManNH
What exactly do you need the handle of the hidden window for? In 8 years of using AutoIt, I don't think I've ever seen anyone that ever needed that information, so I'm curious as to why you think this is necessary.

Jul 19, 2018:

8:23 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) closed by Melba23
No Bug
8:21 AM Ticket #3645 (StringRegExpSplit) closed by Melba23
Rejected
1:40 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) updated by jchd18
It seems #cs & #ce somehow nest: it appears you need as many #ce as #cs. If you have one more of any of #cs or #ce, the interpretor barks. Here it complains about "extra": […] I wouldn't qualify this behavior as "bug": say "feature".
1:27 AM Ticket #3645 (StringRegExpSplit) updated by jchd18
It can still work: […] But maybe you'll tell us that if the subject has adjacent separators it won't again work the way you expect it to. Note that since the function is an actual one-liner, there is no real purpose for a new function: it's simpler to code it inline with the ad-hoc pattern suited to the case being handled. Also Trac isn't the place to discuss various regexes; better post a topic in help and when & if a new function emerges from discussion then it'll be time to place a feature request here.
1:03 AM Ticket #3645 (StringRegExpSplit) updated by genius257
Hmmm seems to work for almost everything, except the following. […] But the chances for that to give me problems currently are slim :)

Jul 18, 2018:

10:59 PM Ticket #3645 (StringRegExpSplit) updated by Jos
Something like this? […] Jos
9:39 PM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) created by genius257
The following code […] Results in […] Shouldn't anything …
11:28 AM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
Yeah, the last one was meant to be […] And i do get that StringRegExp CAN solve this, it simply seems like a ease of use function. Especially when converting from one language (like js or php) to AutoIt
9:40 AM Ticket #3645 (StringRegExpSplit) updated by Melba23
The first 2 are easy to do with the existing function: […] No idea about the last one as the given input does not match the required output in any way. M23

Jul 17, 2018:

5:09 PM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
Well it seems i forgot the code block Here's the examples with the code block […]
5:05 PM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
In a small, simple example, yes. StringRegExpSplit("|a|| |b|| c| ||d|", "\s*\|\|\s*") [ "|a", "|b", "c|", "d|" ] Or StringRegExpSplit("|a|| |b|| c| ||d|", "\s*(\|\|)\s*") [ "|a", "||", "|b", "||", "c|", "||", "d|" ] Or StringRegExpSplit("Hello 1 word. Sentence number 2.", "(\d)") [ "Hello ", "1", " word. Sentence number ", "2", "." ]
1:47 PM Ticket #3627 (Feature Request: AutoItWinGetHandle()) updated by therks
I suppose if that variable is set and used like a constant (at the beginning of a script launch), there would probably be no problems. But if the lookup for the window handle happens some time after launch (eg: from a UDF) when the calling process is not focused, it could return the incorrect handle. For example, if you have a folder open titled "AutoIt v3" and your script calls WinGetHandle(AutoItWinGetTitle()) a few minutes after it was first launched, it will return the Explorer window. Maybe it would even be more appropriate as a macro, like @AutoItWinHandle. I guess it doesn't matter though as it seems I'm the only one interested.
10:34 AM Ticket #3645 (StringRegExpSplit) updated by Melba23
You mean like this: […] M23
6:52 AM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
Yes and no. Yes that it's by using regular expression. No because StringRegExp returns the part of string matched by the pattern. For example StringRegExpSplit("abc", "(:?)") would return ["a", "b", "c"]

Jul 16, 2018:

9:16 PM Ticket #3645 (StringRegExpSplit) updated by Jos
as in StringRegExp() you mean? Jos
9:12 PM Ticket #3645 (StringRegExpSplit) created by genius257 <hot415@…>
A core function to split strings by regular expression.

Jul 15, 2018:

10:06 PM Ticket #3560 (parentheses around function refference fails when follwed by calling ...) updated by genius257 <hot415@…>
Hi Jos :) I've tried the au3check.exe from the autoit-v3.3.15.1.zip of the beta download, and i still seem to get the same problem. Sorry for the slow response, i have tried adding my mail my preferences in hope that i will get a notification when there's responses in a ticket i participate in :) […]
Note: See TracTimeline for information about the timeline view.