218 replies to this topic

[Chimaera]

sorry all the same thing to me
yes from the exe details 3.3.6.1

[BrewManNH]

Why was the heading for Encryption Management changed to Crypt Management? It seems to be obscuring the function reference. Actually, it makes it sound a little gruesome.

[guinness]

This is down to how the files are generated.

[Zedna]

#Include <Crypt.au3>

is there a list in this section anywhere of the possible encyption types?
ie $CALG_RC4 etc etc

I couldn't find that in helpfile too in almost latest beta (3.3.7.18).
Finally I found all these algoritms in sources of Crypt UDF.

[Richard Robertson]

The name change is most likely for accuracy sake. If the file were named encryption but decrypted too, that would be wrong. If it is name crypt, that includes both directions.

[BrewManNH]

The name change is most likely for accuracy sake. If the file were named encryption but decrypted too, that would be wrong. If it is name crypt, that includes both directions.

Except that Encryption Management would make most people think of encrypting both ways, while Crypt Management would make it harder to find if you're looking for encryption help, even to decrypt. Just my thoughts on the matter, it doesn't affect me either way, just was curious as to why it was changed and changed to what it was changed to.

[RichardL]

_IsPressed
Check if key has been pressed

I think _IsPressed is an instantaneous test whether a key is pressed, not test if it has been pressed. So "has been" should say "is". (or change the function to _HasBeenPressed())

Richard

[Mat]

Technically "pressed" is the key being pushed down, so a key is 'pressed', 'held' and 'depressed'. Ofc in english I think you would actually calling the pushing down bit 'depressed'...

But you are right that it is misleading. It is far easier to say "is currently pressed". Or even just "is pressed"

To go by msdn: "Determines whether a key is up or down at the time the function is called"

Edited by Mat, 16 November 2011 - 11:04 PM.

[czardas]

How about if the key is pressed during the execution of the script? You could argue that, at the time of writing the script, it should be _WillBePressed. Trying to map English syntax onto a scripting language is going to get kind of messy, however you do it, IMO.

Functions beginning with _Is (or Is) return 1 or 0 (True or False respectively). This gives the language a certain degree of consistancy. The coder knows what results to expect since the syntax follows a logical and familiar pattern.

Edited by czardas, 16 November 2011 - 11:44 PM.

[Valik]

You could argue that, at the time of writing the script, it should be _WillBePressed. Trying to map English syntax onto a scripting language is going to get kind of messy, however you do it, IMO.

You could argue that but you'd look pretty silly. That would mean when the code is executing it would read in English terms that it wants to detect a keystroke in the future. That doesn't make any sense. Remember, when you are writing code your frame of reference for time is always the present. The present is defined in coding terms as time of execution, not time of authoring. Therefore _WillBePressed() does not make sense in the context of detecting something that is happening at execution time. With that in mind it is not hard for anybody who understands the basics of tense in English to write functions named correctly with reference to time.

[czardas]

It was intended as an illustration of a stupid function name, and I see the syntax as being clear as it is (the way you decribe it).

[jchd]

We should warn in help file that Binary() shouldn't be used with strings and recommend use of StringToBinary() instead, so that the user decides by himself which encoding should be represented in the binary result.

Binary($str) behaves like StringToBinary($str), that is converts the string to ANSI first. The issue is that if $str contains characters which don't have an equivalence in the current ANSI codepage, they are silently replaced by '?', which is certainly not what users expect.

My ISP doesn't allow me to connect to the repository (filtering on protocol I guess). Hence I'm unable to do anything there.

[AdmiralAlkex]

My ISP doesn't allow me to connect to the repository (filtering on protocol I guess). Hence I'm unable to do anything there.

But we connect through https, surely your isp can't mess with that. How do you do your banking, buying stuff online or even read your webmail?

[jchd]

I can't say what happens exactly, it's hard to say where it fails. https is no problem, except using svn on this repository and another one as well (PCRe which should work fine). I don't use webmail but banking, buying etc runs fine.
I'm forced to use cooperative puclic hotspot, authenticating via a 3G access, but direct 3G would cost me a leg and 3 arms a day.

[JohnOne]

_INetGetSource

#include <INet.au3>
_INetGetSource ( $s_URL ) <- Does not mention optional parameter.

Parameters
$s_URL (The URL of the site.) eg 'www.autoitscript.com'
$bString [optional] If True the data is returned in string format, otherwise binary format.

Return Value
<- Has no return info

Remarks
None.

seems to be missing info.

Edited by JohnOne, 23 November 2011 - 09:44 PM.

[guinness]

Fixed. Thanks.

[BrewManNH]

Would we use this thread to report errors in the Beta help file? Because I found an error in the 3.3.7.22 beta help file and wasn't sure where to post it.

In the remarks for the Number function - "If input value after conversation fits 32bit" that should be conversion.

[trancexx]

Yeah, others saw that too.
It's my English.

[131738]

New functions have no income documentation

Edited by 131738, 09 December 2011 - 08:13 AM.

[trancexx]

New functions have no income documentation

They have, only not where it should be. Will be fine for the next version.
"Search" (the help file) too see them.

Edited by trancexx, 09 December 2011 - 10:50 AM.