Cusem Posted July 25, 2009 Share Posted July 25, 2009 Not sure if I'm in the right forum, with questions regarding SciTE, can't think of a better forum though (developer chat maybe?). I wrote a project opener, which opens all most recents versions of modules of a project. It also opens AutoIT Help and the AutoIT Forums. I'm using AutoIT v3.3.0.0 and SciTE 1.76. Usually If I click F1 in SciTE, not only the help will open up, but the script will also run (like pressing F5). If I Click Help -> Help F1 this isn't the case and Help launches. In my project opener I used the following code to open the AutoIT Help WinMenuSelectItem("[CLASS:SciTEWindow]", "Source", "&Help", "&Help F1") But now the opened script also runs. So If I open the helpfile with the following code, the script that is opened in SciTE also runs (like pressing F5). Anybody any idea's how to combat this? Link to comment Share on other sites More sharing options...
Cusem Posted July 25, 2009 Author Share Posted July 25, 2009 After I compiled the script, the problem doesn't occur anymore. Link to comment Share on other sites More sharing options...
amokoura Posted July 25, 2009 Share Posted July 25, 2009 I've had the same problem sometimes. I recall there was a unfixable bug in Scite that caused the behaviour. There were some threads about the problem also. Link to comment Share on other sites More sharing options...
Developers Jos Posted July 25, 2009 Developers Share Posted July 25, 2009 This is indeed a know issue in SciTE. When you press F5 to run a script and while that is still running you do F1, it will also do again an F5. This is due to the design of the JobQueue in SciTE and haven't seen anybody working on it at the SciTE Interest Site lately to fix that. Jos SciTE4AutoIt3 Full installer Download page - Beta files Read before posting How to post scriptsource Forum etiquette Forum Rules Live for the present, Dream of the future, Learn from the past. Link to comment Share on other sites More sharing options...
Cusem Posted July 25, 2009 Author Share Posted July 25, 2009 Ok, thanks! Doesn't matter that much since fortunately the compiled version of the script opener doesn't trigger this bug. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now