Sign in to follow this  
Followers 0
JLC123

Download now or wait for stable version?

Just looking for opinions   40 members have voted

  1. 1. Just looking for opinions

    • Yes, download now
      36
    • No, wait
      4

Please sign in or register to vote in this poll.

11 posts in this topic

#1 ·  Posted (edited)

I haven't downloaded the Beta version yet because I don't want my codes to break once the stable version is released. Good idea? Silly to wait? Probably silly to post this in this forum since everyone here obviously has the beta version, but what the heck. Tell me what you think anyway. :)

Thanks!

Edited by JLC123

Two wrongs don't make a right, but three lefts do

Share this post


Link to post
Share on other sites



I'm not patient at all ... gotta have the newest as soon as its out

Damn the script rewrites ... full speed ahead :)


We have enough youth. How about a fountain of SMART?

Share this post


Link to post
Share on other sites

I can't help myself. I always download the current beta, only burned once and since then keep a -1 copy around. This tool with its Scite enhancements is way too valuable to not use every feature you can. AutoIt3 is the Swiss army knife of utilities.

:)

Share this post


Link to post
Share on other sites

I can't help myself.  I always download the current beta, only burned once and since then keep a -1 copy around.  This tool with its Scite enhancements is way too valuable to not use every feature you can.  AutoIt3 is the Swiss army knife of utilities.

:)

<{POST_SNAPBACK}>

Its as easy to have the latest stable release installed with the installer and have a seperate directory for the current unstable.

In SciTE you just add these to the SciteUser.properties so Alt+F5= run unstable and Alt+F7 = Compile unstable. Alt+F1 for the unstable helpfile. (this needs to be renamed to autoitbeta.chm)

Beta_Autoit3dir=D:\winutil\AutoIt3\au3beta
command.21.*.au3=$(Beta_Autoit3dir)\autoit3.exe /ErrorStdOut "$(FilePath)"
command.name.21.*.au3=Run Debug 
command.save.before.21.*.au3=1
command.shortcut.21.*.au3=Alt+F5
command.22.*.au3=$(Beta_Autoit3dir)\aut2exe.exe /in "$(FilePath)"
command.name.22.*.au3=Compile Debug
command.save.before.22.*.au3=1
command.shortcut.22.*.au3=Alt+F7
command.24.*.au3=$(CurrentWord)!$(Beta_Autoit3dir)\autoitbeta.chm
command.name.24.*.au3=Debug Help
command.subsystem.24.*.au3=4
command.shortcut.24.*.au3=Alt+F1
command.save.before.24.*.au3=2

Visit the SciTE4AutoIt3 Download page for the latest versions  - Beta files                                How to post scriptsource        Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

I've waited long enough for buttons and tabs!!!

I'm in on the beta so keep it coming!!!

Share this post


Link to post
Share on other sites

I am for downloading and using ALWAYS the lastest.

Ok, I had to remake Run! from Zero for the new GUI sintax... but how can you say NO to new power?

Share this post


Link to post
Share on other sites

I am for downloading and using ALWAYS the lastest.

Ok, I had to remake Run! from Zero for the new GUI sintax... but how can you say NO to new power?

<{POST_SNAPBACK}>

Well, that's excatly what's holding me back. I used a beta for MultiShrink but now that I'm aiming at a multi language version where you can switch between english and german at the click of a button and a few other settings I'll prolly better wait so I do not have to rewrite the whole interface yet again.

Is a final scheduled yet?


MultiMakeMKV: batch processing for MakeMKV (Win)MultiShrink: batch processing for DVD ShrinkOffizieller Übersetzer von DVD Shrink deutsch

Share this post


Link to post
Share on other sites

Well I had voted to wait but I just downloaded and am using the Beta as of last week. I needed the DLL Call function for a script, so I didn't have much choice. I hope my other scripts continue to function properly.

:idiot:


Share this post


Link to post
Share on other sites

I also program in an obscure language called Libery Basic. Recently I received a programming assignment at work that I wrote in LB with an AutoIt engine that wrapped into a 1.4 Meg application - I replaced the whole thing with an AutoIt GUI ap in 144 K. Since this ap will be used at some remote sites with ISDN as their "broadband", the 144 K ap is the winner - and so is AutoIt GUI. I'm moving ahead with the Beta!


Anyone have a TRS 80 Model III for sale?

Share this post


Link to post
Share on other sites

Didn't someone make a script that could automatically "convert" a script

from the old GUI-names to new GUI-names ?

I'm planning to update a program that I'm making, and for that I

need one of the newer releases (I'm currently using one of the September-

releases, I think..), and it would be great if I didn't had to rewrite the

source (over 1200 lines :idiot: ) manually..

- Helge

Share this post


Link to post
Share on other sites

#11 ·  Posted (edited)

Didn't someone make a script that could automatically "convert" a script

from the old GUI-names to new GUI-names ?

<{POST_SNAPBACK}>

There is this, but I should stress it only works for simple scripts :idiot: Lots of nested parentheses can confuse it; and you sometimes need to manually clean up some leftover GuiWrite and AutoItSetOptions.....

Once regular expression searching gets implemented, the conversion script could be rewritten...

Edit: fix typos

Edited by CyberSlug

Use Mozilla | Take a look at My Disorganized AutoIt stuff | Very very old: AutoBuilder 11 Jan 2005 prototype I need to update my sig!

Share this post


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
Sign in to follow this  
Followers 0