Timeline
May 9, 2015:
May 4, 2015:
- 9:30 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- > -9223372036854775808 and -9223372036854775807 yield the same result. Only when using a site which limits integral values to Int32 or under the double tab. And no they are not the same value and both are valid int64 values.
- 8:59 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- Not Int with Double confused !! http://calc.penjee.com/?s=HJJJJJJJJJJJJJJJ
- 8:32 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- That's not an Int64 value, it's too large. When converting it to a 64 bit value, -9223372036854775808 and -9223372036854775807 yield the same result. http://www.binaryconvert.com/result_double.html?decimal=045057050050051051055050048051054056053052055055053056048056
May 3, 2015:
- 9:11 PM Ticket #3019 (#2LOYPRUVG) closed by
- No Bug
- 6:51 PM Ticket #3019 (#2LOYPRUVG) created by
- 1:50 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) closed by
- Fixed: Fixed by revision [11281] in version: 3.3.13.21
May 2, 2015:
- 6:10 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) updated by
- Same for lightnessLevel https://msdn.microsoft.com/en-us/library/windows/desktop/ms534069(v=vs.85).aspx
- 5:33 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) created by
- In the help file (Release&Beta) saturation limits are -180 to 180 but …
May 1, 2015:
- 9:55 PM Ticket #1479 (ListView WM_NOTIFY Message on x64 Returning Wrong Results) updated by
- Forgot to mention that the bug in the current version is still available.
- 9:08 PM Ticket #1479 (ListView WM_NOTIFY Message on x64 Returning Wrong Results) updated by
- If you change the following in the file StructurConstants.au3 then it works with 32bit and 64bit. from […] to […] This probably applies to other structures in this file.
- 2:13 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- This is rather the largest negative int64 value, but yes there seems to be an issue with parsing the literal value -9223372036854775808.
- 12:49 PM Ticket #1686 (AU3_PixelSearch crashes with access violation at address 0x00000008) updated by
- Replying to Jpm: > Fixed by revision [5893] in version: 3.3.7.0
- 12:47 PM Ticket #3017 (The largest negative integer value we misinterpret) created by
- The following code illustrates the problem […] at …
Apr 27, 2015:
- 9:44 AM Ticket #3016 (FileSetPos() not used in FileSetPos() example) closed by
- No Bug: No bug there is a FileSetPos() after the 1st MsgBox()
- 6:33 AM Ticket #3016 (FileSetPos() not used in FileSetPos() example) created by
- The example for FileSetPos() does not contain any use of FileSetPos(). …
Apr 24, 2015:
- 1:00 PM Ticket #2901 (Text file as a binary) updated by
- Bumped for visibility.
- 2:22 AM Ticket #2989 (@OSVersion And Windows 10) updated by
- You could always just run FileGetVersion("Winver.exe") and get the same basic information. On my Windows 7 SP1 system it return 6.1.7600.16385. The 6.1 corresponds to the 601 in the table, the 7600 is the build number.
- 1:46 AM Ticket #2989 (@OSVersion And Windows 10) updated by
- as reply to BrewManNH's question in comment no3: that's the "microsoft way". the underlying "core" (or kernel) is identical for certain client and server os. 601 = win 7 / 2008 R2; 602 = win 8.0 / 2012. and that's exactly what we developers are interested in - the underlying "core". it's the information we need to add in our log files (e.g. "Log("OsVersion: " + @OSVersionNT)" and also the information we may use for conditional code execution (e.g. "If(@OSVersionNT > 603)".
Apr 23, 2015:
- 7:53 PM Ticket #2989 (@OSVersion And Windows 10) updated by
- In a follow up to comment #3, why would you want that returned? It's a very untrustworthy way of determining the OS version. Using that you'd never know if you were running Win 7 or Server 2008, for an example, unless you further checked to see if the OS is a server or not.
- 5:00 PM Ticket #2989 (@OSVersion And Windows 10) updated by
- in the same context it would be nice to introduce a new macro "@OSVersionNT" that returns a numeric value the mirosoft way: https://msdn.microsoft.com/en-us/library/aa370556.aspx (e.g. windows 2000 = 500; windows xp = 501; windows 7 = 601; windows 8.0 = 602)
- 4:48 PM Ticket #2989 (@OSVersion And Windows 10) updated by
- also see RtlGetVersion to avoid the requirement of manifestation - as proposed in http://www.autoitscript.com/forum/topic/166932-os-version/
Apr 22, 2015:
- 8:28 AM Ticket #3015 (Object Schedule.Service) created by
- I did not test all Beta versions. On 3.3.13.5 it is working. And on …
Apr 20, 2015:
- 6:33 PM Ticket #3012 (GUISetFont - no default value for parameter: attribute) updated by
- There is no value for the default, I would assume in this case the default value would be zero, meaning no attribute set. There's no constant to put in that parameter in the GUIConstantsEX.au3 file. We'd have to use a made up constant name if zero wasn't sufficient for there, which sort of goes against using the defined variables that the Windows API uses. But that decision is above my paygrade, and I'd just use the Default keyword, or zero.
Apr 18, 2015:
- 10:17 PM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') updated by
- After deliberation, I have to agree with your opinion, and also to ask you to consider, adding an appropriate description for the Help documentation, because this was not clear for me so can be not clear for others, especialy non native english coders.
- 7:43 PM Ticket #3013 (Forum Intelligent Seach) closed by
- Rejected: The Search comes with the forum software we use so changes need to be requested there. .. or simply use Google. Jos
- 7:42 PM Ticket #3014 (Intelligent Forum Search) closed by
- Duplicate
- 12:02 PM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') closed by
- No Bug: I am going to close this. It seems illogical to me that the function should deal with adding/subtracting an interval smaller than the lowest interval defined in the DTG passed to it. If the user wants to add/subtract a time interval they need to define the start time, not expect the function to default to some arbitrary value. M23
- 1:00 AM Ticket #3014 (Intelligent Forum Search) updated by
-
Version changed
Automatic ticket cleanup. - 12:11 AM Ticket #3014 (Intelligent Forum Search) created by
- I'd like to see a Forum Intelligent Search option in addition to …
- 12:00 AM Ticket #3013 (Forum Intelligent Seach) updated by
-
Version changed
Automatic ticket cleanup.
Apr 17, 2015:
- 11:56 PM Ticket #3013 (Forum Intelligent Seach) created by
- Id like to see a Forum Intelligent Search option in addition to …
- 8:28 AM Ticket #3012 (GUISetFont - no default value for parameter: attribute) updated by
- I forgot to add some additional request: Please consider making appropriate changes.
Apr 14, 2015:
- 10:42 PM Ticket #3012 (GUISetFont - no default value for parameter: attribute) created by
- In HelpFile documentation there is lack of information about the …
Apr 13, 2015:
- 8:06 AM Ticket #3011 (_FileListToArrayRec does not closes file handle) closed by
- Fixed: Fixed by revision [11269] in version: 3.3.13.21
- 8:05 AM Ticket #3011 (_FileListToArrayRec does not closes file handle) updated by
- I have discovered why there is a difference between 3.3.12.0 and 3.3.13.20 - in the latter only asking to exclude symbolic links from the UDF return uses the DLL call, excluding hidden and system files is done using the native FileFindFirstFile function. When I change the function parameters to exclude links I get the same results as you. Thanks for the report I will amend the UDF accordingly. M23
Note:
See TracTimeline
for information about the timeline view.
