Jump to content
Sign in to follow this  
Jos

New SciTE4AutoIt3 available with SciTE v3.3.7

Recommended Posts

I think there is a problem with SciTe.

When i'll do compile, the UPX flag is not checked, right? If i make "Save script" there is no change to the script.

If i'll click on Compile and i'll add the flag to the UPX, then click on "Save script" nothing happened, no changes to the script.

In the second case, why SciTe don't add this line?

#AutoIt3Wrapper_UseUpx=yes

I'll remeber the old version add that line.


Nothing is so strong as gentleness. Nothing is so gentle as real strength

 

Share this post


Link to post
Share on other sites

You forgot to specify all version info you are using.

I just tried it on a script without any directives and it did add the UPX directive when I ticked it, but could very well be it got fixed in the current beta.

Jos

Share this post


Link to post
Share on other sites

I didn't specific because i can't check now but at 99% the last stable SciTe+3.3.8.1, if not i'll repost with more information.

Tested with the current download and can't replicate this. AutoIt3Wrapper v.2.1.4.4

Jos

Share this post


Link to post
Share on other sites

Share this post


Link to post
Share on other sites

Jos know best :sorcerer:

Yes my version was:

SciTe 13.11.14.16 - 3.3.6 - Wrapper 2.1.3.0

I have download the lastest version:

SciTe 41.01.22.21 - 3.3.7 - Wrapper 2.1.4.4

And i don't have that issue, when i thick the UPX i have the directive, sorry for the loosing of time.

Little OT question:

I'll respect your decision to leave out from the Obfuscator project, you know what I think about security of our script. Obfuscator don't make your script more secure but IMHO better then nothing/plain text. But why you don't have given the project in the hands of someone you trust within the forum instead of "let it die", there is a particular reason? Thanks 


Nothing is so strong as gentleness. Nothing is so gentle as real strength

 

Share this post


Link to post
Share on other sites

Little OT question:

I'll respect your decision to leave out from the Obfuscator project, you know what I think about security of our script. Obfuscator don't make your script more secure but IMHO better then nothing/plain text. But why you don't have given the project in the hands of someone you trust within the forum instead of "let it die", there is a particular reason? Thanks 

 

The project isn't dead but just took a turn and is now focussing on stripping the source to remove as much ballast as possible.

The Obfuscation of source isn't buying you much any more these days since there are deobfuscators available and will be more or less the same as using the new /RenameMinimum switch in Au3Stripper which is the  /OM switch of Obfuscator.

The opening up of the source is not open for discussion. If someone feels this project needs to continue, I would have no issue with explaining more of its internals, but this person will have to write its own program to make it maintainable.

Jos

Edited by Jos

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Similar Content

    • By AutoitMike
      Scite 3.4.4
      Win 10
      I click "Help" or press F1, there is no response
      If I use the file explorer and double click Autoit.chm or Autoit3.chm help opens.
      There is no dialog to check or uncheck "Always ask before opening this file" when clicking on these files.
       
      If you are curious as to why I dont have the latest version, I am creating a back up laptop that has a VERY extensive automation application that I have written over the past 15 years.
       
      An extremely potent, powerful, needed function has been deleted in the upgrade of Autoit in recent years that I can not do without. If my main laptop dies, which it almost did, I am in a very bad position. So I bought the exact same laptop and I am "cofiguring" it to work exactly the same as my main laptop. However, this one has been "Upgraded" to Win 10 which I hope is not the problem. 
      Thanks for any help
    • By Beege
      If you have every taken the time to set up a nice dark theme for your scite editor, you probably noticed shortly after a small yet really annoying flaw. For what ever reason, scite is not set up to let you change the caret fore color and caret line color per language. This really sucks if say you want to edit a properties file or any of the many other languages that Scite currently is setup to support. Pretty much all the other languages are set as light theme so unless you change the theme for those file types, you end up with something like below where the line color and caret are still using the dark theme colors. Line 3 in the pic:
       

       
      To get around this I came up with the following that seems to work pretty well.  
       
      Add the following properties to SciteUser.properties file (Options -> Open User Options File). Update colors to your own needs. You can addionally add any other propertys that dont have a lexer language option in the same fashion.
      # The default values (light themes) will be used for any lexer other than au3 caret.default.fore=#000000 caret.default.line.back=#FFFED8 selection.default.fore=#006000 selection.default.back=#F0A0A8 caret.au3.fore=#FFFFFF caret.au3.line.back=#111111 selection.au3.fore=#C2FFAE selection.au3.back=#f9f9f9  
      Add the following function to PersonalTools.Lua file. As jos pointed out, the OnStartup covers the filetab switches as well as the startup so only need the one function:
      function PersonalTools:OnStartup() -- the "and" + "or" keywords are ternary operators here local sLex = self:IsLexer(SCLEX_AU3) and 'au3' or 'default' props['caret.line.back'] = props['caret.' .. sLex .. '.line.back'] props['caret.fore'] = props['caret.' .. sLex .. '.fore'] props['selection.fore'] = props['selection.' .. sLex .. '.fore'] props['selection.back'] = props['selection.' .. sLex .. '.back'] end
      Last restart SciTE and that should be it. Let me know if you have any issues. Thanks
       
    • By ozymandius257
      Is there a way to remove the numbers from the tabs in Scite?
      When you have multiple autoit programs open, the tabs are numbered, so you'll get something like 1 ProgramA.au3    2 Program2.au3   3 Program3.au3
      I am working on programs with numbers as the first character, so I get  1 3-DoThis.au3     2 4-DoAnother.au3   3 5-DoTheRest.au3  (not the real program names, obviously :))
      It would be nice if I could get rid of the tab number, and just have the program name on each tab.
       
       
    • By SgtHugoStiglitz
      HI people,
                        I got a questions, I maintain code in autoIT and every time I compile a new version or modification, Scite generate 2 folders. One folder is finish by released and the other is tentative. I try to make some google search, but never find answer would satisfied myself. The dev who was maintain it before were using AutoIt3Wrapper_GUI, and I don't know if it's related. I look both folder, but they seem pretty identical, but I would like to know what it's the difference between those to folder. Anyone have a clue?
    • By user4157124
      ConsoleWrite('>Message here.' & @CRLF) outputs colored text (per + > - ! characters).
      ConsoleWrite('warning' & @TAB & '38' & @TAB & 'more text ...' & @CRLF) enables jump to line 38 on doubleclick.

      Using "jump to line" format, only red and pink text coloring seems possible (simply prefixing color directives to output-text disables jump to line functionality). Is it possible to combine the two (define custom color while keeping "jump to line" functionality)?
×
×
  • Create New...