Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
SlickEditĀ® / Re: command line and scroll bars blacked out
« Last post by Dan on September 20, 2023, 05:58:23 pm »
Is this 27.0.2?

If you go to Tools>Options, Appearance/Tool Window and Toolbar Options, what is "Button Size" set to?
42
SlickEditĀ® / command line and scroll bars blacked out
« Last post by pbrightly on September 20, 2023, 05:53:22 pm »
I've been experiencing a problem lately where my command-line and scrollbars turn black-on-black.  I can see the cursor when I click on command area, but nothing else.  yellow message text shows up if I click on some other app.

This is on latest Windows 11.
I don't know the root cause yet (well.. scenario that causes it).
Workaround: restart editor
43
SlickEdit 2023 v28 Beta Discussion / Javadoc Preview Ignores paragraph separators
« Last post by Johnco3 on September 20, 2023, 03:38:17 pm »
Javadoc Preview broken. 

The following example ignores the paragrapgh breaks.  (note the terminating </p> is not required in Javadoc (it doesn't fix it either).  This currently works in SlickEdit Pro 2022.

Note, another difference is the blank line separator before the Parameters: section (I think I prefer this in the new beta, SlickEdit 2022 leaves no space before the parameters section which looks a little ugly in my opinion).

Code: [Select]
    /**
     * configureDevice slot.
     *
     * <p>This slot runs in the worker thread context.
     *
     * <p>If <code>rDeviceConfigPath</code> is in XML format (*.xml
     * or *.adcx), it is parsed for the the input and output
     * VL definitions and converted to ASCII-HEX format where the
     * file is used to initialize the AIT hardware.
     *
     * <p>If <code>rDeviceConfigPath</code> is in ASCII-HEX format
     * (*.hex or *.adc), the file is converted to XML and parsed for
     * input and output VL definitions.  The ASCII-HEX file is then
     * used to initialize the AIT hardware.
     *
     * <p>If the <code>rDeviceConfigPath</code> is located in the
     * resource area of the application, we must firstly copy the
     * file to the temp folder so it can read by the converter
     * executable.  The code uses the <code>QTemporaryFile</code>
     * for this purpose.
     *
     * @param rDeviceConfigPath [in] XML or HEX Simulyzer device
     *                          configuration path (filesystem or
     *                          resource file).
     */
    void handleConfigureDevice(const QFileInfo& rDeviceConfigPath);

I attach a copy of the latest version of the preview (as of Beta 3, it was also broken in Beta 2) and the previous working version
44
SlickEdit 2023 v28 Beta Discussion / Re: Slickedit doesn't paste from clipboard
« Last post by Clark on September 20, 2023, 12:27:54 pm »
Beta 3 is available now
45
SlickEdit 2023 v28 Beta Discussion / Re: Soft linking to vs doesn't work
« Last post by patrick on September 18, 2023, 08:26:17 pm »
Reproduced, we need to resolve that link so it's not a relative path before we start .

I hacked together something quick if you want a workaround. I'll add something that's actually tested for the beta 3.  Changes to the first 3 lines of the vs script:
Code: [Select]
CPATH="`realpath \"$0\"`"
VS_LAUNCH_BIN_NAME="`basename \"$CPATH\"`"
VS_LAUNCH_BIN_PATH="`dirname \"$CPATH\"`"

46
SlickEdit 2023 v28 Beta Discussion / Soft linking to vs doesn't work
« Last post by astromme on September 18, 2023, 06:12:59 pm »
As I called out here, https://community.slickedit.com/index.php/topic,19258.msg76910.html#msg76910 I'm running into an error when I try to use soft links.

Code: [Select]
stromme@WORK:~/bin$ ls -la
total 44
drwxrwxr-x  2 stromme stromme 4096 Sep 18 11:17 .
drwxr-x--- 37 stromme stromme 4096 Sep 18 11:50 ..
lrwxrwxrwx  1 stromme stromme   13 Oct 27  2022 Grep -> /usr/bin/grep
lrwxrwxrwx  1 stromme stromme   23 Aug 10 16:56 old-slickedit-dir -> /opt/slickedit-pro2021/
lrwxrwxrwx  1 stromme stromme   30 Sep 18 11:08 slickedit-dir -> /opt/slickedit-pro2023beta2qt/
lrwxrwxrwx  1 stromme stromme   28 Sep  5 12:59 slickedit-dir.old -> /opt/slickedit-pro2023beta2/
-rwxrwxr-x  1 stromme stromme   15 Jan 24  2023 ubuntu_version
lrwxrwxrwx  1 stromme stromme   20 Sep 18 11:09 vs -> slickedit-dir/bin/vs
lrwxrwxrwx  1 stromme stromme   24 Aug 10 16:56 vsdiff -> slickedit-dir/bin/vsdiff
-rwxr-xr-x  1 stromme stromme   38 Aug 10  2022 vs-git
lrwxrwxrwx  1 stromme stromme   25 Aug 10 16:56 vsmerge -> slickedit-dir/bin/vsmerge

I have ~/bin/ in my PATH.

When I try to create a new file:
Code: [Select]
stromme@WORK:~$ vs newfile
/home/stromme/bin/vs: 49: exec: slickedit-dir/bin/vs_exe: not found

Interestingly:
Code: [Select]
stromme@WORK:~$ cd bin
stromme@WORK:~/bin$ vs newfile
stromme@WORK:~/bin$

If I'm in the ~/bin directory, things seem to work.
47
SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults
« Last post by Clark on September 18, 2023, 05:41:14 pm »
No need to test this installer. Glad Qt 5 vsdiff works!
48
SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults
« Last post by astromme on September 18, 2023, 05:38:48 pm »
Yes.

SlickEdit Pro 2023 (v28.0.0.2 64-bit Qt5) vsdiff works fine.

SlickEdit Pro 2023 (v28.0.0.2 64-bit Qt4) vsdiff crashes as described earlier.
49
SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults
« Last post by Clark on September 18, 2023, 05:32:02 pm »
Not sure I completely follow your post.

Does the Qt 5 v28 beta 2 vsdiff work for you?
50
SlickEdit 2023 v28 Beta Discussion / Re: Directory diff seg faults
« Last post by astromme on September 18, 2023, 05:18:25 pm »
Incidentally, I switched to qt5 version (via softlinks) we talked about here: https://community.slickedit.com/index.php/topic,19267.msg76904.html#msg76904 and it doesn't crash.. I switched back to to the "original" 2023 beta 2 and it crashes again.

Would you still like me to try the debug version you created?
Pages: 1 ... 3 4 [5] 6 7 ... 10