Timeline
Dec 31, 2012:
- 4:38 PM Ticket #2296 (SHA2 for Crypt.au3) updated by
- Replying to jNizM: > ALG_ID (Windows) > http://msdn.microsoft.com/en-us/library/windows/desktop/aa375549(v=vs.85).aspx thanks, that certainly means that MS does not support it !!!
Dec 28, 2012:
- 9:36 AM Ticket #2296 (SHA2 for Crypt.au3) updated by
- ALG_ID (Windows) http://msdn.microsoft.com/en-us/library/windows/desktop/aa375549(v=vs.85).aspx
- 9:32 AM Ticket #2296 (SHA2 for Crypt.au3) updated by
- any reason why SHA_224 not available in the proposal?
Dec 27, 2012:
- 12:36 PM Ticket #2296 (SHA2 for Crypt.au3) updated by
- Windows XP with SP3: This algorithm is supported Windows XP with SP2, Windows XP with SP1, and Windows XP: This algorithm is not supported.
- 12:00 PM Ticket #2296 (SHA2 for Crypt.au3) updated by
-
Version changed
Automatic ticket cleanup. - 11:48 AM Ticket #2296 (SHA2 for Crypt.au3) created by
- see here: http://autoit.de/index.php?page=Thread&threadID=35302 …
Dec 25, 2012:
- 9:08 AM Ticket #2295 (Help on ObjGet) updated by
-
Description changed
The line with ObjEvent needs to go away from current example.
Dec 24, 2012:
- 12:00 PM Ticket #2295 (Help on ObjGet) updated by
-
Version changed
Automatic ticket cleanup. - 11:32 AM Ticket #2295 (Help on ObjGet) created by
- I had to add an empty function, to make example two work, in the help …
Dec 23, 2012:
- 8:49 AM Ticket #2294 (ControlGetText failing when window title happens to contain umlauts) closed by
- No Bug: Your error is of semantic nature considering this works: […]
- 5:47 AM Ticket #2294 (ControlGetText failing when window title happens to contain umlauts) created by
- Sample: $Aktiivne_Suund = ControlGetText($MAINWIN,"Piiriületus", …
Dec 22, 2012:
- 10:30 AM Ticket #2293 (_GDIPlus_GraphicsDrawImage crashes if we dispose the bitmap.) closed by
- No Bug: So you are disposing image object and then use pointer to released object to draw. Then you report bug because of the crash you get. ...I'm sorry for you waiting 4 days for developer (OMG!) response and for AutoIt not having one person with enough knowledge and capability to close this report earlier. Clearly we are doing something wrong. I'm also sure that some time from now you will say for yourself: "Oh that was embarrassing, shame on me." Btw, Your code is unrunnable.
Dec 18, 2012:
Dec 17, 2012:
- 6:36 PM Ticket #2292 (_IEErrorNotify() and $_IEErrorNotify are conflicting, in IE.au3 for 3.3.9.5) closed by
- No Bug: That version of AutoIt is outdated at this point and wasn't meant to be anyhing more than a sort of a teaser showing very basic concept of future development (that have taken place in the meantime). I'm not sure why is that still available for downloading. The only smart thing to do for me is close this report as no_bug therefore and ask you no to report bugs relaed to that version in the future.
- 12:22 PM Ticket #2292 (_IEErrorNotify() and $_IEErrorNotify are conflicting, in IE.au3 for 3.3.9.5) created by
- The function name and the variable name $_IEErrorNotify / …
Dec 15, 2012:
- 7:13 PM Ticket #2291 (AutoIt causes memory leak?) closed by
- Works For Me: Sorry, I see no leakage.
Dec 14, 2012:
- 8:29 AM Ticket #2291 (AutoIt causes memory leak?) created by
- Hey guys, im writing on my project and got some memory leaks. Actual …
Dec 8, 2012:
- 8:24 AM Ticket #2289 (PixelGetColor - output options) closed by
- Rejected
- 8:23 AM Ticket #2289 (PixelGetColor - output options) updated by
- It seems such discussion have to take place in the Forum. From the point of view of the track, unless there is really a bug which can be reproduced just open a new ticket as Bug. For the feature request no need to change the reporting type just use Hex() when needed
- 4:23 AM Ticket #2289 (PixelGetColor - output options) updated by
- I'm having trouble reproducing it in a controlled environment, but when values that should have been matching up in my bot weren't, I had it output the values and they were confirmed not matching up. Then, I'd have it output it as Hex($color,6) and it would be the correct value, even though that hex value did not match the decimal value it had shown prior. After using Dec(Hex(PixelGetColor($x,$y),6)), the problem went away and hasn't reoccurred.
- 1:46 AM Ticket #2289 (PixelGetColor - output options) updated by
- The function returns the color of the pixel at the location specified. Either the color you're having it look for is different than what you think it should be, or there's a shade variation. The function PixelGetColor returns a decimal value, which can easily be converted with the Hex function. I don't see an overwhelming need to have the devs add functionality when it's easy to get it another way with a function that already exists. Plus the fact that the value it returns on my system is the correct color, converted to Hex or in Decimal, means that the function is working properly.
- 12:38 AM Ticket #2289 (PixelGetColor - output options) updated by
- It doesn't return the decimal number I'd expect. I.e. I have a variable set to 0x0A1B22, which is then converted to 662306. The number that function will spit out by default when encountering that color is not that number. So in order to use PixelGetColor, I had to wrap the output. So the output of that function is never usable in a sensical manner, prior to using another function on it.
Dec 7, 2012:
- 8:38 PM Ticket #2289 (PixelGetColor - output options) updated by
- I'm not understanding the problem with it returning just the decimal number. Doesn't this do what you're looking for, where the second messagebox shows the 6 digit Hex number? […] Or even simpler, just automatically convert it to hex as you call it. […]
- 7:54 PM Ticket #2290 (String functions fails on a file) closed by
- No Bug: Please be serious with bug reporting next time.
- 12:40 PM Ticket #2290 (String functions fails on a file) updated by
- Epic fail. Seems like I have made tons of mistakes that I believed there was a bug. Sorry, you can close this.
- 12:39 PM Ticket #2289 (PixelGetColor - output options) updated by
- Fixed typo in GUICtrlCreateCombo.
- 12:33 PM Ticket #2290 (String functions fails on a file) updated by
- There is only one instance of _singleton in that file (using the latest from June '12) and you need to set the flag option to 1 if you want the return value of StringSplit to be 2 (or in your case 3.) As far as I can tell this isn't a bug.
- 11:25 AM Ticket #2290 (String functions fails on a file) created by
- I wanted to replace a simple string on the file …
- 7:59 AM Ticket #2289 (PixelGetColor - output options) created by
- The current decimal output has to be converted to Hex using said …
- 4:35 AM Ticket #2288 (Duplicated _WinAPI_OpenProcess) updated by
- Oh, I see. Thanks for the clarification.
Dec 6, 2012:
- 8:01 PM Ticket #2288 (Duplicated _WinAPI_OpenProcess) updated by
- duplication are just to include big library for just a function
- 6:34 PM Ticket #2288 (Duplicated _WinAPI_OpenProcess) closed by
- No Bug: Yes. However, former is function for internal use and not meant to be used outside Memory.au3. No bug, just weird logic.
- 2:56 PM Ticket #2288 (Duplicated _WinAPI_OpenProcess) created by
- Hi Mem_OpenProcess function in Memory.au3 and _WinAPI_OpenProcess …
Dec 5, 2012:
- 6:48 PM Ticket #2287 (GUICtrlSetState($controlID, $GUI_ONTOP) Doesn't set on top) closed by
- No Bug: $GUI_ONTOP does what it's docummented that it does. There is no bug here. Documentation says that control will get to the top of z-order. By default if the control is on top, it's the closest to the parent window (GUI) and it's therefore covered by all other controls being lower down the z-order. On the other hand, for example, if the GUI would have WS_EX_COMPOSITED ex-style, you would see different effect (also docummented).
Note:
See TracTimeline
for information about the timeline view.
