Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
I enabled "Activate a window by hovering over it with the mouse" in Windows 7 and I am not able to reproduce any problems with using Windows Explorer file associations.  I tried all the scenarios you have listed, SlickEdit Standard 2017 open & closed, with no files open, file already open, and I did not have any issues with files opened by dbl-click in Windows Explorer.  Are there any other settings you have enabled that you might also have enabled that?  You state that SlickEdit does have focus after double-clicking, does the open editor control have focus (cursor-blinking) or maybe some other window has focus?
22
SlickEdit® / Window/file configuration not saved on crash
« Last post by jorick on May 25, 2018, 01:42:48 pm »
A power failure caused SE to close unexpectedly.  When SE was restarted, none of my current files were loaded.  Instead, SE loaded all of the files from a previous project that I had worked on the day before.  I wasted a half hour chasing down the files I was working on when the power failure occurred.
23
SlickEdit® / Unable to do a Find In Files on word at cursor in child window
« Last post by jorick on May 25, 2018, 01:27:03 pm »
If I grab a tab and pull it out of the main SE window, and then try to click on a word and do a Find In Files, the dialog box will show the word at the cursor in a different window inside the main SE window.  I have to select the word, copy it, and then insert the word into the dialog box.

SlickEdit Pro 2017 (v22.0.2.1 64-bit)

Serial number: [redacted]
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\22\slickedit.lic

Build Date: February 12, 2018
Emulation: CodeWright

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 62% Load, 17898MB/28577MB Physical, 19312MB/57152MB Page File, 773MB/8388607MB Virtual
Shell Information: C:\Windows\system32\cmd.exe /q
Screen Size: 1680 x 1050, 1680 x 1050, 1680 x 1050, 1680 x 1050, 1920 x 1200

Project Type: (Other)
Language: .c (C/C++)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 22.0.2\ (non-removable drive,NTFS,86658MB free)
Configuration Directory: C:\Users\rbennet\Documents\My SlickEdit Config\22.0.2\ (non-removable drive,NTFS,86658MB free)
Migrated from: C:\Users\rbennet\Documents\My SlickEdit Config\22.0.0\

24
ok, sorry. I wasn't sure if process monitor could do it or not  -  it chucks out so much stuff I thought it might.

MultiMon can
http://www.resplendence.com/downloads
When it opens, tick the "keyboard" checkbox on the left, then the green arrow on the toolbar at top left.  Then fire up slickedit etc.  - press the up arrow key or something.
Multimon will tell you the process that got the key as well as the window title and PID.
If the focus is in the MDI window, then the name and path of the file being edited will be in the window title, if the focus is in search results then the window title will be "search results" etc.  Check the PID against what task manager shows.

Slickedit definitely doesn't stop you from running multiple instances of slick and they can be any version.  To run multiple instances you need to use the +new switch when you invoke slick
ve.exe +new  - so in the properties dialog for the shortcut you use to start slick, add +new into the "Target" setting at the end.
When you start V22, make sure in task manager that slick isn't already running.

If you still can't resolve it you could try this macro
https://community.slickedit.com/index.php/topic,16114.msg61880.html#msg61880


25
SlickEdit® / Re: Configuring mingw project in v22.0.2.1
« Last post by bremenpl on May 25, 2018, 04:01:46 am »
Code: [Select]
C:\mingw32\bin\mingw32-make.exe
This path does exist, make is for some reason elsewhere:

Code: [Select]
C:\MinGW\msys\1.0\bin\make.exe
So when I run --version:

Code: [Select]
C:\Windows\System32>C:\MinGW\msys\1.0\bin\make.exe --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-msys

C:\Windows\System32>

Now I try to make manually, using this makefile:

Code: [Select]
all: Debug/test.o
C:/MinGW/bin/gcc.exe  -O0 -g3 -ggdb -p -pg -o "Debug/test.exe" Debug/test.o

Debug/test.o : test.c
C:/MinGW/bin/gcc.exe -c   -O0 -g3 -ggdb -p -pg -o "Debug/test.o"  test.c


It works:

Code: [Select]
k:\test>C:\MinGW\msys\1.0\bin\make.exe -f makefile
C:/MinGW/bin/gcc.exe -c   -O0 -g3 -ggdb -p -pg -o "Debug/test.o"  test.c
C:/MinGW/bin/gcc.exe  -O0 -g3 -ggdb -p -pg -o "Debug/test.exe" Debug/test.o

k:\test>

Here I show again the slickedit makefile, after all path modifications that doest work:

Code: [Select]
# SlickEdit generated file.  Do not edit this file except in designated areas.

# Make command to use for dependencies
MAKE=C:\MinGW\msys\1.0\bin\make.exe
RM=rm
MKDIR=mkdir

# -----Begin user-editable area-----

# -----End user-editable area-----

# If no configuration is specified, "Debug" will be used
ifndef CFG
CFG=Debug
endif

#
# Configuration: Debug
#
ifeq "$(CFG)" "Debug"
OUTDIR=Debug
OUTFILE=$(OUTDIR)/test.exe
CFG_INC=
CFG_LIB=
CFG_OBJ=
COMMON_OBJ=$(OUTDIR)/test.o
OBJ=$(COMMON_OBJ) $(CFG_OBJ)
ALL_OBJ=$(OUTDIR)/test.o

