[monoceres]

Just to clarify, static will not be in the next stable, correct?

[Valik]

Correct. You won't see Static again until next year.

[MvGulik]

Any change #65 'Au3Check gives wrong error with Const ByRef params' will make it into the next final?

[Valik]

No.

[Anteaus]

weaponx, on 20 May 2009 - 08:05 PM, said:

- Added #837: FileFindNextFile() set @extended if a directory is returned.
Brilliant! Eliminates the need for calling FileGetAttrib when searching for files.

Just a suggestion for the team, as it stands the @extended flag treats junctions as directories. It might be better if it either treated junctions as NOT directories, or else set a different @extended value for junctions. That would make things a lot easier for Vista/7 users faced with those damn cyclic links inside profiles.

As things stand the only sure way to avoid endless loops in profile copy/backup ops is to perform a DLL call for each directory.

[Valik]

I think that is well beyond the scope of what FileFindNextFile() should do.

[andygo]

hello, just downloaded the beta 3.3.1.5

if i try to download a file with inetget directly to d:\ the autoit crashes:

!>00:09:01 AutoIT3.exe ended.rc:-1073741571

if i choose a subfolder, everything is fine.

[ code='text' ]    ( Popup )

Problemsignatur:
  Problemereignisname:  APPCRASH
  Anwendungsname:   dvbs549.01beta.exe
  Anwendungsversion:    3.3.1.5
  Anwendungszeitstempel:    4af35031
  Fehlermodulname:  ntdll.dll
  Fehlermodulversion:   6.1.7600.16385
  Fehlermodulzeitstempel:   4a5bdb3b
  Ausnahmecode: c00000fd
  Ausnahmeoffset:   0002dece
  Betriebsystemversion: 6.1.7600.2.0.0.256.1
  Gebietsschema-ID: 1031
  Zusatzinformation 1:  cedc
  Zusatzinformation 2:  cedcabbd28669fd1230baace347c517c
  Zusatzinformation 3:  3b57
  Zusatzinformation 4:  3b5764752c946160ec172e9bb3b8b707

This post has been edited by andygo: 14 November 2009 - 12:06 PM

[Anteaus]

Valik, on 13 November 2009 - 08:06 PM, said:

I think that is well beyond the scope of what FileFindNextFile() should do.

I agree, FileFindNextFile() in a scripting context should be a straightforward way to parse a directory. The issue is that if it parses into junctions as well as ordinary folders then from this point on, things cease to be simple.

As far as the default Vista/7 junctions are concerned there is no point in parsing them, and attempting to do so may lead to trouble.

The only case where someone might want their script to parse through junctions is if they've created some of their own, perhaps to other partitions. In my experience (do others agree?) this is a very rare situation, though.

Therefore I suggest that the default behaviour should be to NOT parse into junctions -or that it should be possible to identify from @extended when this is about to happen. Whichever is easier.

If it's not practical then I take your point, however I think it would be a very worthwhile improvement.

[Valik]

Anteaus, on 15 November 2009 - 03:16 PM, said:

The only case where someone might want their script to parse through junctions is if they've created some of their own, perhaps to other partitions. In my experience (do others agree?) this is a very rare situation, though.

All my Windows XP systems have cross-volume junctions. :: shrugs ::

Quote

Therefore I suggest that the default behaviour should be to NOT parse into junctions -or that it should be possible to identify from @extended when this is about to happen. Whichever is easier.

It's not about ease, it's about doing what's sensible. You're suggesting we add overhead to every invocation to test for a rare scenario that will affect less than 1% of all users.

[Jon]

To be fair, Vista and later have a junction within the user profile that turns into a cyclic spiral when you try and keep going down a level. So don't be too quick to write off working with junctions.

And it's something like local appdata and not something massively obscure ;(

Not saying it's needed in the command in this topic, but it's quite a nasty problem when it bites and it's not expected.

[Michel Claveau]

Hi!

Jon, on 15 November 2009 - 09:58 PM, said:

Vista and later have a junction

Junctions exists since W2K (but more used with Vista & 7)

[Valik]

Michel Claveau, on 17 November 2009 - 04:03 PM, said:

Hi!



Junctions exists since W2K (but more used with Vista & 7)

We know. Jon's point is that Vista and later have a junction in the profile.