Latest Beta

[Valik]

Ok, I worked around the keywords problem by splitting the keywords into two files: au3.keywords.properties and au3.keywords2.properties, then adding the extra import line in au3.properties. I'm guessing there's a character limit somewhere ~60000.

I definitely can confirm this. I use my own version of the file which is slightly different than the provided version. Mine also stops at exactly 60,000 characters. For me that falls right in the special keyword #Alternate. If I enter #Alte it is highlighted because the break ends right after that.

This may not be fixed in time for the next beta because it's going going to take something clever to solve in a way that doesn't just delay the problem again.

[wraithdu]

Cool.

Oh, I also tried to reopen my Trac ticket #1026, but could not. I think it was fixed opposite to what I intended. Here would have been my response:

I think maybe you misunderstood my original post. The correct resource disposal function for all _GDIPlus_BitmapCreate* functions is _GDIPlus_BitmapDispose(), with the exception of _GDIPlus_BitmapCreateHBITMAPFromBitmap(). That is the only function which should use _WinAPI_DeleteObject(). Using _WinAPI_DeleteObject() on the other functions will return failure.

[trancexx]

Besides that, manifest res is missing from the AutoIt3.exe - beta.

[wraithdu]

Yikes, and a good number of the GDIPlus return values are wrong. For those functions that return True/False, it should be 'Return $aResult[0] = 0'. Many of them are just using 'Return $aResult[0]'.

[trancexx]

Yikes, and a good number of the GDIPlus return values are wrong. For those functions that return True/False, it should be 'Return $aResult[0] = 0'. Many of them are just using 'Return $aResult[0]'.

Gdip returns Status.

[wraithdu]

@trancexx

Exactly. So to return True, it needs to use 'Return $aResult[0] = 0', since Status 'Ok' = 0.

[Valik]

Yikes, and a good number of the GDIPlus return values are wrong. For those functions that return True/False, it should be 'Return $aResult[0] = 0'. Many of them are just using 'Return $aResult[0]'.

This is not a bug. Properly written code will not know the difference between True, 1, 100, -1, 0xDEADBEEF or False and 0. Also, the BOOL and boolean DllCall() types *should* cast the return value to True or False implicitly and if they don't then those two new types need changed so that they do (I'll have to check the code, I didn't write it). That would make it a moot point anyway.

Edit: Oh. Well fuck.

Edit 2: Why are the manifests missing!? When I build AutoIt in my developmentenvironment it has a manifest. But the clean build I did for therelease doesn't have a manifest!?

I'll fix both problems tomorrow and do another release. For the time being I don't recommend upgrading to 3.3.1.2.

Edited October 15, 2009 by Valik

[AdmiralAlkex]

@Valik

Good update. I like that you have finally decided to do more code-breaking changes, which I believe will lead to better functions, and a better language. I actually look forward to update my scripts and hope you will continue to bring new useful changes, even if it's mean sacrificing compatibility with old code.

People that doesn't like it when updates break their scripts shouldn't update in the first way.

[trancexx]

Hex("0x1234")

That is crashing beta for me on XP SP3.

[UEZ]

The executables are now smaller. Trend was in every version that the exe getting bigger!

Hex("0x1234") is crashing on Vista x32, too!

UEZ

[wraithdu]

If you feel like updating documentation for the new release today, there's those few issues I mentioned above, and _Crypt_EnryptData() is misspelled in the help file as well.

[ProgAndy]

Some tests on XP SP3:

;                                               STABLE     BETA 3.3.1.2
ConsoleWrite( Hex("1234") & @CRLF)           ;  000004D2   crash
ConsoleWrite( Hex("0x1234") & @CRLF)         ;  00001234   crash
ConsoleWrite( Hex(Binary("0x1234")) & @CRLF) ;      1234       1234
ConsoleWrite( Hex(Binary("1234")) & @CRLF)   ;  31323334   31323334
ConsoleWrite( Hex( 1234 ) & @CRLF)           ;  000004D2   000004D2
ConsoleWrite( Hex( 0x1234 )  & @CRLF)        ;  00001234   00001234

//Edit: In Beta, you should try every line in a new Script or the tests after the crash won't run.

It seems that it is a bug with the internal typecasting of AutoIt in this func.

Edited October 15, 2009 by ProgAndy

[monoceres]

Posted fixes for Crypt.au3 in original thread.

The problem with the combobox for EncryptFile is an autoit bug I believe (?) so I did not change it.

[UEZ]

Here Progandy's example ran (beta) on Windows2003 Standard x64:

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "E:\AU3\Test01.au3" /autoit3dir "C:\Program Files (x86)\AutoIt3\beta" /UserParams

+>16:08:06 Starting AutoIt3Wrapper v.2.0.0.0 Environment(Language:0409 Keyboard:00000407 OS:WIN_2003/Service Pack 2 CPU:X64)

>Running AU3Check (1.54.17.0) from:C:\Program Files (x86)\AutoIt3\beta

+>16:08:06 AU3Check ended.rc:0

>Running:(3.3.1.2):C:\Program Files (x86)\AutoIt3\beta\autoit3.exe "E:\AU3\Test01.au3"

!>16:08:09 AutoIT3.exe ended.rc:-1073741819

+>16:08:10 AutoIt3Wrapper Finished

>Exit code: -1073741819 Time: 4.391

UEZ

[wraithdu]

The problem with the combobox for EncryptFile is an autoit bug I believe (?) so I did not change it.

I just figured out the problem with the combo box is because of the missing manifest. I added the manifest from beta 3.3.1.1 to AutoIt3.exe of 3.3.1.2 and the control works properly and has the correct Win7 style.

@monoceres

Where is the original thread for Crypt.au3 with the fixes?

Edited October 15, 2009 by wraithdu

[wraithdu]

@monoceres

Also, with your Crypt functions and AES:

- what mode is used? (ECB, CBC, CBF, OBF, CTR)

- is it possible to specify an initialization vector?

[monoceres]

I just figured out the problem with the combo box is because of the missing manifest. I added the manifest from beta 3.3.1.1 to AutoIt3.exe of 3.3.1.2 and the control works properly and has the correct Win7 style.

Good.

@monoceres

Where is the original thread for Crypt.au3 with the fixes?

In a private subforum (the post was so Valik could find it).

@monoceres

Also, with your Crypt functions and AES:

- what mode is used? (ECB, CBC, CBF, OBF, CTR)

- is it possible to specify an initialization vector?

I have no idea.

The entire UDF is built upon this api provided by windows. I'm sure the default value for what you're talking about is specified there somewhere.

[Valik]

Guys, crashing bugs and things that are very obviously bugs need reported on the issue tracker. This is getting to be a bit too much to track here on the forum. This thread is for discussion, not bug reporting.

Cool.

Oh,I also tried to reopen my Trac ticket #1026, but couldnot. I think it was fixed opposite to what I intended. Here wouldhave been my response:

Just because youcannot reopen the ticket yourself does not mean you shouldn't post inthe ticket. Post your text to the ticket and I'll reopen it.

The executables are now smaller. Trend was in every version that the exe getting bigger!

Don't put any stock in that. I am not Jon. This release is missing the manifest file (unintentional and obviously a bug), intentionally missing the digital signature (I don't have the files to sign it) and does not have profile guided optimizations (something I believe Jon uses). Edited October 15, 2009 by Valik

[Yashied]

@Valik

I agree with you that you got rid of all _WinAPI_Check() functions. Maybe it's better than a "drag" them.

Edited October 15, 2009 by Yashied

[wraithdu]

@Valik

Posted, thanks.