Timeline
Mar 11, 2023:
- 10:47 PM Ticket #842 (Adding Lua as an alternative syntax) updated by
- (i speak Of CoUrSe of the mr anonymous here.. what a dumb noob! dared to make an inquire and got a mild rebuke! haha that'll show him!! /s)
- 10:41 PM Ticket #842 (Adding Lua as an alternative syntax) updated by
- Wooooow. what an... individual this person was. Deeply disturbed.
Mar 8, 2023:
- 3:23 PM Ticket #3945 (StringRegExp help about \s misses VT) updated by
-
[…]
If the helpfile is gonna be reworked (topic StringRegExp) then I got a little issue with \xA0 e.g. chr(160) non-breaking space.
Here is a script where the subject is a string of 255 characters from chr(1) to chr(255)
You can comment out / uncomment any pattern line to display in Scite Console the ascii codes that matched.
The goal is to have a help-file even more accurate concerning
\sor[[:blank:]]etc... This rework is a real nightmare, I wonder how many days/weeks jchd spent to prepare this help file topic (especially he also indicated all code characters > 255), hats off ! […]
Mar 4, 2023:
- 4:55 PM Ticket #3946 (_ChooseFont() updated defaults) updated by
- hmm, I changed a few more things regarding errors: […] So now all errors are clearly returned. I think this is my last revision. =)
- 2:20 PM Ticket #3946 (_ChooseFont() updated defaults) updated by
- The idea for updating these aspects comes from https://www.autoitscript.com/forum/topic/209809-_choosefontex/
- 4:00 AM Ticket #3946 (_ChooseFont() updated defaults) updated by
-
Version changed
Automatic ticket cleanup. - 3:33 AM Ticket #3946 (_ChooseFont() updated defaults) updated by
- oops, did not test the prior code before posting. Here's the working code: […]
- 3:20 AM Ticket #3946 (_ChooseFont() updated defaults) created by
- added Default(keyword) to entries and color lookup, as the default of …
Mar 3, 2023:
- 3:23 PM Ticket #3945 (StringRegExp help about \s misses VT) updated by
-
Some infos concerning the evolution of Chr(11) e.g. Vertical Tab VT
Excerpts from AutoIt history and PCRE changelog, displayed by date, descending :
https://www.pcre.org/original/changelog.txt
A) AutoIt 3.3.16.1 (19th September, 2022) (Release)
B) AutoIt 3.3.16.0 (6th March, 2022) (Release)
Changed: PCRE regular expression engine updated to 8.44
C) PCRE Version 8.36 26-September-2014
13. When a pattern starting with \s was studied, VT was not included in the list of possible starting characters; this should have been part of the 8.34/18 patch.
D) PCRE Version 8.34 15-December-2013
18. The character VT has been added to the default ("C" locale) set of characters that match \s and are generally treated as white space, following this same change in Perl 5.18. There is now no difference between "Perl space" and "POSIX space". Whether VT is treated as white space in other locales depends on the locale.
E) AutoIt 3.3.8.1 (29th January, 2012) (Release)
F) PCRE Version 8.11 10-Dec-2010
3. If \s appeared in a character class, it removed the VT character from the class, even if it had been included by some previous item, for example in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part of \s, but is part of the POSIX "space" class.)
G) AutoIt 3.3.6.1 (16th April, 2010) (Release)
Test 1 : the bug in F)
======
Local $sSubject = Chr(11) ; Vertical Tab VT
Local $sPattern = '[\x00-\xff\s]'
No match using AutoIt 2010 (because of bug PCRE)
Match Chr(11) using AutoIt 2012+ (PCRE fixed the bug)
Test 2 : \s
======
Local $sSubject = a string of 256 characters, from Chr(0) to Chr(255)
Local $sPattern = '
\s' ; now same as '[[:space:]]' AutoIt 2022 => match Chr(9) Chr(10) Chr(11) Chr(12) Chr(13) Chr(32) <= 6 whitespace Test 3 : \S (mLipok's question) ====== Local $sSubject = a string of 256 characters, from Chr(0) to Chr(255) Local $sPattern = '\S' ; now same as '[[:^space:]]' AutoIt 2022 => match 250 characters (e.g. 256 - 6 whitespace above) […] So PCRE 8.45 could be the last version to integrate the next AutoIt release, because PCRE2 10.xx series may require a lot of rework for integration ? Good luck Jon - 7:51 AM Ticket #3945 (StringRegExp help about \s misses VT) updated by
-
Is there also adequate change for
\S? As so far it wasMatches any non-whitespace character.
Feb 28, 2023:
- 11:41 AM Ticket #3945 (StringRegExp help about \s misses VT) created by
- PCRE v8.44 changed the meaning of character class \s to include VT as …
Feb 27, 2023:
- 11:12 AM Ticket #3942 (@EVT_POS, @EVT_TIME, @EVT_INFO event macros) updated by
- More ref: https://devblogs.microsoft.com/oldnewthing/20140122-00/?p=2013
Feb 24, 2023:
- 2:58 AM Ticket #3944 (GUICtrlSetFont (and GUISetFont) sets font name inconsistently) created by
- The following uses of GUICtrlSetFont don't result in the same font …
Feb 22, 2023:
- 1:40 PM Ticket #3943 (Using a function return to increment an counter array element causes ...) updated by
- For what it's worth, the related issue appeared for the 1st time with AutoIt version 3.3.10.0 […] 2012 - AutoIt 3.3.8.1 => 1 call (tested) 2013 - AutoIt 3.3.10.0 => 2 calls (tested)
- 12:44 PM Ticket #3943 (Using a function return to increment an counter array element causes ...) updated by
- Presumably this affects all compound operators, not just += The solution would be to not blindly expand A[x]+=y to A[x]=A[x]+y but first capturing x in a temporary.
- 10:02 AM Ticket #3943 (Using a function return to increment an counter array element causes ...) created by
- When a function call yields an index that is used directly to …
Feb 21, 2023:
- 1:26 PM Ticket #3942 (@EVT_POS, @EVT_TIME, @EVT_INFO event macros) created by
- References: […] Motivation: Manually calling MouseGetPos() when …
Feb 18, 2023:
- 1:54 AM Ticket #3941 (ToolTip with $TIP_CENTER + $TIP_FORCEVISIBLE is mispositioned) created by
- When the ToolTip function is used with both the $TIP_CENTER and …
Feb 9, 2023:
- 2:53 PM Ticket #3940 (_GUICtrlTab_GetItemText does not work in V3.3.16.1) updated by
- hi, I have new findings. https://www.autoitscript.com/forum/topic/208604-_guictrltab_getitem-fails-to-retrieve-item-text-since-autoit-version-33160/?do=findComment&comment=1505592 When i add the x86 and x64 part of this comment i can access the text of the tab of a file property, but sadly not of the active directory window. i continue my research
- 1:57 PM Ticket #3940 (_GUICtrlTab_GetItemText does not work in V3.3.16.1) updated by
- when i use the tabs of properties from a file, i get the same results.
- 7:53 AM Ticket #3940 (_GUICtrlTab_GetItemText does not work in V3.3.16.1) updated by
- Thanks, But I have not the environment to replicate (no Active directory on my side) could you find the same ith noa active directory Cheers
Note:
See TracTimeline
for information about the timeline view.
