Modify

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#1244 closed Feature Request (Rejected)

New AU3Wrapper directive: #AutoIt3Wrapper_MinVersion

Reported by: danielkza Owned by: Jos
Milestone: Component: SciTE4AutoIt
Version: Severity: None
Keywords: scite4autoit au3wrapper autoit3wrapper Cc: danielkza2@…

Description

I'm trying to use the currently available directive (#AutoIt3Wrapper_Version) to force my script to always run on the 3.3.1.x Beta, since it uses new features.

Setting it to 'B' is not very helpful, unfortunately: I still have to manually select 'Beta Run' and 'Beta Compile' for it to work, and it will stop making much sense when 3.3.2.0 is released.

So I thought maybe there is a better way: I could specify a minimum working version, and AU3Wrapper could check if it needs to use the beta or not.

For instance, the following code:

#AutoIt3Wrapper_MinVersion=3.3.1.0

would work like that in the following scenarios:

1)Prod: 3.3.0.0, Beta: 3.3.1.3

  • Run/compile using the Beta version;

2)Prod: 3.3.2.0, Beta: none

  • Run/compile using the Prod version;

3)Prod: 3.3.0.0, Beta: none

  • Show a warning to the user, asking whether to continue running or not. If not stopped, run using Prod.

If neither Prod nor Beta are new enough, there are two possible solutions: always run the production version, or use the most recent one. Maybe the choice can be included in the warning prompt.

I wrote code for it already (too much free time), but it doesn't look very nice or polished. If it can help you guys in any way (or speed things up), I can post it.

Thank you for the attention.

Attachments (0)

Change History (4)

comment:1 in reply to: ↑ description Changed 10 years ago by Jos

Replying to danielkza:

Setting it to 'B' is not very helpful, unfortunately: I still have to manually select 'Beta Run' and 'Beta Compile' for it to work, and it will stop making much sense when 3.3.2.0 is released.

I don't understand what you mean by manually select? How do you run/compile your scripts?
I always do F5 to run Prod and Alt+F5 to run the latest Beta.

Jos

comment:2 Changed 10 years ago by danielkza

Not all my scripts require the Beta: I find myself running with the wrong version a lot. It would be much more useful when running scripts from others, since you would not need to guess whether you need the Beta or Prod.

The issue I have with it is that what makes a script work or fail are the new features used: they'll be in beta for a while, but not forever, and when that change happens, things will break, and they should not.

For instance, if I only install final releases (which is the 'default' behavior for most people), I may have a compatible version, but my script will try to run with a Beta I may or may not have: that doesn't sound right to me.

comment:3 Changed 10 years ago by Jos

  • Resolution set to Rejected
  • Status changed from new to closed

Don't think you answered my question about "How do you run/compile your scripts"
Anyways: I have no intentions to create anything more complex than what I have today that works for 99.99% of the population. :)

Jos

comment:4 Changed 10 years ago by danielkza

I run them with F5, that's my default behavior, because most of my scripts don't need Beta versions. But the problem shows up when you're using/editing other people scripts.

If that makes any diff, my implementation added ~35 lines only.

Thanks anyway.

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Modify Ticket

Action
as closed The owner will remain Jos.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.