COMPILE=C:/MinGW/bin/gcc.exe -c -O0 -g3 -ggdb -p -pg -o "$(OUTDIR)/$(*F).o" $(CFG_INC) $<
LINK=C:/MinGW/bin/gcc.exe -O0 -g3 -ggdb -p -pg -o "$(OUTFILE)" $(ALL_OBJ)
COMPILE_ADA=gnat -g -c -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_ADB=gnat -g -c -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_F=gfortran -c -g -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_F90=gfortran -c -g -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_D=gdc -c -g -o "$(OUTDIR)/$(*F).o" "$<"

# Pattern rules
$(OUTDIR)/%.o : %.c
$(COMPILE)

$(OUTDIR)/%.o : %.ada
$(COMPILE_ADA)

$(OUTDIR)/%.o : %.d
$(COMPILE_D)

$(OUTDIR)/%.o : %.adb
$(COMPILE_ADB)

$(OUTDIR)/%.o : %.f90
$(COMPILE_F90)

$(OUTDIR)/%.o : %.f
$(COMPILE_F)

# Build rules
all: $(OUTFILE)

$(OUTFILE): $(OUTDIR) $(OBJ)
$(LINK)

$(OUTDIR):
$(MKDIR) -p "$(OUTDIR)"

# Rebuild this project
rebuild: cleanall all

# Clean this project
clean:
$(RM) -f $(OUTFILE)
$(RM) -f $(OBJ)

# Clean this project and all dependencies
cleanall: clean
endif

#
# Configuration: Release
#
ifeq "$(CFG)" "Release"
OUTDIR=Release
OUTFILE=$(OUTDIR)/test.exe
CFG_INC=
CFG_LIB=
CFG_OBJ=
COMMON_OBJ=$(OUTDIR)/test.o
OBJ=$(COMMON_OBJ) $(CFG_OBJ)
ALL_OBJ=$(OUTDIR)/test.o

COMPILE=gcc -c   -o "$(OUTDIR)/$(*F).o" $(CFG_INC) $<
LINK=gcc  -o "$(OUTFILE)" $(ALL_OBJ)
COMPILE_ADA=gnat -O -c -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_ADB=gnat -O -c -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_F=gfortran -O -g -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_F90=gfortran -O -g -o "$(OUTDIR)/$(*F).o" "$<"
COMPILE_D=gdc -c -g -o "$(OUTDIR)/$(*F).o" "$<"

# Pattern rules
$(OUTDIR)/%.o : %.c
$(COMPILE)

$(OUTDIR)/%.o : %.ada
$(COMPILE_ADA)

$(OUTDIR)/%.o : %.d
$(COMPILE_D)

$(OUTDIR)/%.o : %.adb
$(COMPILE_ADB)

$(OUTDIR)/%.o : %.f90
$(COMPILE_F90)

$(OUTDIR)/%.o : %.f
$(COMPILE_F)

# Build rules
all: $(OUTFILE)

$(OUTFILE): $(OUTDIR) $(OBJ)
$(LINK)

$(OUTDIR):
$(MKDIR) -p "$(OUTDIR)"

# Rebuild this project
rebuild: cleanall all

# Clean this project
clean:
$(RM) -f $(OUTFILE)
$(RM) -f $(OBJ)

# Clean this project and all dependencies
cleanall: clean
endif

Do you have any hints after this?


26
SlickEdit® / Re: Configuring mingw project in v22.0.2.1
« Last post by Dennis on May 24, 2018, 09:34:43 pm »
Really looks like something is amiss about your mingw installation and mingw make.  What do you get if you run C:\mingw32\bin\mingw32-make.exe --version ?

Why don't you go ahead and write your own Makefile for building your program and see if you can get that off the ground.  Then you can return to debugging whatever is going wrong with the makefile that we are generating for you.
27
SlickEdit® / Re: Configuring mingw project in v22.0.2.1
« Last post by bremenpl on May 24, 2018, 06:34:35 pm »
Yes, I have also included the msys path. When I manually run make:

Code: [Select]
k:\test>C:\MingW/bin/mingw32-make.exe -f test.mak
C:/MinGW/bin/gcc.exe -O0 -g3 -ggdb -p -pg -o "Debug/test.exe" Debug/test.o
gcc.exe: fatal error: no input files
compilation terminated.
test.mak:61: recipe for target 'Debug/test.exe' failed
mingw32-make.exe: *** [Debug/test.exe] Error 1

k:\test>
28
Hi Graeme,

I see now you said "Process Monitor" not "Process Explorer"!  So I just opened Process Monitor and it's incomprehensible to me.

Thanks,

-Rob
29
SlickEdit® / Re: Configuring mingw project in v22.0.2.1
« Last post by Dennis on May 24, 2018, 04:17:37 pm »
What's entered in the makefile is only used if the makefile has to call 'make' recursively, for example to compile a dependent project.

You are running just 'make', but what you just sent was mingw32-make.exe, so are you certain that when you run 'make' that it is running C:/mingw/bin/make ?

What happens if you run C:\MingW/bin/mingw32-make.exe -f test.mak ?

On my Windows machine, I had to insure that /c/mingw/msys/1.0.bin/ was in my PATH in order for make to work correctly with the mingw gcc compiler.  The easiest way to do that is to launch the msys shell window rather than the more bare-bones mingw32 terminal.
30
SlickEdit® / Re: Configuring mingw project in v22.0.2.1
« Last post by bremenpl on May 24, 2018, 03:07:54 pm »
Its the right make. I have now even entered it manually in the makefile:
Code: [Select]
MAKE=C:/MinGW/bin/mingw32-make.exe
The thing is I can execute it from command line and it works. It just doesnt when run in the slickedit script.
Pages: 1 2 [3] 4 5 ... 10