Help File/Documentation Issues. (Discussion Only)

[mLipok 1,389]

13 hours ago, TheXman said:

Just a small typo.

In the Remarks section of the #OnAutoItStartRegister topic in the help file (chm and web), you will see the word "Dlobal".

Thanks for reporting.

btw.
This has already been fixed on March 23, 2018
 

[TheXman 637]

1 hour ago, mLipok said:

This has already been fixed on March 23, 2018

Thanks @mLipok. 

I searched the forum for "dlobal" to see if it had already been reported and found no results.  Since I rarely use betas, I didn't think to look at the latest beta's help file.    I do see that the beta help file has the correction.  If I come across any more help file issues, I'll make sure to check the beta first. 

[JockoDundee 634]

35 minutes ago, Anisha said:

Please check it:

Help page entitled “_GDIPlus_BitmapCreateFromMemory” returns as expected.

Should I run the function thru a comprehensive stress test in my function simulator and compare the output to the help page, or do you want to indicate what the specific problem is?

[oliviakaylie 0]

None of the Array functions work on anything more than a 2D array, no point in using multiD array as a description, it would cause much more confusion than clarity.

[mLipok 1,389]

Your statement is not clear.

Please be more specific and say exactly what you mean ... with example.

Edited June 18, 2021 by mLipok

[mLipok 1,389]

20 hours ago, oliviakaylie said:

None of the Array functions work on anything more than a 2D array, no point in using multiD array as a description, it would cause much more confusion than clarity.

I'm still not sure what exactly you mean.

I can only say that in:
https://www.autoitscript.com/autoit3/files/beta/autoit/docs/keywords/Dim.htm

"Example 1" was recently changed to:

; Declaring variables
Local $i, $j = 23, $k
Global $g_fPI = 3.14159, $g_iRADIUS
Local $iDaysWorking = 5

; Declaring arrays
Global $g_aChessBoard[8][8]
Global $g_aEmptyArray[0]
Global $g_aAutoSize[] = [1, 2, 3, 4]
Local $aStates[2], $aWindowsStats[4]
Local $a2Dimensions[2][3] = [[1, 2, 3], [4, 5, 6]]

; Declaring constant variables
Const $iX1 = 11, $iY1 = 23, $iZ1 = 55
Global Const $PI = 3.14159, $E = 2.71828
Local Const $DAYS_WORKING = 5

I'm not sure if the "Declaring arrays" section (in this mentioned current version ) is what you mean.

If not, just try to be more specific.

mLipok

 

[Jos 2,849]

4 minutes ago, mLipok said:

I'm still not sure what exactly you mean.

Just let it be for the moment as my current guess is you won't ever get an answer and maybe even that the post will suddenly vanish., so just wait n see what happens.  

[mLipok 1,389]

description for this following macros

@LogonDNSDomain	Logon DNS Domain.
@LogonDomain	Logon Domain.
@LogonServer	Logon server.

they are not very informative.

Can anyone propse a better description?

Edited July 1, 2021 by mLipok

[argumentum 959]

..the names are self describing. If you know what it is then use it, else, get acquainted with the concepts, as a better description would have to be educational and not a one liner.  

[seadoggie01 302]

The example in VarGetType calls the Double a Float ($fFloat) and includes an extra line for hWnd, even though it returns a Ptr.

Also, the tabs make the data come out mis-aligned, but that might just be me.

[mLipok 1,389]

In description for:
 

IsAdmin()

there is :
 

Quote

Return Value

Success:

1 if the current user has administrator privileges.

IMHO this statement is not accurate.
Because you can run for example an compiled script as a specific not current user.
I mean current user (logged into a Windows) it is not always the same as the user who started the program.

Does this description need a correction ?

What you think about ?
 

Edited August 15, 2021 by mLipok

[argumentum 959]

Linguistic interpretations.
Say you RunAs another user. The current user for the program, is the user the program runs under. That is the current user at the time for that program.
The help statement is accurate, unless you find better wording. I can not think of better wording at this time. As is, is good.
Maybe add a reference to RunAs() ?, as to hint the reader that a current user could be any user, even SYSTEM. 

[Skysnake 95]

How about something "as the running user" would that be too vague but concerning enough?

[Skysnake 95]

The problem is that I cannot get the SetCueBanner to display on EditBoxes 

This example is from the help file, and only slightly modified.

@Melba23's research indicates it cannot be done.

 

A one line addition to the Help File

Windows documentation indicates that it is not possible to set Cue text on multiline controls.

Yes?

 

 

 

[Melba23 3,799]

Skysnake,

Suitable text added to Help file.

M23

[mLipok 1,389]

Does for GUICreate() function Helpfile says nothing about width and height default values, or I'm blind ?
Can somebody explain and propose some description to this parameters default values ?

[mLipok 1,389]

I'm not EN native speaker but want to ask if here: https://www.autoitscript.com/autoit3/docs/script_breaking_changes.htm

Quote

 has been addaptedto fit W3C Colors.

Do there should be an additional space? And not duplicated "d" ?
I mean "adapted to" instead "addaptedto"
Google translates both forms `addaptedto` and `adapted to` as well.

btw. 
There is one more lack of space

Quote

MDGRAY,MONEYGREEN 

 

Edited March 7, 2022 by mLipok

[Jon 1,251]

Should be “adapted to”

[mLipok 1,389]

14 hours ago, Jon said:

Should be “adapted to”

Fixed on SVN

[mLipok 1,389]

I have a question about: _WinAPI_GetProcessWindowStation()
In this descripion what mean "station" in what sens "window station" it is ?
Is this simply handle to the main window of the process ?

_WinAPI_GetProcessWindowStation

Retrieves a handle to the current window station for the calling process

#include <WinAPISys.au3>
_WinAPI_GetProcessWindowStation ( )