Jump to content

pedrit0

Active Members
  • Posts

    22
  • Joined

  • Last visited

Profile Information

  • Location
    Paris, France

pedrit0's Achievements

Seeker

Seeker (1/7)

0

Reputation

  1. to be noted : when using that you must disable Au3Check before compilation... it won't like unexplicitely declared vars.
  2. I have just tried but the global vars declared in the library are not detected by the main script... but i think this a good clue and I try out all I can with that tomorrow. Tired. Going to bed. thx a lot for the time you have spent on the topic :-)
  3. :-) that would be heaven if I could. These functions are to be called from the main exe.
  4. yep but my issue remains : how to keep the library out ???
  5. Oh I get your misunderstanding... sorry. I have made up this system: - I have an ini file listing some steps of processings. Step# = FunctionName() - I have the main script parsing the ini file and executing the iniread as a function call in a loop, whatever the function is and whatever its name. So no need to know the function for the main script. - the function to be executed is stored in the functionlibrary.au3 - several persons need to update / add functions in the library without recompiling anything.
  6. What I mean is that I cannot pass trough using ini or xml files as a workaround. The goal is really to store some functions in the library.
  7. External functions that do not stick to the script own structure. These functions can be altered/modified without threatening the main script process. The vars are global vars that could be used by several scripts later.
  8. To be more specific, this library strictly contains var statements and functions. No processing.
  9. My only goal. For an IT project. The exe would run 'in production' on a server and its function library can be edited/updated without having to modify the main exe. Can you develop about ' shellexecute au3 source files' ? Sounds interesting but when I google it it seems not to fit exactly to what I need.
  10. Hi Jfish I have 2 files: - mainscript.au3 - FunctionLibrary.au3 that contains the functions to be used by mainscript I want to compile mainscript.au3 but not FunctionLibrary.au3 because i want to be able to modify it later without having to recompile the mainscript. I know this behavior is not possible with the #include method that would merge the library to the mainscript during compilation. Which means that the external library would become useless. So I am looking for another method.
  11. Hi all. I have created an external au3 (a library of functions and vars) that is #included in a main script that i must compile. I wish that the content of the library is not merged with the main script when compiling. My goal is to keep the ability to modify the library even after the main exe is compiled and that these changes are effective when executing the exe. I guess this is not possible using the standard #include method. Is there a way to do that ? thx a lot :-)
  12. Thx for the honest & detailed answer :-)
  13. As this UDF no longer lives, there is a recent initiative from Minxomat to implement advanced OOP in AutoIT.
  14. Hi Minxomat. It seems that you've made a great job and I am considering to use OOPE in a project I am currently working on. Before I can decide, I have some questions. Is the 0.3 version stable enough to use it for a software development ? Is it the relevent version to use: for example do you plan to add a killer-feature soon in a 0.4 or 0.5 version which would make it more interesting to wait for this new version ? What is the plan for staying compliant with the future versions of AutoIT ? Thx, and again, great job
  15. Rover, It works : thank u very much... U saved me I could not imagine such a solution. Big up to you skills on the gui part of AutoIT, you are the Pedrit0
×
×
  • Create New...