Jump to content
Spiff59

What happened to "Compile with Options"?

Recommended Posts

Spiff59

When I right-click on an autoit source file, I no longer get the "Compile with Options" choice in the Windows Explore context menu. "Compile" is there, but not "Compile with Options". It seems to have gone away when I installed beta 3.3.1.1?

Edited by Spiff59

Share this post


Link to post
Share on other sites
Spiff59

No luck (I did reboot too)

Share this post


Link to post
Share on other sites
Richard Robertson

Did you install the full SciTE after updating?

Share this post


Link to post
Share on other sites
Spiff59

Did you install the full SciTE after updating?

You mean re-install the full Scite after installing the beta Autoit?

No, I hadn't thought that necessary.

I've tried it now, a reinstall of Scite 1.7.8 doesn't bring my option back.

This is the dope:

Installing Autoit Beta 3.3.1.1 trashes "Compile with options" from the explorer context menu, only re-installing the production 3.3.0.0. version, after the beta install, brings it back.

I don't doubt a proper registry patch would have done it as well, I likely mangled up the example offered to me.

So I'm good for now, but in the future I may have to reinstall the prod version everytime I install a beta in order to keep one of my favorite autoit "shortcuts" available.

Share this post


Link to post
Share on other sites
GEOSoft

For future reference the Reg hack is

$sCmd = '"C:\Program Files\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper_Gui.exe" /in "%l"'
RegWrite("HKCR\AutoIt3Script\Shell\Compile with Options\Command", "", "REG_SZ", $sCmd)

The path for $sCmd may be different on your system.


George

Question about decompiling code? Read the decompiling FAQ and don't bother posting the question in the forums.

Be sure to read and follow the forum rules. -AKA the AutoIt Reading and Comprehension Skills test.***

The PCRE (Regular Expression) ToolKit for AutoIT - (Updated Oct 20, 2011 ver:3.0.1.13) - Please update your current version before filing any bug reports. The installer now includes both 32 and 64 bit versions. No change in version number.

Visit my Blog .. currently not active but it will soon be resplendent with news and views. Also please remove any links you may have to my website. it is soon to be closed and replaced with something else.

"Old age and treachery will always overcome youth and skill!"

Share this post


Link to post
Share on other sites
Jos

You mean re-install the full Scite after installing the beta Autoit?

No, I hadn't thought that necessary.

I've tried it now, a reinstall of Scite 1.7.8 doesn't bring my option back.

This is the dope:

Installing Autoit Beta 3.3.1.1 trashes "Compile with options" from the explorer context menu, only re-installing the production 3.3.0.0. version, after the beta install, brings it back.

I don't doubt a proper registry patch would have done it as well, I likely mangled up the example offered to me.

So I'm good for now, but in the future I may have to reinstall the prod version everytime I install a beta in order to keep one of my favorite autoit "shortcuts" available.

This needs to be looked at. The AutoIt3 installer shouldn't mess up this AutoIt3Wrapper_GUI option.

Jos


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
Jos

This needs to be looked at. The AutoIt3 installer shouldn't mess up this AutoIt3Wrapper_GUI option.

Jos

Seems that this registry entry is the reason:

"HKEY_CLASSES_ROOT\.au3" "Default" is set to "AutoIt3ScriptBeta" which causes "HKEY_CLASSES_ROOT\AutoIt3ScriptBeta" to be used in stead of "HKEY_CLASSES_ROOT\AutoIt3Script"

This should not be happening because that means that Beta becomes the default when installed.

Jos


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
Spiff59

Seems that this registry entry is the reason:

"HKEY_CLASSES_ROOT\.au3" "Default" is set to "AutoIt3ScriptBeta" which causes "HKEY_CLASSES_ROOT\AutoIt3ScriptBeta" to be used in stead of "HKEY_CLASSES_ROOT\AutoIt3Script"

This should not be happening because that means that Beta becomes the default when installed.

Jos

Are you pursuing this Jos? Or, should I initiate a BugTrac referencing this thread?

Thanks.

Share this post


Link to post
Share on other sites
Jos

Are you pursuing this Jos? Or, should I initiate a BugTrac referencing this thread?

Thanks.

I will take it up with the other devs. Was hoping they would see this post and chime in here :)

If this behaviuour is really what is wanted then I will also add the "Compile with Options" to the Beta Reg Hive to make it the same.

Either way works for me.

Jos

Edited by Jos

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
Jos

I have added the shortcuts for "Tidy" and "Compile with options" also to the "AutoIt3ScriptBeta" Hive to resolve this issue.

Next SciTE4AutoIt3 installer release will have this fix.


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
Spiff59

Thank you for the fix.

I don't suppose making the explorer contect menu options user-selectable, maybe via global options, would be a simple task?

Share this post


Link to post
Share on other sites
Jos

Thank you for the fix.

I don't suppose making the explorer contect menu options user-selectable, maybe via global options, would be a simple task?

As an addition to SciTEConfig would not be hard to do.

Is that what you mean?

Jos

Edited by Jos

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
Spiff59

