Jump to content

v3.0.103 Unstable - Reloaded


Recommended Posts

  • Developers

I didn't, thanks :)

Does that also fix the problem of drive mapping an already mapped drive failing?  Maybe I should just force a drivemapdel before a drivemapadd is performed.

<{POST_SNAPBACK}>

This fixes the scenario where you use DriveMapDel to remove a Map for a driveletter and then try to remap the same driveletter with DriveMapAdd. (Like Trids script does)

I don't understand the issue you describe, because I though the DriveAddMap should fail with error 3 if the DriveLetter is already mapped to another Share?

3 = The device is already assigned

Edited by JdeB

SciTE4AutoIt3 Full installer Download page   - Beta files       Read before posting     How to post scriptsource   Forum etiquette  Forum Rules 
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Link to post
Share on other sites
  • Replies 220
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

  • Administrators

I don't understand the issue you describe, because I though the DriveAddMap should fail with error 3 if the DriveLetter is already mapped to another Share?

I know, I realised that after I wrote it... :">
Link to post
Share on other sites
  • Administrators

http://www.autoitscript.com/autoit3/files/unstable/autoit

Updated:

- GUI updown controls notify

- DriveMapDel fixed

- InetGet doesn't use as much CPU

- New "client" mode added to PixelCoordMode, MouseCoordMode, CaretCoordMode

Link to post
Share on other sites

Hi

Thanks Jon for great job, i have think for a long time before posting in this part of forum

But i have seen that your last update work arount inetget instruction

And i have always the same problem with a expected timeout option like explain in my post of september

sorry for my bad english

My post : My post

Can you do something around that ?

Thx.

Link to post
Share on other sites
  • Administrators

Updated:

- Au3spy saves settings (win positions, modes, highlight colour, etc)

- Registry keys changed around

Au3spy/aut2exe will only save their settings to the registry if run on a machine that has AutoIt fully installed (uses keys created by the installer to check). If AutoIt is not installed then no settings are saved (making it safe to run these files on servers or machine that you don't want to tattoo the registry of).

If you run the installer and select "upgrade" (rather than "clean") then you'll have to delete the old registry keys manually (if you care that is :) )

They are:

HKLM\Software\Hiddensoft\AutoIt3\

HKCU\Software\Hiddensoft\AutoIt3\

Link to post
Share on other sites
  • Administrators

Thanks.

@Jon: It means that paths like: #include <UDF.au3>, are affected?

Right?

Should be fine if you used the installer. Just tried a couple of scripts here and they all include guiconstants.au3.
Link to post
Share on other sites

Jon, the compiler needs update with the registry key used in resolving #include's.

Edit: It also appears the compiler isn't looking in the proper location for the InstallDir key as I just received an error where the compiler couldn't find GuiConstants.au3. Adding the Hiddensoft key back in fixed the problem.

Edited by Valik
Link to post
Share on other sites
  • Administrators

Jon, the compiler needs update with the registry key used in resolving #include's.

Edit: It also appears the compiler isn't looking in the proper location for the InstallDir key as I just received an error where the compiler couldn't find GuiConstants.au3.  Adding the Hiddensoft key back in fixed the problem.

Bollocks, I forgot the compiler used the include code.
Link to post
Share on other sites

Did you get a chance to fix the compiler error if fileinstall is used inside a #cs - #ce block?

EDIT: Have you also had a little time to look over my posts here:

http://www.autoitscript.com/forum/index.php?showtopic=5897

http://www.autoitscript.com/forum/index.php?showtopic=5894

Edited by this-is-me
Who else would I be?
Link to post
Share on other sites
  • Administrators

Did you get a chance to fix the compiler error if fileinstall is used inside a #cs  - #ce block?

EDIT: Have you also had a little time to look over my posts here:

http://www.autoitscript.com/forum/index.php?showtopic=5897

http://www.autoitscript.com/forum/index.php?showtopic=5894

#cs #ce It's not a quick fix so might not get done anytime soon. Use ; to workaround

Includes: Files are combined and included waay before autoit ever sees them so there is no easy way to do it.

Move thing, yeah maybe. I think someone submitted something similar for filecopy, but I'm trying to get a consistant way of handling all blocking functions without reinventing the wheel for each function (like I did with inetget) so it goes to the bottom of the todo list.

Link to post
Share on other sites
  • Administrators

Updated:

http://www.autoitscript.com/autoit3/files/unstable/autoit/

- Added WinList()

- Fixed FileSelectFolder so it can return computernames

- Fixed odd bug when calling exit functions from Gui Events

WinList:

Note, to make this function I messed around a lot with the general "title", "text" type code - please make sure I've not wrecked all the normal Win... and Control... commands!

New title option of "all" is now valid for WinTitleMatchMode=4 (it just matches all titles)

$result = WinList( ["title" [,"text"]] )

Returns an array of the MATCHING windows. If no title/text is given then all top level windows are listed. No parameters in this function is equivalent to:

Opt("WinTitleMatchMode", 4)

$result = WinList("all")

The result is a 2-D array containing the titles and window handles of the matched windows. In true AutoIt style element [0][0] is the number of windows

$result[0][0] = number of windows

$result[1][0] = first window title

$result[1][1] = first window handle

$result[2][0] = second window title

$result[2][1] = second window handle

And so on.

Here is an example that gets a list of all windows:

$var = WinList()

For $i = 1 to $var[0][0]
; Only display visble windows that have a title
  If $var[$i][0] <> "" AND IsVisible($var[$i][1]) Then
    MsgBox(0, "Details", "Title=" & $var[$i][0] & @LF & "Handle=" & $var[$i][1])
  EndIf
Next

Func IsVisible($handle)
  If BitAnd( WinGetState($handle), 2 ) Then 
    Return 1
  Else
    Return 0
  EndIf

EndFunc

Here is an example that gets a list of all windows of the "Notepad" class:

Opt("WinTitleMatchMode", 4)
$var = WinList("classname=Notepad")

For $i = 1 to $var[0][0]
; Only display visble windows that have a title
  If $var[$i][0] <> "" AND IsVisible($var[$i][1]) Then
    MsgBox(0, "Details", "Title=" & $var[$i][0] & @LF & "Handle=" & $var[$i][1])
  EndIf
Next

Func IsVisible($handle)
  If BitAnd( WinGetState($handle), 2 ) Then 
    Return 1
  Else
    Return 0
  EndIf

EndFunc

If you remove the IsVisible check you'll notice that there are 100s of invisible/titleless windows present on the system - something to watch out for.

I'll document it properly this week when you've confirmed it's working/useful.

Edited by Jon
Link to post
Share on other sites
  • Administrators

Great!

A question. You said:

(I assume you didn't forget any words, sentences...)

Does that mean only visible windows are saved in the array?

All windows are listed, even invisible and titleless windows. It is the user's responsibility to decide what to do with them.
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...