#2251 closed Feature Request (Rejected)
variables in FileInstall's "source"
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Milestone: | Component: | AutoIt | |
Version: | Severity: | None | |
Keywords: | FileInstall variables | Cc: |
Description
As far as I can see in issue #768, it should be possible to use variables in FileInstall's "source" if I upgrade to version 3.3.0
I have downloaded AutoIt 3.3.8.1 and SciTe using "autoit full installation" at http://www.autoitscript.com/site/autoit/downloads, and after seing the "cut down version" of SciTe, I downloaded SciTe v 3.3.9.0 using SciTE4AutoIt3.exe at http://www.autoitscript.com/site/autoit-script-editor/downloads.
I installed it on my Windows XP SP2, being local administrator, but when opening SciTE it shows "SciTE Version 3.2.0, Jun 9 2012 00:35:28 by Neil Hodgson"
And I can't use this:
Global $_sSource = "MyNewTool" Global $_sTarget = "C:\ITD\Setup.exe" Global $_bStatus $_bStatus = FileInstall("C:\Temp\" & $_sSource & "\Setup.exe",$_sTarget,1)
Attachments (0)
Change History (9)
comment:1 Changed 12 years ago by TicketCleanup
- Version Other deleted
comment:2 follow-up: ↓ 3 Changed 12 years ago by Valik
- Resolution set to Rejected
- Status changed from new to closed
You're not very smart. So many examples of that. Please go away.
comment:3 in reply to: ↑ 2 Changed 12 years ago by TrywareDk
Replying to Valik:
You're not very smart. So many examples of that. Please go away.
Hi Valik
I actually did a lot search of the FileInstall issue, and couldn't find any solution, but only a lot of promises from you 4 years ago that it's about to be resolved according to among other #47, #220 and #768.
So I decided to raise a feature request about it.
I'm not satisfied with the way you answer me, because I think that you should have told me, that I forgot to read [www.autoitscript.com/trac/autoit/wiki/AutoItNotOnToDoList] before raising new feature request, instead of using the "language" you did.
BTW: Please understand that I'm a very satisfied user of AutoIt for many many years
Sincerely
- Malmgren
IT-Programmer
Denmark
[www.tryware.dk]
comment:4 Changed 12 years ago by Valik
What FileInstall() issue? The only issue with FileInstall() are the idiots who think the compiler can somehow resolve variables that aren't going to receive input until runtime. If you bothered to comprehend (the most important part of reading) all of those tickets you linked to then you would see that yes, while I did allude to a FileInstall() rewrite that never materialized, I also explicitly stated that variables as source parameters would not be implemented.
Here, I'll make this easy. If you can tell me what file the compiler should include in the resulting binary for the following example script I'll implement the feature immediately.
$sInput = FileOpenDialog(...) FileInstall($sInput, "C:\Somewhere")
comment:5 follow-ups: ↓ 6 ↓ 7 Changed 12 years ago by anonymous
Hi Valik
Sorry that I've offended you, but I really only wanted some support, and I don't believe I'm one of the idiots.
My wish is not to let the enduser select a file using FileOpenDialog(), but that I should be able to use a variable like e.g.
$sFile = @ScriptDir & "\MyTest.exe" FileInstall($sFile,"C:\Somewhere")
But as you already have told, this is NOT possible according to [www.autoitscript.com/trac/autoit/wiki/AutoItNotOnToDoList]
So I am aware, that this issue is 100% totally rejected and closed.
Have a nice day ;O)
Sincerely
- Malmgren
IT-Programmer
Denmark
[www.tryware.dk]
comment:6 in reply to: ↑ 5 Changed 12 years ago by anonymous
Replying to anonymous:
Hi Valik
Sorry that I've offended you, but I really only wanted some support, and I don't believe I'm one of the idiots.
My wish is not to let the enduser select a file using FileOpenDialog(), but that I should be able to use a variable like e.g.
$sFile = @ScriptDir & "\MyTest.exe" FileInstall($sFile,"C:\Somewhere",1)But as you already have told, this is NOT possible according to [www.autoitscript.com/trac/autoit/wiki/AutoItNotOnToDoList]
So I am aware, that this issue is 100% totally rejected and closed.
Have a nice day ;O)
Sincerely
- Malmgren
IT-Programmer
Denmark
[www.tryware.dk]
comment:7 in reply to: ↑ 5 Changed 12 years ago by Valik
Replying to anonymous:
Hi Valik
Sorry that I've offended you, but I really only wanted some support, and I don't believe I'm one of the idiots.
Lolwut? Offend me? It's cute that you think you're capable of that. Hint: You aren't.
You're not helping the "I'm not an idiot" case, though, when you want support on the issue tracker. It's kind of one of the guidelines that the issue tracker is not for support.
My wish is not to let the enduser select a file using FileOpenDialog(), but that I should be able to use a variable like e.g.
I'm perfectly aware of what you want. That does not change anything, however. The compiler is not an interpreter. It cannot evaluate your simple statement any more than it can evaluate my complex statement.
So what you really want is for FileInstall() to have different syntax entirely so that compile-time statements can be expanded without abusing the variable mechanism since that is entirely inappropriate. It almost sounds like I've thought about this, doesn't it?
comment:8 follow-up: ↓ 9 Changed 6 years ago by mark.pt@…
For me it sounds like you can't imagine a concept like, I don't know... freaking static value pre evaluation.
Please don't make excused for the last of knowledge or skills (maybe both) mister Mr. I'm not an idiot.
comment:9 in reply to: ↑ 8 Changed 6 years ago by Jos
Replying to mark.pt@…:
For me it sounds like you can't imagine a concept like, I don't know... freaking static value pre evaluation.
Please don't make excused for the last of knowledge or skills (maybe both) mister Mr. I'm not an idiot.
... and you felt the need to make this reply to an 6 years old close ticket ....why?
Jos
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.
Automatic ticket cleanup.