Re: [perl-win32-gui-users] Win32::FileOp Erro with Win32::GUI

[ramy]

Dear Steve,

Thanks first for your prompt reply.

After some investigation of removing the modules from the script, 
I found out that the main source of the error come from Win32::API module

Since the Win32::FileOp Which uses the Win32::API therefore it generates the 
error

That means a big loose for me and everyone that can not use Win32::API module
and all modules based on using it to load and interface to windows with threads
as it makes life easier with loading dll's.

I am not sure if WIn32::API is actively updated or not as this may be a little 
bug in it

Regards
Ramy
  ----- Original Message ----- 
  From: Steve Pick 
  To: [EMAIL PROTECTED] ; perl-win32-gui-users@lists.sourceforge.net 
  Sent: Sunday, January 25, 2004 3:03 AM
  Subject: Re: [perl-win32-gui-users] Win32::FileOp Erro with Win32::GUI


  Hi Ramy,

  Could you verify that Win32::GUI is causing this by testing without GUI code 
running. Create an application that uses threads and Win32::FileOp without 
Win32::GUI loaded and see if the problem still occurs. If so, it's out of our 
hands and is a fault in Win32::FileOp. A lot of modules are not 
threads-compatible, and it's probable that Win32::FileOp is one of them.

  If it only happens with Win32::GUI loaded, please let us know and we'll 
undoubtable jump at the chance to look into it, such a powerhouse of activity 
that we are.

  Thanks,

  Steve
    ----- Original Message ----- 
    From: [EMAIL PROTECTED] 
    To: perl-win32-gui-users@lists.sourceforge.net 
    Sent: Saturday, January 24, 2004 10:24 PM
    Subject: [perl-win32-gui-users] Win32::FileOp Erro with Win32::GUI


    Hi All,

    I noticed that when I use the module Win32::FileOp
    in a GUI application (may be also not gui) in a Threads,
    When the threads starts, the script shows error
    that says :

    The instruction at "0x28053f9a" referenced memory at "0x000010c0". The 
memory ould not be "read".
    Click on OK to terminate the program
    Click on CANCEL to debug the program

    and sometimes it is The memory ould not be "Written" instead of "read".

    I actually found that if I use the module "Win32::API" it will generate
    this error and of course Win32::FileOp use internally this module.

    The threads works fine if I remove the "use Win32::FileOp;" line but
    I need to use it for the File Open and Save Dialogs.

    Any solutions or suggestions?

    Thank you in advance for help

    Ramy