Timeline
Feb 6, 2021:
- 8:27 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) updated by
- Replying to Jpm: > Hi, > You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). > The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. > in specific case an extra delay of 10 is added when the focus is not at the right place > so there is not bug Actually, that's not the issue which I am addressing. I am very aware that MouseClickDelay does affect the delay AFTER the click, but not the delay DURING the click. The fact that the delay DURING the click cannot be changed for ControlClick is the issue itself, in other words the bug is not fixed, the MouseClickDownDelay still refuses to affect the delay DURING the click of ControlClick
- 8:25 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) updated by
- Replying to Jpm: > Hi, > You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). > The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. > in specific case an extra delay of 10 is added when the focus is not at the right place > so there is not bug
- 7:58 AM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) closed by
- No Bug: Hi, You right the Autoit code use Opt("MouseClickDownDelay",...) only for MouseClick(). The Opt("MouseclickDelay",...) is used in Mouse functions and also in the ControlClick to simultate the delay of the mouse displacement. in specific case an extra delay of 10 is added when the focus is not at the right place so there is not bug
Feb 4, 2021:
- 7:32 PM Ticket #3793 (Add project explorer and open folder options in scite) updated by
- This is a Plugin for Notepad++. I am using the standard SciTE.exe & SciLexer.dll published by Neil as a base. NotePad++ is also using SciLExer.dll for the Syntax Highlighting, but is a total different Editor. Jos
- 6:48 PM Ticket #3793 (Add project explorer and open folder options in scite) updated by
- I saw Notepad++ which uses the same text edit control as Scite have it: https://github.com/funap/npp-explorer-plugin Do by "standard option" you mean that you have not modified the source code of Scite itself for AutoIt and it's stock Scite with with simply AutoIt specific conf?
- 4:18 PM Ticket #3803 (ControlClick unaffected by MouseClickDownDelay) created by
- I recently opened up a post discussing how the "MouseClickDelay" …
Feb 3, 2021:
- 7:59 PM Ticket #3802 (Window is not activated by a partial title) closed by
- No Bug: This is not a support forum, so please visit our support forums for questions and only post here when you have a confirmed bug. Thanks, Jos
- 7:12 PM Ticket #3802 (Window is not activated by a partial title) created by
- A C# / .Net 5.0 console project. […] The output: […] Why …
- 8:49 AM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) updated by
- A simpler solution is to use the unique file identifier via GetFileInformationByHandle. It is Available in Windows XP.
Feb 2, 2021:
- 11:42 PM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) updated by
- Vista is older than Windows 7. I assume you meant Windows XP? The lowest Windows version the current AutoIt3 version supports is Windows XP. It is true that GetFinalPathNameByHandleA is not supported in Windows XP, however there is a way to get the same result on Windows XP: https://stackoverflow.com/questions/65170/how-to-get-name-associated-with-open-handle/5286888#5286888
- 10:35 AM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) closed by
- Wont Fix: Sorry to close this ticket as this function is only available starting Vista/Server 2008. We still want AutoIt to be used with Windows 7 …
Feb 1, 2021:
- 9:23 PM Ticket #3801 (AutoIt #include does not handle symlinks right if included file has ...) created by
- It would be nice if AutoIt used something like …
Jan 31, 2021:
- 5:28 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Replying to Ant: > Yes. They work fine when dropped into the SciTE4AutoIt set-up. > > No problem! It's just frustrating knowing the answer's out there. Thanks for persisting and for going to the trouble of accommodating earlier processors. :) Thanks for letting me know. :)
- 4:08 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Yes. They work fine when dropped into the SciTE4AutoIt set-up. No problem! It's just frustrating knowing the answer's out there. Thanks for persisting and for going to the trouble of accommodating earlier processors. :)
Jan 29, 2021:
- 2:37 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) closed by
- Fixed: Fixed by revision [12482] in version: 3.3.15.4
Jan 27, 2021:
- 3:05 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Think the easiest solution is going to be to build SciTE & ScilLexer with VC in stead on nmake for the time being, like we do with the lite version. I have made these now available in directory /ia32 and removed all other test compiles. Could you try those once more, and when working, will move them into the Beta so that will be the next standard for Production? Thanks for your testing! Jos
- 11:59 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
-
Not sure if it's any help, but I came across this predefined macro.
You may well know about it already. If not, it indicates at run time which
/archoption was set. Maybe it can be used to check whether the/arch:IA32option is actually being picked up by compiler. - 8:41 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Unfortunately, it didn't work with any of the set-ups. It was worth a shot, though. By the way, I tried the software on another almost identical machine, just to rule out some kind of glitch in my device / set-up. The same error occurred, albeit with a slightly different offset in the signature. Both machines are up-to-date (as much as they can be).
Jan 20, 2021:
- 8:31 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
-
Replying to Ant:
> Sadly, neither did the trick. Tried them in the beta, AutoIt3 and SciTE4AutoIt3 set-ups.
>
> So, to summarise:
> 1. the full version of ScITE fails,
> 2. the "lite" version runs fine, even though it uses the same project file as the full version, and
> 3. the full version runs fine when compiled under Visual Studio 2017 with the
<EnableEnhancedInstructionSet>option set toNoExtensions. > > The/arch:IA32compiler option seems to be the right one. A Visual Studio bug that causes SSE2 code to be generated unintentionally with that option is described here. > Thanks for your feedback. I had a look at that article and it does sound similar but I am not seeing that /fp: build flag so am not sure it is. To test, I changed the buildflags to: […] as they indicate that the second parameter shold be a tempory workaround. The result is stored in directory ia32/namkeia32. Could you try that set aswell? Thanks Jos - 7:33 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
-
Sadly, neither did the trick. Tried them in the beta, AutoIt3 and SciTE4AutoIt3 set-ups.
So, to summarise:
1. the full version of ScITE fails,
2. the "lite" version runs fine, even though it uses the same project file as the full version, and
3. the full version runs fine when compiled under Visual Studio 2017 with the
<EnableEnhancedInstructionSet>option set toNoExtensions. The/arch:IA32compiler option seems to be the right one. A Visual Studio bug that causes SSE2 code to be generated unintentionally with that option is described here.
Jan 14, 2021:
- 1:59 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- I have added 2 versions to the ia32 directory: maknono compiled mak file with: -DUSE_MSVC_SSE=OFF -DUSE_MSVC_SSE2=OFF makyesno compiled mak file with: -DUSE_MSVC_SSE=ON -DUSE_MSVC_SSE2=OFF Have a go and see if that solves anything... else I might have to consider doing the compile with Visual Studio instead of nmake.
Jan 13, 2021:
- 4:54 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Unfortunately, it doesn't. When dropped into each of the beta, AutoIt3 and SciTE4AutoIt3 set-ups, the original error occurs. I'm way out of my depth here, but could the desired command line options be as follows? […] In other words, use SSE (compatible with my machine) but don't use SSE2 (incompatible with my machine). Feel free to ignore me; this is an uninformed stab in the dark. If it exists, I can't find the on-line documentation for these options.
Jan 8, 2021:
- 8:04 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Ok, adding this in the vcxproj file does the trick then for the VC2017 build: […] Previously I added this to the standard scite.mak and scitilla.mak files but that doesn't seem to work: […] Found somewhere another option to try: […] .. and uploaded that to https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/ia32/mak/ Could you try that version for me to see if that fixes it? Jos
- 3:25 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Btw, thanks very much for that, mLipok. I only just spotted the new username.
- 3:15 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- We have progress. Having successfully installed the (2015) redistributable package, both the lite and the full versions of SciTE that you compiled with Visual Studio (in "comment9") open and seem to run fine when dropped into the beta set-up. So this means the recent Visual Studio SciTE compilations have something (that ensures compatibility with my device) that the published versions don't.
- 3:21 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Replying to Jos: > .....which I believe are standardly installed these days....... Unfortunately not. I have similar issue at my work, when we install some software on fully udpated Win10 Pro, then we must to especially install this following vcredist pack. @Ant Try to install those 3 following MS Visual C++ Redistributable package: vcredist_x86_2005.exe vcredist_x86_2008.exe vcredist_x86_2015.exe EN version->vcredist_x86_2015.exe
Jan 7, 2021:
- 9:14 AM Ticket #3800 (Number() - case sensivity with scientific notation by using $NUMBER_AUTO) closed by
- Fixed: Already solver for the next Beta/Release
- 7:48 AM Ticket #3800 (Number() - case sensivity with scientific notation by using $NUMBER_AUTO) created by
- Following Script: […] produces: […] The capitalized letter "E" …
Note:
See TracTimeline
for information about the timeline view.