Well, just some simple method (other than manual registry changes0 where a user could tailor the explorer context menu for .au3 files to thier tastes.

Hmm, I'm getting an idea now, and one that would require for me to do most the work, not you!

Has anyone ever built a slick little GUI to display the Scite configs, like global options? It could present the data in logical sections, limit the input of invalid values, display descriptions for the parameters. Anyway...

The fix you've put in will negate the necessity of me reinstalling the production version everytime I update the beta.

So my initial problem is fixed.

Share this post


Link to post
Share on other sites
Jos

Hmm, I'm getting an idea now, and one that would require for me to do most the work, not you!

Has anyone ever built a slick little GUI to display the Scite configs, like global options? It could present the data in logical sections, limit the input of invalid values, display descriptions for the parameters. Anyway...

I call that GUI SciteConfig. It enables you to make all the needed changes.

See if you can add it to that. I have no issue adding your modification to the distributed version.

The fix you've put in will negate the necessity of me reinstalling the production version everytime I update the beta.

So my initial problem is fixed.

This is all you need to fix it at this moment:

$SciTEAutoIt3Dir = RegRead("HKCR\AutoIt3ScriptBeta\Shell\Edit\Command","")
RegWrite("HKCR\AutoIt3ScriptBeta\Shell\Tidy\Command","","REG_SZ",StringReplace($SciTEAutoIt3Dir,"SciTE.exe","Tidy\Tidy.exe"))
RegWrite("HKCR\AutoIt3ScriptBeta\Shell\Compile with Options\Command","","REG_SZ",StringReplace($SciTEAutoIt3Dir,'SciTE.exe"','AutoIt3Wrapper\AutoIt3Wrapper_Gui.exe" /beta /in'))

Jos :)

Edited by Jos

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
Spiff59

I call that GUI SciteConfig. It enables you to make all the needed changes.

See if you can add it to that. I have no issue adding your modification to the distributed version.

Jos :)

Maybe something along the line of this attachment?

(there is no handling for the new checkboxes, nor any of the necessary registry reads/writes, nor any update of the version number)

Edit: The fonts settings on the second tab works nicely, now when you modify them, you get a live on-screen display of the change.

Edit2: It looks like the 2 columns of checkboxes are unnecessary. As I'd only display the settings for whatever definition file was current.

SciteConfigBeta.au3

Edited by Spiff59

Share this post


Link to post
Share on other sites
Spiff59

I updated the attachment on the prior post.

I added a field that I think is useful, one that lets the user know what file they are editing regardless of the tab they are viewing.

I cut the context menu checkboxes back to one column. There is room to put the 6 context options in a 3-row by 2-column format which would free up space on the main tab. Maybe you've some options you've been wanting to add to the first tab? Otherwise, the 6-row format above fills up the first tab well enough.

I could stick in a few lines to do direct, live registry reads and writes and make it work.

But I'm not sure if that is all that you would want.

Whether or not the changes need to be logged somehow, or the settings stored ias part of a configuration scheme, I don't know.

Share this post


Link to post
Share on other sites
Spiff59

Jos, I'd seen your prior post prior to the reversion of the forum software caused it to be lost.

(by the way, I replaced the prior attachment again. Bumping the tab size to 455 vertically made the spacing around the buttons at the bottom more consistant and allowed some adjustments on the second tab to make it look a little less crowded).

Regarding your prior post, this is what I had replied:

To be honest, I have zero knowledge of the two different installers and how they interact with SciTE. At this point, I only have limited familiarity of the SciTEConfig program. I am not incapable of figuring this all out, but I believe it would be very time-consuming. If any of the easily-done GUI changes I've made can provide the groundwork for a next version of SciTEConfig, then I'd be happy to have saved you some of the development time. I think I'll leave my suggestions in your hands and let you decide which, if any, are desirable.

Thank you very much for your time.

Share this post


Link to post
Share on other sites
Jos

Jos, I'd seen your prior post prior to the reversion of the forum software caused it to be lost.

(by the way, I replaced the prior attachment again. Bumping the tab size to 455 vertically made the spacing around the buttons at the bottom more consistant and allowed some adjustments on the second tab to make it look a little less crowded).

Regarding your prior post, this is what I had replied:

I have read your reply. thanks :)

This was the text of my post. (had it prepared in SciTE as the forum went down while replying so still have it.)

Had a look and like the design changes you made.

Just a couple of observations:

  • The SciTE4AutoIt3 installer only sets the "Compile with Options" and "Tidy", the other options are set by the AutoIt3 Installer.
  • I am not clear, once the code for the reg handling is put in, how it all will work. Currently both installers will just add all these context entry back into the registry ignoring any settings that might have been made. Only way I would see this working when we make our own separate hive next to "AutoIt3Script" and "AutoIt3ScriptBeta" and maintain that. This would totally ignore any context entries made by the 2 installer, but I am unclear what the gain would be doing it that way.
  • Saw one Cut&Paste mistake in the current code:

Will you have a look at the code needed for the Reg handling too or you want me to have a go at that?

Thanks

Jos


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
Spiff59

$H_Context_Edit = GUICtrlCreateCheckbox("", $BaseX + 180, $BaseY + 99, 17, 17)

Yep, that be a cut-and-paste boo boo. It would have revealed it self real quick had I gone the next step and started processing the new checkboxes and making the registry changes. I look forward to seeing what you eventually do with the next revision of SciTEConfig.

Share this post


Link to post
Share on other sites
Spiff59

Was it decided that a beta install done after a production install should override the default settings?

I just installed beta 3.3.1.4 and it like previous betas trashed my "Compile with Options" and "Tidy" options in explorer.

I've reinstalled 3.3.0.0 to get them back.

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

×