Custom Query

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (70 - 72 of 3856)

Ticket Resolution Summary Owner Reporter
#2378 Fixed BITMAPV4HEADER and BITMAPV5HEADER Structures incorrect guinness Ascend4nt@…
Description

In the <WinAPIGdi.au3> header the definitions for BITMAPV4HEADER and BITMAPV5HEADER are incorrect.

For bV4Endpoints and bV5Endpoints, the structure lists these as an array of 3 ints. What it should be really is an array of 9 ints for both.

The relevant links which show the structures: BITMAPV4HEADER http://msdn.microsoft.com/en-us/library/windows/desktop/dd183380%28v=vs.85%29.aspx BITMAPV5HEADER http://msdn.microsoft.com/en-us/library/windows/desktop/dd183381%28v=vs.85%29.aspx

CIEXYZTRIPLE http://msdn.microsoft.com/en-us/library/windows/desktop/dd371833%28v=vs.85%29.aspx CIEXYZ http://msdn.microsoft.com/en-us/library/windows/desktop/dd371828%28v=vs.85%29.aspx FXPT2DOT30 No official link on this, but the Windows API has this defined as long in the <WinGDI.h> header:

typedef long            FXPT2DOT30, FAR *LPFXPT2DOT30;

So basically the EndPoints member type is 3 structures of 3 longs, so those arrays needs to be [9].

#856 Completed _StringAddThousandsSep() prefixes some #'s with , Ascendant
Description

During testing, this UDF sometimes puts a ',' at the beginning of a number which isn't correct. For example, the below results in -,123,456,789,012,345.67890:

#include <String.au3>
MsgBox(16,"_StringAddThousandsSep() faulty reult", _
	"Result of _StringAddThousandsSep('-123456789012345.67890'): "& _
	_StringAddThousandsSep('-123456789012345.67890'))

_DebugBugReportEnv() Result:

Environment = 3.3.0.0 under WIN_XP/Service Pack 3 X86

#876 Rejected @error passthrough on 'Return' statements Ascendant
Description

It would be nice to be able to use 'Return MyFunction()' to both return the values from that function *and* the @error/@extended codes. It looks ridiculous, and is probably wasteful to change the below code:

Func _ReturnErr()
    Return SetError(1,0,1)
EndFunc

Func _ReturnReturnErr()
    Return _ReturnErr()
EndFunc

_ReturnReturnErr()
If @error Then ConsoleWrite("Error returned correctly"&@CRLF)

to this code:

Func _ReturnErr()
    Return SetError(1,0,1)
EndFunc

Func _ReturnReturnErr()
    ; Wasteful temporary storage
    $tempVal=_ReturnErr()
    ; This looks ridiculous, setting @error to @error:
    If @error Then SetError(@error,@extended)
    Return $tempVal
EndFunc

_ReturnReturnErr()
If @error Then ConsoleWrite("Error returned correctly"&@CRLF)

I recognize that there is function 'localization', but I believe that 'Return FunctionName()' makes more sense to return the value AND the @error\@extended code information. It would save extra work and make more sense in the end.

Actually, even better - I recommend a new keyword - something like 'ReturnWithSubError', which will take the last @error + @extended codes returned by a called function and return them as the @error/@extended values.

This will prevent breaking old code, and make code clearer, easier, and more sensible. Code with SetError(@error) looks (and is) ridiculous, in my opinion. (Sorry, don't mean to offend)

Note: See TracQuery for help on using queries.