Help pls.

[holmes]

I've installed today v6.0

Whenever I try to add action "file open or file run" to a button, I get a message pop-up saying: Unexpected symbol near ???

How can I overcome this ?

Thnks in advance

[TJ_Tigger]

Can you post the code that you have on the button?

[holmes]

Can you post the code that you have on the button?


File.Open("AutoPlay\\Docs\\dreamsuite_4.", , SW_SHOWNORMAL);

[Eagle]

Hi, this one is from the related action help file example:

File.Open("AutoPlay\\Docs\\readme.txt", "", SW_SHOWNORMAL);

so its should be just a syntax thing, have a look at the "" above
and compare with your posted syntax.

also check your file path..the file extension seems a little odd.

without any change to the file extension, try below now:

File.Open("AutoPlay\\Docs\\dreamsuite_4.", "", SW_SHOWNORMAL);

hope helps.

[holmes]

Thnks Eagle for your reply.

It helped in file open, but not in file run.

Why this is happening? The code is created by the app itself when we browse to a file and select it.

I had no problems with previous version.

I'm runing Xp + Sp2

Please do reply.

[Eagle]

Yes, now I understand what you mean..this appears to be bug in AMS60,

unless the 'Args' and Working folder' parameters are manually selected,
it does not create the default "" in these parameters, which causes the
error message.

Untill this is fixed, when selecting these types of actions, just click
once in each of the above mentioned 'parameter', as this triggers
the correct creation of the "" when the action has been created.

I have placed a reference to this link in the Feedback Section for IR

[Eagle]

here is an example syntax for File.Run:

File.Run("AutoPlay\\Docs\\myfile.ext", "", "", SW_NORMAL, false); --no wait

File.Run("AutoPlay\\Docs\\myfile.ext", "", "", SW_NORMAL, true); --wait

hth keep you going for now

(the bug report link)

http://www.indigorose.com/forums/showthread.php?t=12986

[Eagle]

Ooops, make that

File.Run("AutoPlay\\Docs\\myfile.ext", "", "", SW_SHOWNORMAL, false); --no wait

File.Run("AutoPlay\\Docs\\myfile.ext", "", "", SW_SHOWNORMAL, true); --wait


btw: another workaround is when the action has been created and added
into the script window, just double click the action and this will fix it also.

[holmes]

Thnks once again Eagle. Hope this will be fixed soon. I'll be watching the forum.

[Eagle]

noproblemo

[hjortsune]

Seems to be the same problem with File.RunOnReboot and Shell.CreateShortcut....

[holmes]

Seems to be the same problem with File.RunOnReboot and Shell.CreateShortcut....


You are right. Apart from this, the App keeps freezing when some commands are executed. I really don't understand what the Beta testers have done, but I will uninstall this version and return to the previous one. :huh

For sure I'll not buy it now.

[Tek]

holmes,

Try not to judge a product based on a few bugs you have found. I am a software tester and I can say from experience with IR software that they are quick to log a bug when it is found and it is not usually long before a service release is available to fix the problem.

A viable workaround has been provided so it's only a matter of time before you can use this action without any problems.

You will not find a comparable product on the market today that can compete with AMS 6.0. There will always be some bugs in a new major version of any software and usually most severe bugs have already been found and fixed before the release.

I think all IR software is wonderful to work with and I'm glad our company decided to implement IR software with our software rollout plans.

[Corey]

Hi, a couple thoughts from someone who has used *a lot* of software. On the "professional developer tool" level it's impossible to produce "100% bug free" software in a commercial context. No company has ever done that. Every piece of commercial developer software you currently own contains at least one bug. Microsoft, Adobe, Borland, Sun, NASA, IBM, Macromedia and Oracle all have never released a "100% bug free" commercial developer tool...

What we have achieved is a very high level of functionality with a minimum of problems, this is the best any developer can hope to do. AutoPlay Media Studio is as solid, on a feature-by-feature basis, as any comparable software on the market today was in its first week of release.

Eagle has presented a simple workaround which will give you the exact functionality you need until a fix is released. This particular bug is insignificant in terms of completing a project today.

We don't claim our software is "100% bug free" nor do any other software companies as far as I know. But if you view our track record, you'll see that we do a great job of releasing fixes for reported bugs in a timely and efficient fashion. That's the best any developer can be expected to do. We're definitely "as good or better than" any comparable team in our sector in that regard.

When compared to the alternatives, AutoPlay Media Studio 6.0 is an extremely good package with a ton of features and some of the best product support in our industry. It's a heck of a value for the price, and allows you to do quite a few things which no other software does. :) :yes

[Intrigued]

You are right. Apart from this, the App keeps freezing when some commands are executed. I really don't understand what the Beta testers have done, but I will uninstall this version and return to the previous one. :huh

For sure I'll not buy it now.

One thing I have found with concerns to Indigo Rose's software and support services. They WILL get it fixed if that is the outcome of a situation!

Remember, AMS 6.0 just came out.... and what Corey is, for what's it's worth, right on the money.

Hiccups will happen... but it's how a company handles such that you should be focusing on.

AMS 6 = a very nice platform that has strong roots in AMS 5 (for those new to the Autoplay Media Studio line of I.R. products).

I would have paid for AMS 6 even if I had not received a copy from I.R. for helping in the beta testing stage. Because I know they care and it shows in everything I have seen them put forth, done.

Sincerely,

[Brett]

Thanks for the bug report. It will be fixed for the next service release.

REF: 11056