Recent Posts

Pages: 1 [2] 3 4 ... 10
Thanks for the quick investigation and fix Clark!

I have not applied the latest version of the macro yet. Before applying it though, I do see the "Show/match files in current file directory", see attached screenshot, contrary to what you wrote.

Before applying the fix, I have some questions:

1) To apply it, I open the tbopen.e file in the editor and then do <ESC>load, correct? Does the tbopen.e file need to be in any special directory when I open it?
2) What happens when the official hotfix is available later. When I apply it, it will overwrite the tbopen.e file that I manually loaded from another location?
SlickEdit® / Press ESC to close CapsLock and IME
« Last post by netbrain on July 17, 2018, 06:07:43 am »

Press ESC to close CapsLock and IME, automatically.
using Vim emulation, it's helpful.
the attach zip file includes source and x64 dll file.

To build the dll file, add SE_INSTALL_PATH\h and sub-directory to include path,
add SE_INSTALL_PATH\lib to library path, add vsapi.lib to link library, set
configuration to x64/release depends on your platform.
To load the dll file, activate command line, type 'dload somepath\capslock.dll'.
To test, type 'capslock_information' in command line.
SlickEdit® / Re: Smart Open finds files from previous projects when it shouldn't
« Last post by Clark on July 16, 2018, 11:03:37 pm »
There are two bugs. First bug is that the smart open options are not being displayed. Second bug has to do with the "Show/match files in current file directory" option. It's on by default (hard to turn off now since the option isn't visible). When the last file is closed, there's a bug where this match list isn't being cleared. Both bugs were trivial to fix.

This will be fixed in the next hotfix build.

Since you're a pretty advanced user, I've attached the latest 22.0.2 version of this macro. I'm not sure if the first problem will just go away if you load this new tbopen.e (it may require a new state file). The more important fix is the second issue.

Thanks again for helping us find this.
Here's a little more info on the search part of it anyway.

Sometimes it gets stuck on a file and puts up that popup.  Click Ok, pops up again, click Ok again, and then the search window says:

Failed to open:  (some path)\some file.c or .h (which is the filter I'm using)

However, Slick Edit can indeed open those files.  You can copy the path and open it and boom, open in Slick Edit.  Indeed, even if the file is already open in Slick Edit, it happens again.

You should put an AI button on that popup with the text we can click:  "Are you sure you can't open it?  It's open right there behind you inside of you!" :) :) :)
SlickEdit 2013 (v18.0.1.2 64-bit)
Win 7 Enterprise 64-bit

This started today (reboot after weekend) so I don't know what's going on.

It pops up a little window with "Error Creating Directory Entry".

This happens in these situations:

1. Starting Slick Edit (sometimes)
2. Searching big directories recursively (which makes the search "stuck" somewhere.)

If I click Ok, the search continues, but I usually encounter 5-6 of these stuck popups.

I tried deleting everything in My Slickedit Config under Documents.  Slick Edit is reset to factory more or less (you would know this; I don't) and it wants to drive me through a setup wizard.

Anyway, whatever the problem is, it isn't in that Documents folder.

Also, I have no *.stu files, which is the only other reference I can find using Google, on this site.  So both threads I can find, one from 2006, and one from 2014, do not have a working solution (anymore.)

SlickEdit® / Re: Compile current file on save
« Last post by asandler on July 16, 2018, 08:14:26 pm »
OK. I got it working. I created a new build tool that compiles one file (I could not use stock Compile tool, more on this later). Then I wrote a Slick-C macro that runs it.

I could not actually use Compile tool because for GNU C/C++ projects I cannot make it use my own command. Not sure why.
Another problem has been the fact that in a new build tool I could not express what I want to do in terms of escape sequences for build commands. To compile single file located at <ROOT>/src/foo/bar.c we have to run make out/src/foo/bar.o. It could be possible to do that if there was escape sequence that returns file path relative to project's root directory. So I wrote a small BASH script that constructs and wraps above make command.

Another caveat that I don't quite know how to solve yet is that my new Compile tool is defined for all file extensions. I don't want to run it on anything but C files. I solved this problem by ignoring all non-C files in the wrapper script. However, may be this is the right way to do it because I do want to save the file even if it is not a C file.
SlickEdit® / Re: Smart Open finds files from previous projects when it shouldn't
« Last post by Clark on July 16, 2018, 08:04:14 pm »
Reproduced. You do have that option unchecked. Thanks for taking the time to give us a small test case.
That is currently unchecked in my smart open, and I still have this issue. You should be able to see that in the configuration that I sent.
SlickEdit® / Re: Smart Open finds files from previous projects when it shouldn't
« Last post by Dennis on July 16, 2018, 02:21:41 pm »
Right click in the file list for the Smart Open tool window.  Under "Options", uncheck "Show/match files in history".
SlickEdit® / Re: Compile current file on save
« Last post by Dennis on July 16, 2018, 02:18:10 pm »
The project_compile() command will save the current file if you have the "compile" tool configured to do so in your project properties.
Pages: 1 [2] 3 4 ... 10