Recent Posts

Pages: [1] 2 3 ... 10
1
SlickEdit® / Re: Per window color profile
« Last post by Dennis on Today at 01:59:38 pm »
This is the same as the other issue.  Will be addressed by the hot fix.
2
SlickEdit® / Re: Per file color profile
« Last post by Dennis on Today at 01:58:57 pm »
Hot fix is forthcoming for multiple-files-share-window case when changing color profile settings.
3
SlickEdit® / Re: Per file color profile
« Last post by Dennis on Today at 12:13:48 pm »
Remind me, are you using Brief emulation where one-file-per-window is turned off?  If that is the case, I've reproduced the issue.
4
SlickEdit® / Re: Per window color profile
« Last post by jporkkahtc on October 25, 2021, 09:43:26 pm »
Note that foobar.pem was still loaded, and now in the vpwhist file it doesn't specify a color profile anymore.

Code: [Select]
BUFFER: BN="\TEMP\foobar.pem"""""
BI: MA=1 74 1  TABS= WWS=1 IWT= ST=8 IN=0 BW=0 US=2000 RO=0 SE=1 SN=0 BIN=0 MN= HM=0 MF=51380224 TL=0 MLL=0 ASE=0 LNL=1 LCF=6 CAPS=0 E=0 ESBU2=-1 CL="," SC="" SCE= SCU= ALM=0 FWRM=0 HMRE=0 HMRBW=0 SPCWT= SWF=2 SM= STAT= BFONT="" MFONT="" DF=1024 SCO=
VIEW: LN=.1268 CL=26 LE=0 CX=27 CY=26 WI=5 BI=1 HT=0 HN=0 HF=0 HC=4 HB=4
5
SlickEdit® / Per window color profile
« Last post by jporkkahtc on October 25, 2021, 09:41:35 pm »
Trying to fix my now mixed set of colors for all the files I have open, I used Window->Color, selected my Light theme and set "All files and global default".

It switched the current file to Light, but none of the other files I currently have open got updated.
6
SlickEdit® / Per file color profile
« Last post by jporkkahtc on October 25, 2021, 09:39:03 pm »
Today I switch back to light colors after having using dark for the last couple months - I switched just before the beta started I think.

Some of the files I had open at the time became light, but most are still dark.
So in my projects vpwhist file I see most of the files have CL="Black,"

Is this expected?
Shouldn't it be something like CL="" -- to mean whatever the default is, unless I had specifically set a profile for this file?

When I now open a file (that isn't already in the vpwhist file), it appears as CL="," - Presumably this means default?



Interesting ....
1. So, I had this file open: foobar.pem
2. Current Tools > Options > Appearance > Colors editor profile set to "Light: AJoe Default".
3. I have 2 editor windows side by side, and neither editor window was showing foobar.pem.
4. In the VPWHist file:
Code: [Select]
BUFFER: BN="\TEMP\foobar.pem"""""
BI: MA=1 74 1  TABS= WWS=1 IWT= ST=8 IN=0 BW=0 US=2000 RO=0 SE=1 SN=0 BIN=0 MN= HM=0 MF=51380224 TL=0 MLL=0 ASE=0 LNL=1 LCF=6 CAPS=0 E=0 ESBU2=-1 CL="," SC="" SCE= SCU= ALM=0 FWRM=0 HMRE=0 HMRBW=0 SPCWT= SWF=2 SM= STAT= BFONT="" MFONT="" DF=0 SCO=
VIEW: LN=.0 CL=1 LE=0 CX=2 CY=0 WI=5 BI=60 HT=0 HN=0 HF=0 HC=4 HB=4
5. I then changed Tools > Options > Appearance > Colors editor profile set to "Dark".
6. I switched one of the editor windows to show foobar.pem
7. foobar.pem appeared as Light.
8. Now in the VPWHIST file:
Code: [Select]
BUFFER: BN="\TEMP\foobar.pem"""""
BI: MA=1 74 1  TABS= WWS=1 IWT= ST=8 IN=0 BW=0 US=2000 RO=0 SE=1 SN=0 BIN=0 MN= HM=0 MF=51380224 TL=0 MLL=0 ASE=0 LNL=1 LCF=6 CAPS=0 E=0 ESBU2=-1 CL="Light: AJoe Default," SC="" SCE= SCU= ALM=0 FWRM=0 HMRE=0 HMRBW=0 SPCWT= SWF=2 SM= STAT= BFONT="" MFONT="" DF=1024 SCO=
VIEW: LN=.1268 CL=26 LE=0 CX=27 CY=26 WI=5 BI=62 HT=0 HN=0 HF=0 HC=4 HB=4


Since foobar.pem didn't have a color scheme specified in the VPWHist file, it should have been Dark when I switched to it - but instead it was light and now the VPWHist file explicitly specifies light for this file.
7
SlickEdit® / Re: Python debugging: Conditional Breakpoints
« Last post by patrick on October 25, 2021, 08:22:17 pm »
Fixed the disabled context menu entry for the first v26 hotfix.
8
SlickEdit® / Re: Python debugging: Conditional Breakpoints
« Last post by patrick on October 25, 2021, 07:46:17 pm »
I can reproduce that.  I can only edit the breakpoint properties with the button on the left with the wrench, but not with the context menu. 

For #1, true enough.  We don't have a conditional column in the breakpoints tool window, or a different gutter icon for breakpoints with conditions, so the only way to see now is to bring up the properties.
9
SlickEdit® / Re: V26 DZilla stack
« Last post by jporkkahtc on October 25, 2021, 04:52:29 pm »
That I didn't do, afaik.
Then again, I haven't reproed yet either.
10
SlickEdit® / Python debugging: Conditional Breakpoints
« Last post by jporkkahtc on October 25, 2021, 04:50:37 pm »
When I create a breakpoint I can make it conditional.
But in the Breakpoints tool the "Properties" item in the context menu is disabled.
There doesn't appear to be any way to
#1: Tell that a break point is conditional
#2: Edit the condition.
Pages: [1] 2 3 ... 10