Timeline
12/27/12:
- 11:48 Ticket #2296 (SHA2 for Crypt.au3) created by
- see here: http://autoit.de/index.php?page=Thread&threadID=35302 …
12/24/12:
- 11:32 Ticket #2295 (Help on ObjGet) created by
- I had to add an empty function, to make example two work, in the help …
12/23/12:
- 08:49 Ticket #2294 (ControlGetText failing when window title happens to contain umlauts) closed by
- No Bug: Your error is of semantic nature considering this works: […]
- 05:47 Ticket #2294 (ControlGetText failing when window title happens to contain umlauts) created by
- Sample: $Aktiivne_Suund = ControlGetText($MAINWIN,"Piiriületus", …
12/22/12:
- 10:30 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.
12/18/12:
12/17/12:
- 18:36 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 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 / …
12/15/12:
- 19:13 Ticket #2291 (AutoIt causes memory leak?) closed by
- Works For Me: Sorry, I see no leakage.
12/14/12:
- 08:29 Ticket #2291 (AutoIt causes memory leak?) created by
- Hey guys, im writing on my project and got some memory leaks. Actual …
12/08/12:
12/07/12:
- 19:54 Ticket #2290 (String functions fails on a file) closed by
- No Bug: Please be serious with bug reporting next time.
- 11:25 Ticket #2290 (String functions fails on a file) created by
- I wanted to replace a simple string on the file …
- 07:59 Ticket #2289 (PixelGetColor - output options) created by
- The current decimal output has to be converted to Hex using said …
12/06/12:
- 18:34 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.
- 14:56 Ticket #2288 (Duplicated _WinAPI_OpenProcess) created by
- Hi Mem_OpenProcess function in Memory.au3 and _WinAPI_OpenProcess …
12/05/12:
- 18:48 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).
11/29/12:
- 11:32 Ticket #2287 (GUICtrlSetState($controlID, $GUI_ONTOP) Doesn't set on top) created by
- GUICtrlSetState($controlID, $GUI_ONTOP) Doesn't set the control on top …
Note: See TracTimeline
for information about the timeline view.
