News on upgrading to WinEdt 8.2

[Karl Koeller]

Dear WinEdt-ers,

WinEdt 8.2 has been officially released today.

If you are using one of the following contributions from winedt.org,
you can quietly proceed with the Upgrade functionality:

- Acronym
- ANSI2UTF8
- arara
- Asymptote
- ConTeXt standalone
- DocZoom
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- bibMacros
- FasTeX
- MathGreek
- R-Sweave
- Stata-support

After you perform the Upgrade process, the following package has to
be installed over the old one, due to radical changes in DocTabs.ini:

- DocZoom

The new version for WinEdt 8.2 is available already at winedt.org.

I would suggest that you install the new version over the old one also
for the following packages:

- arara
- Asymptote
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- R-Sweave
- Stata-support

If you instead have the following package installed, it must be uninstalled
before installing WinEdt 8.2 and you will have then to install the new
version in WinEdt 8.2:

- YandY TeX

Moreover, note that many configuration files have been radically modified
in WinEdt 8.2, so the Upgrade process may fail for someone.
If you are one of them and you are not able to solve the issue by yourself,
feel free to ask for help.

Best regards to all and enjoy WinEdt 8.2.

Karl

[Zulkifli Hidayat]

The main page of winedt.com seems not yet updated.

Best,
-Zul-

Post by Karl Koeller
Dear WinEdt-ers,
WinEdt 8.2 has been officially released today.
If you are using one of the following contributions from winedt.org,
- Acronym
- ANSI2UTF8
- arara
- Asymptote
- ConTeXt standalone
- DocZoom
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- bibMacros
- FasTeX
- MathGreek
- R-Sweave
- Stata-support
After you perform the Upgrade process, the following package has to
- DocZoom
The new version for WinEdt 8.2 is available already at winedt.org.
I would suggest that you install the new version over the old one also
- arara
- Asymptote
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- R-Sweave
- Stata-support
If you instead have the following package installed, it must be uninstalled
before installing WinEdt 8.2 and you will have then to install the new
- YandY TeX
Moreover, note that many configuration files have been radically modified
in WinEdt 8.2, so the Upgrade process may fail for someone.
If you are one of them and you are not able to solve the issue by yourself,
feel free to ask for help.
Best regards to all and enjoy WinEdt 8.2.
Karl

[Karl Koeller]

The main page of winedt.com <http://winedt.com> seems not yet updated.
Best,
-Zul-

Press F5 in your browser.

Karl

[Alex Degtyarev]

There seems to have been a huge change in the syntax: *_COLOR things require
a string parameter now and there seems to be no *_RGB things anymore. Is
there an easy way to upgrade? Are there constants for what used to be the
0..15 colors?

-----Original Message-----
Sent: Saturday, June 14, 2014 12:31 AM
Subject: [WinEdt] News on upgrading to WinEdt 8.2
Dear WinEdt-ers,
WinEdt 8.2 has been officially released today.
If you are using one of the following contributions from winedt.org, you

can

- Acronym
- ANSI2UTF8
- arara
- Asymptote
- ConTeXt standalone
- DocZoom
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- bibMacros
- FasTeX
- MathGreek
- R-Sweave
- Stata-support
After you perform the Upgrade process, the following package has to be
- DocZoom
The new version for WinEdt 8.2 is available already at winedt.org.
I would suggest that you install the new version over the old one also for

the

- arara
- Asymptote
- Figures&Tables
- LaTeX3
- LaTeXify
- MetaPreview
- Nomenclature
- VerbatimPlus
- R-Sweave
- Stata-support
If you instead have the following package installed, it must be uninstalled
before installing WinEdt 8.2 and you will have then to install the new

version in

- YandY TeX
Moreover, note that many configuration files have been radically modified

in

WinEdt 8.2, so the Upgrade process may fail for someone.
If you are one of them and you are not able to solve the issue by

yourself, feel

free to ask for help.
Best regards to all and enjoy WinEdt 8.2.
Karl

[Alex Degtyarev]

This should probably be regarded as a bug report.

anymore. Is there an easy way to upgrade? Are there constants for what

used

to be the
0..15 colors?

I found the constants, but before I did, I replaced 13 with "RGB_13" at one
of the *_COLOR= statements (admittedly stupid of mine :) Naturally, I got an
error. However, after I replaced this with the correct value, I could not
recompile the configuration anymore: the error persisted even after restart,
pointing to innocent lines in random *.ini files. I had to execute "Rebuild
default" before I could rebuild my local configuration again.

Best,
Alex

[WinEdt Team]

Alex,

Post by Alex Degtyarev
I found the constants, but before I did, I replaced 13 with
"RGB_13" at one of the *_COLOR= statements (admittedly stupid of
mine :) Naturally, I got an error. However, after I replaced this
with the correct value, I could not recompile the configuration
anymore: the error persisted even after restart, pointing to
innocent lines in random *.ini files. I had to execute "Rebuild
default" before I could rebuild my local configuration again.

A problem like that can occur in custom configuration files with
multiple *-sections because a warning is issued at the end of any
section that requires recompiling the colors and at that point
WinEdt stops processing the file and thus never comes to the place
where a wrong value has been assigned and corrected.

I suppose I can modify this behavior for warnings of this nature by
continuing with loading the configuration... I will probably do
this (done and uploaded) but:

Loading defaults and rebuilding local is often a good idea for
users that are using *-sections in their private settings a lot and
have committed and corrected errors in their local settings.

[COLOR*] section (if used properly) allow easy modification of some
colors without requiring direct modifications to long and
complicated highlighting files like switches or keywords...
However, one should not introduce new colors that are used for
highlighting (eg. Switches.ini) in Private settings because Rebuild
All command will result in warnings after Colors.ini is loaded (at
that point you will have undefined color references until
Private.ini is loaded at the end and extra colors become defined).
%INCLUDE in Colors.ini is a way to go if you need more named colors
for use elsewhere (this is the first configuration loaded). In
private settings it is safe to overwrite colors but not define new
ones unless you change Rebuild*.edt macros to load things in
different order but then you will have pay attention to maintain
these macros in the future when new configuration section may be
introduced...

Advanced users that take advantage of customizations in their
private settings should keep this in mind.

Best regards,

alex

[Alex Degtyarev]

Thanks, Alex. I'll keep this in mind.

-----Original Message-----
Sent: Saturday, June 14, 2014 11:43 PM
Subject: Re: [WinEdt] News on upgrading to WinEdt 8.2
Alex,

Post by Alex Degtyarev
I found the constants, but before I did, I replaced 13 with "RGB_13"
at one of the *_COLOR= statements (admittedly stupid of mine :)
Naturally, I got an error. However, after I replaced this with the
correct value, I could not recompile the configuration
anymore: the error persisted even after restart, pointing to innocent
lines in random *.ini files. I had to execute "Rebuild default" before
I could rebuild my local configuration again.

A problem like that can occur in custom configuration files with multiple

*-

sections because a warning is issued at the end of any section that

requires

recompiling the colors and at that point WinEdt stops processing the file

and

thus never comes to the place where a wrong value has been assigned and
corrected.
I suppose I can modify this behavior for warnings of this nature by

continuing

with loading the configuration... I will probably do this (done and
Loading defaults and rebuilding local is often a good idea for users that

are

using *-sections in their private settings a lot and have committed and
corrected errors in their local settings.
[COLOR*] section (if used properly) allow easy modification of some colors
without requiring direct modifications to long and complicated

highlighting

files like switches or keywords...
However, one should not introduce new colors that are used for

highlighting

(eg. Switches.ini) in Private settings because Rebuild All command will

result in

warnings after Colors.ini is loaded (at that point you will have undefined

color

references until Private.ini is loaded at the end and extra colors become
defined).
%INCLUDE in Colors.ini is a way to go if you need more named colors for

use

elsewhere (this is the first configuration loaded). In private settings it

is safe to

overwrite colors but not define new ones unless you change Rebuild*.edt
macros to load things in different order but then you will have pay

attention to

maintain these macros in the future when new configuration section may be
introduced...
Advanced users that take advantage of customizations in their private

settings

should keep this in mind.
Best regards,
alex

[Karl Koeller]

Post by Alex Degtyarev
There seems to have been a huge change in the syntax: *_COLOR things require
a string parameter now and there seems to be no *_RGB things anymore. Is
there an easy way to upgrade? Are there constants for what used to be the
0..15 colors?

Use "Upgrade Personal Configuration" under Maintenance menu.

For manual work use the following substitutions:

*_COLOR=-1 *_COLOR="SysNone"
*_COLOR=0 *_COLOR="clWindowText"
*_COLOR=1 *_COLOR="RGB_4"
*_COLOR=2 *_COLOR="RGB_6"
*_COLOR=3 *_COLOR="RGB_E"
*_COLOR=4 *_COLOR="RGB_0"
*_COLOR=5 *_COLOR="RGB_3"
*_COLOR=6 *_COLOR="RGB_F"
*_COLOR=7 *_COLOR="RGB_9"
*_COLOR=8 *_COLOR="xclComment"
*_COLOR=9 *_COLOR="RGB_5"
*_COLOR=10 *_COLOR="RGB_6"
*_COLOR=11 *_COLOR="RGB_9"
*_COLOR=12 *_COLOR="RGB_1"
*_COLOR=13 *_COLOR="RGB_2"
*_COLOR=14 *_COLOR="RGB_7"
*_COLOR=15 *_COLOR="clWindow"

Regards,

Karl

[Alex Degtyarev]

Post by Karl Koeller
Use "Upgrade Personal Configuration" under Maintenance menu.

Did not work: some %INCLUDE'd files were left over.

[Karl Koeller]

Post by Alex Degtyarev

Post by Karl Koeller
Use "Upgrade Personal Configuration" under Maintenance menu.

Did not work: some %INCLUDE'd files were left over.

They had to be in %b\ConfigEx to be upgraded...

Karl

[Alex Degtyarev]

Post by Karl Koeller
They had to be in %b\ConfigEx to be upgraded...

Would it search subfolders (in the future?)
Here is my point: WinEdt stores locally its own files changed by the users.
However, for "big" changes, it is easier to maintain the configurations if
they are in separate files, preferably stored in a separate folder. Right
now they are in %b\Custom; what if I move them, say, to %b\ConfigEx\Custom:
will they be upgraded automatically?

Post by Karl Koeller
Karl

[Karl Koeller]

Post by Alex Degtyarev

Post by Karl Koeller
They had to be in %b\ConfigEx to be upgraded...

Would it search subfolders (in the future?)
Here is my point: WinEdt stores locally its own files changed by the users.
However, for "big" changes, it is easier to maintain the configurations if
they are in separate files, preferably stored in a separate folder. Right
will they be upgraded automatically?

No, they have to be in %b\ConfigEx

Karl

[Gyorgy SZEIDL]

Dear List Members?

I have two questions (the second is more imortant
for me).

1. Is there a way to make winedt show the line numbers
if I open a file? Without clicking on the left margin and
choosing the option Show line numbers? I would like
winedit to show the line numbers as default!

2. I have installed WinEdt82 and changed the background scheme:
(a) the default is disabled.
(b) the last two schemes are rewritten so that I can get back my
favorite schemes (Those I have used under WinEdt60-WinEdt81)
(c) Option Allow Environment Background is also disabled.
(d) Scheme "Bitmap" (this is the second) works fine, however I am
unable to
to switch to scheme "Gradient Gray & Blue" (this is the first).
I have tried to set View Filter to
(I) "A;B" for both schemes
(II) "A" for the second, "B" for the first -- this works
perfectly under WinEdt81
(III) "A;B" for the second, "B" for the first.
There is however no change: scheme "Bitmap" works fine,
scheme "Gradient Gray & Blue" does not work. By the way I receive
no error message.

What have I done wrong?

Below you shall find the critical part of the file background scheme.ini
both for Winedt82 and for WinEdt60-WinEdt81.

Thank you for any information in advance
Best regards
G. Szeidl



WinEdt 82: ----------------------------------------------------------


BACKGROUND_SCHEME="Gradient Gray & Blue"
ENABLED=1
MODE_FILTER=""
VIEW_FILTER="B"
BACKGROUND_MODE=2
BACKGROUND_BITMAP="Bk-Gray.bmp"
TEXT_MODE=1
BACKGROUND_COLOR="$E8E8E8"
BOOKMARK_MODE=1
BACKGROUND_COLOR="$C6DCDF"
LINE_NUMBERS_MODE=1
BACKGROUND_COLOR="$E7BEBE"
TEXT_COLOR="#202020"
FOLDING_MARGIN_MODE=1
BACKGROUND_COLOR="#EFEFEF"
SCOPE_COLOR="#808080"
SCOPE_COLOR="SysNone"
SCOPE_HOT_COLOR="#0000FF"
SCOPE_HOT_COLOR="#00B0B0"
CURRENT_LINE_MODE=1
BACKGROUND_COLOR="$7BE0F2"
RIGHT_MARGIN_MODE=1
RIGHT_MARGIN_ENABLED=1
RIGHT_MARGIN_OFFSET=2
BACKGROUND_COLOR="$09AFDF"

//
===============================================================================
//
// Bitmaps can be used if you want to "carve" your text into wood or
marble:-)
//
// Defaults are bitmap-free:
// background like this is not considered "cool" these days!
//
// The following Bitmaps are by default in Bitmaps\Background Folder:
//
// BACKGROUND_BITMAP="Dots-Blue.bmp" // BACKGROUND_COLOR="#E7E7F6"
// BACKGROUND_BITMAP="Dots-Gray.bmp" // BACKGROUND_COLOR="#E9E9E9"
// BACKGROUND_BITMAP="Bk-Gray.bmp" // BACKGROUND_COLOR="#E8E8E8"
// BACKGROUND_BITMAP="Bk-Brown.bmp" // BACKGROUND_COLOR="#F3E7D1"
// BACKGROUND_BITMAP="Wood-Brown.bmp" // BACKGROUND_COLOR="#D8CDA2"
// BACKGROUND_BITMAP="Wood-Gray.bmp" // BACKGROUND_COLOR="#D8D8D8"
// BACKGROUND_BITMAP="Sky-Blue.bmp" // BACKGROUND_COLOR="#E3EAFE"
// BACKGROUND_BITMAP="Sky-Gray.bmp" // BACKGROUND_COLOR="#EDEFEC"
// BACKGROUND_BITMAP="Marble-Brown.bmp" // BACKGROUND_COLOR="#DAD3A1"
// BACKGROUND_BITMAP="Marble-Gray.bmp" // BACKGROUND_COLOR="#CFCFCF"
// BACKGROUND_BITMAP="Paper-Brown.bmp" // BACKGROUND_COLOR="#DFDCC6"
// BACKGROUND_BITMAP="Paper-Gray.bmp" // BACKGROUND_COLOR="#DADADA"
//
// Background Color is a bitmap average color (it can be used for panels)...
//
// This example requires 'Allow Environment Background' to be disabled
in the
// Preferences dialog.
//
//
===============================================================================

BACKGROUND_SCHEME="Bitmap"
ENABLED=1
MODE_FILTER=""
VIEW_FILTER="A"
BACKGROUND_MODE=2
BACKGROUND_BITMAP="Bk-Brown.bmp"
TEXT_MODE=1
BACKGROUND_COLOR="$D1E7F3"
BOOKMARK_MODE=1
BACKGROUND_COLOR="$C6DCDF"
LINE_NUMBERS_MODE=1
BACKGROUND_COLOR="$E7BEBE"
TEXT_COLOR="#202020"
FOLDING_MARGIN_MODE=1
BACKGROUND_COLOR="#E7E7FA"
SCOPE_COLOR="#808080"
SCOPE_COLOR="SysNone"
SCOPE_HOT_COLOR="#0000FF"
SCOPE_HOT_COLOR="#00B0B0"
CURRENT_LINE_MODE=1
BACKGROUND_COLOR="$7BE0F2"
RIGHT_MARGIN_MODE=1
RIGHT_MARGIN_ENABLED=1
RIGHT_MARGIN_OFFSET=2
BACKGROUND_COLOR="$09AFDF"

//
===============================================================================

[END]


WinEdt60 -- WinEdt81
---------------------------------------------------------------

BACKGROUND_SCHEME="Bitmap"
ENABLED=1
MODE_FILTER=""
VIEW_FILTER="A"
BACKGROUND_MODE=3
BACKGROUND_RGB="$D1E7F3"
BACKGROUND_BITMAP="Bk-Brown.bmp"
BOOKMARK_MODE=2
BACKGROUND_RGB="$E9C5C5"
LINE_NUMBERS_MODE=2
BACKGROUND_RGB="$E7BEBE"
DEFAULT_FONT=0
BOLD=0
TEXT_MODE=0
DEFAULT_FONT=1
TEXT_COLOR=0
CURRENT_LINE_MODE=2
BACKGROUND_RGB="$7BE0F2"
DEFAULT_FONT=1
TEXT_COLOR=0
RIGHT_MARGIN_ENABLED=1
RIGHT_MARGIN_OFFSET=2
RIGHT_MARGIN_MODE=2
BACKGROUND_RGB="$09AFDF"
DEFAULT_FONT=1
TEXT_COLOR=0

//
===============================================================================
BACKGROUND_SCHEME="Gradient Gray & Blue"
ENABLED=1
VIEW_FILTER="B"
MODE_FILTER=""
BACKGROUND_MODE=3
BACKGROUND_RGB="$E8E8E8"
BACKGROUND_BITMAP="Bk-Gray.bmp"
BOOKMARK_MODE=2
BACKGROUND_RGB="$C6DCDF"
LINE_NUMBERS_MODE=2
BACKGROUND_RGB="$E7BEBE"
DEFAULT_FONT=0
BOLD=0
TEXT_MODE=0
DEFAULT_FONT=1
TEXT_COLOR=0
CURRENT_LINE_MODE=2
BACKGROUND_RGB="$7BE0F2"
DEFAULT_FONT=1
TEXT_COLOR=0
RIGHT_MARGIN_ENABLED=1
RIGHT_MARGIN_OFFSET=2
RIGHT_MARGIN_MODE=2
BACKGROUND_RGB="$09AFDF"
DEFAULT_FONT=1
TEXT_COLOR=0

//
===============================================================================

[END]

[Alex Degtyarev]

I seem to have a similar problem with the background schemes.
I used to have this in my Private.ini:

[BACKGROUND_SCHEMES*]

// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"

BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"

which would successfully override just the two switches in the "common" .ini
file. Now, it does not seem to work anymore.

[Karl Koeller]

Post by Alex Degtyarev
I seem to have a similar problem with the background schemes.
[BACKGROUND_SCHEMES*]
// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"
BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"
which would successfully override just the two switches in the "common" .ini
file. Now, it does not seem to work anymore.

Try adding

BACKGROUND_SCHEME="Default"
ENABLED=0


Karl

[Alex Degtyarev]

Post by Karl Koeller

Post by Alex Degtyarev
I seem to have a similar problem with the background schemes.
[BACKGROUND_SCHEMES*]
// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"
BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"
which would successfully override just the two switches in the
"common" .ini file. Now, it does not seem to work anymore.

Try adding
BACKGROUND_SCHEME="Default"
ENABLED=0

Thanks. Still does not seem to work: when I change from A to B, nothing
happens.

[Karl Koeller]

Post by Gyorgy SZEIDL
Dear List Members?
I have two questions (the second is more imortant
for me).
1. Is there a way to make winedt show the line numbers
if I open a file? Without clicking on the left margin and
choosing the option Show line numbers? I would like
winedit to show the line numbers as default!
(a) the default is disabled.
(b) the last two schemes are rewritten so that I can get back my
favorite schemes (Those I have used under WinEdt60-WinEdt81)
(c) Option Allow Environment Background is also disabled.
(d) Scheme "Bitmap" (this is the second) works fine, however I am
unable to
to switch to scheme "Gradient Gray & Blue" (this is the first).
I have tried to set View Filter to
(I) "A;B" for both schemes
(II) "A" for the second, "B" for the first -- this works
perfectly under WinEdt81
(III) "A;B" for the second, "B" for the first.
There is however no change: scheme "Bitmap" works fine,
scheme "Gradient Gray & Blue" does not work. By the way I receive
no error message.

1. In Options -> Preferences -> Appearance, Show Line Numbers for Modes,
add "TeX".

2. It seems to be a bug...

Karl

[Gyorgy SZEIDL]

Thank you for your prompt reply Karl.
Best regards
Gyorgy

Post by Karl Koeller

Post by Gyorgy SZEIDL
Dear List Members?
I have two questions (the second is more imortant
for me).
1. Is there a way to make winedt show the line numbers
if I open a file? Without clicking on the left margin and
choosing the option Show line numbers? I would like
winedit to show the line numbers as default!
(a) the default is disabled.
(b) the last two schemes are rewritten so that I can get back my
favorite schemes (Those I have used under WinEdt60-WinEdt81)
(c) Option Allow Environment Background is also disabled.
(d) Scheme "Bitmap" (this is the second) works fine, however I am
unable to
to switch to scheme "Gradient Gray & Blue" (this is the first).
I have tried to set View Filter to
(I) "A;B" for both schemes
(II) "A" for the second, "B" for the first -- this
works perfectly under WinEdt81
(III) "A;B" for the second, "B" for the first.
There is however no change: scheme "Bitmap" works fine,
scheme "Gradient Gray & Blue" does not work. By the way I receive
no error message.

1. In Options -> Preferences -> Appearance, Show Line Numbers for
Modes, add "TeX".
2. It seems to be a bug...
Karl

[Ralf Heckmann]

Hi Karl,

-----Ursprüngliche Nachricht----- von: Karl Koeller [mailto:Karl
...
Moreover, note that many configuration files have been radically
modified in WinEdt 8.2, so the Upgrade process may fail for someone.
If you are one of them and you are not able to solve the issue by
yourself, feel free to ask for help.

I feel free :-)

I think/hope the upgrade had worked properly, although I had one error
message and three warnings on a WinEdt 8 (20131031) with no substantial
configuration changes:

The error was:
Initialization Error!
... WinEdt 8\Local\ConfigEx\Booksmark.ini(26): Unrecognized Keyword

Bookmarks.ini looks (after the Update) in the appropriate lines as follows:
25 // Highlight the Current Line Panel
26 HIGHLIGHT_BOOKMARK_PANEL=0

Is that error a serious one? I can't see ...


The warnings in Upgrade20140613.log are

xxxxxxxxx cut xxxxxxxxx

Bookmarks.ini

------------------------WARNING!!------------------------

The following lines

FLOATING_BOOKMARKS=0

// Highlight the Current Line Panel
HIGHLIGHT_BOOKMARK_PANEL=0

// Set to 0 if you don't want bookmarks
BOOKMARK_PANEL_WIDTH=24

//
===============================================================================

have not been found...
A correctly upgraded Bookmarks.ini should contain the following lines

FLOATING_BOOKMARKS=0

//
===============================================================================

=========================================================

Columns.ini

------------------------WARNING!!------------------------

The following lines

ENABLED=1
MODE_FILTER="DTX;INS;STY;Binary"

have not been found...
A correctly upgraded Columns.ini should contain the following lines

ENABLED=0
MODE_FILTER="INI;DTX;INS;STY;Binary"


WordCount.ini

=========================================================

Wrapping.ini

---------------------------OK!---------------------------

The following lines

REQUIRES=20131017

were already up-to-date

------------------------WARNING!!------------------------

The following lines

RIGHT_MARGIN=78

// Soft Wrapping Options

have not been found...
A correctly upgraded Wrapping.ini should contain the following lines

RIGHT_MARGIN=78

// Right Margin Constraint when FIXED_RIGHT_MARGIN=0
// When set to 1 fixed right margin is still used
// as long as the window is large enough
// This property is ignored when fixed right margin is enabled!
CONSTRAINED_RIGHT_MARGIN=0

// Soft Wrapping Options

xxxxxxxxx cut xxxxxxxxx


I think the warnings are somehow confusing as for example my
bookmarks.ini had

// Set to 0 if you don't want bookmarks
// Org: BOOKMARK_PANEL_WIDTH=24
BOOKMARK_PANEL_WIDTH=5

and my Wrapping.ini

// Fixed Right Margin
RIGHT_MARGIN=72

With these valid values there should not be any warning during the
upgrade process ...

Nevertheless, many thanks for the ongoing development and especially the
excellent support. With the endless number of configuration items in all
the ini-files that support is very helpful and appreciated.

Regards,
Ralf

[Karl Koeller]

Post by Ralf Heckmann
I feel free :-)
I think/hope the upgrade had worked properly, although I had one error
message and three warnings on a WinEdt 8 (20131031) with no substantial

The Upgrade process is not unfailing.... Unfortunately this time Alex
wanted to make too many changes to configuration files...

For the first error and the first warning substitute the lines


FLOATING_BOOKMARKS=0

// Highlight the Current Line Panel
HIGHLIGHT_BOOKMARK_PANEL=0

// Set to 0 if you don't want bookmarks
// Org: BOOKMARK_PANEL_WIDTH=24
BOOKMARK_PANEL_WIDTH=5

//
===============================================================================


with


FLOATING_BOOKMARKS=0

//
===============================================================================


The option BOOKMARK_PANEL_WIDTHis no longer available since WinEdt
automatically resizes that panel depending on the screen resolution.

About the second warning simply ignore it, while for the third
substitute the lines


RIGHT_MARGIN=72

// Soft Wrapping Options


with


RIGHT_MARGIN=72

// Right Margin Constraint when FIXED_RIGHT_MARGIN=0
// When set to 1 fixed right margin is still used
// as long as the window is large enough
// This property is ignored when fixed right margin is enabled!
CONSTRAINED_RIGHT_MARGIN=0

// Soft Wrapping Options

Post by Ralf Heckmann
With these valid values there should not be any warning during the
upgrade process ...

As I said, the Upgrade process is not unfailing.... It does what it can!

Post by Ralf Heckmann
Nevertheless, many thanks for the ongoing development and especially
the excellent support. With the endless number of configuration items
in all the ini-files that support is very helpful and appreciated.

Thanks for appreciating it.

Best regards,

Karl

[Ralf Heckmann]

Karl,

thanks for your answer and the useful explanations!

Regards,
Ralf

[WinEdt Team]

Alex,

I seem to have a similar problem with the background schemes. I
[BACKGROUND_SCHEMES*]
// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"
BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"
which would successfully override just the two switches in the
"common" .ini file. Now, it does not seem to work anymore.

This should work. But there was a bug in the original release which
caused problems with background schemes associated with a view
filter. This has now been fixed and a new version (with the same
build number) has been uploaded.

This will also fix Gyorgy's problem with the same functionality...

Best regards,

alex

[Alex Degtyarev]

Thanks, I will try it :)

-----Original Message-----
Sent: Saturday, June 14, 2014 9:52 PM
Subject: Re: [WinEdt] News on upgrading to WinEdt 8.2
Alex,

I seem to have a similar problem with the background schemes. I used
[BACKGROUND_SCHEMES*]
// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"
BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"
which would successfully override just the two switches in the
"common" .ini file. Now, it does not seem to work anymore.

This should work. But there was a bug in the original release which caused
problems with background schemes associated with a view filter. This has

now

been fixed and a new version (with the same build number) has been

uploaded.

This will also fix Gyorgy's problem with the same functionality...
Best regards,
alex

[Alex Degtyarev]

This should work. But there was a bug in the original release which caused
problems with background schemes associated with a view filter. This has

now

been fixed and a new version (with the same build number) has been

uploaded.

This will also fix Gyorgy's problem with the same functionality...

Yes, this works now. Thanks!

Best regards,
alex

[Gyorgy SZEIDL]

Thank you very much Alex. It works now.
Best regards
Gyorgy

Post by WinEdt Team
Alex,

I seem to have a similar problem with the background schemes. I
[BACKGROUND_SCHEMES*]
// AD: personal preferences; to emphasize the view mode
BACKGROUND_SCHEME="Gray"
ENABLED=1
VIEW_FILTER="B"
BACKGROUND_SCHEME="Light"
ENABLED=1
VIEW_FILTER="A"
which would successfully override just the two switches in the
"common" .ini file. Now, it does not seem to work anymore.

This should work. But there was a bug in the original release which
caused problems with background schemes associated with a view
filter. This has now been fixed and a new version (with the same
build number) has been uploaded.
This will also fix Gyorgy's problem with the same functionality...
Best regards,
alex

[Agustin E. Bolzán]

I have upgraded Figures&Tables and found that only the first figure in
the tree shows the caption, the rest only show the number
"11".....before upgrading, with the old macro, I had no problems, even
with 8.2

Agustin

[WinEdt Team]

Augustin,

Post by Agustin E. Bolzán
I have upgraded Figures&Tables and found that only the first figure
in the tree shows the caption, the rest only show the number
"11".....before upgrading, with the old macro, I had no problems,
even with 8.2

Open Tree.ini (Options Interface) and find

BRANCH="Figures-TeX"

What do you see under CAPTION? It should be:

CAPTION="%[!|Exe('%b\Macros\Gather\FigTab.edt');|];%-0"

Is it or does it look differently?

If so, does a copy if FigTab.edt exist in your local settings (as
indicated above)?

If yes: delete it; default one will work with these settings but
old one will not...

Best regards,

alex

[Agustin E. Bolzán]

Dear WinEdt Team,

Post by WinEdt Team
Open Tree.ini (Options Interface) and find
BRANCH="Figures-TeX"
CAPTION="%[!|Exe('%b\Macros\Gather\FigTab.edt');|];%-0"

Yes! I can see it

Post by WinEdt Team
If so, does a copy if FigTab.edt exist in your local settings (as
indicated above)?

No, there is only one file and it is located in Macros/Gather folder

Post by WinEdt Team
If yes: delete it; default one will work with these settings but
old one will not...

So...I cannot understand what is happening....am I the only one with
this problem?

Best regards,

Agustin

[Agustin E. Bolzán]

No problems now with Figures and Tables!...I do not know why but I
closed and restarted Winedt and then all worked as expected....

the only problem I discovered is that drag&drop does not work now,
i.e. every time I drop a file in the editor, nothing happens....I am
now investigating this issue....it happens, up to now, only in one
computer not in the other....

best regards,

Agustin mailto:***@gmail.com

[WinEdt Team]

Augustin,

Post by Agustin E. Bolzán
No problems now with Figures and Tables!...I do not know why but I
closed and restarted Winedt and then all worked as expected....

Hmm.... there has to be mote to it than that. Anyway, it works for
you now and we will never know what exactly happened before...

Post by Agustin E. Bolzán
So...I cannot understand what is happening....am I the only one
with this problem?

Well, you seem to be a magnet for problems.

Post by Agustin E. Bolzán
the only problem I discovered is that drag&drop does not work now,
i.e. every time I drop a file in the editor, nothing happens....I
am now investigating this issue....it happens, up to now, only in
one computer not in the other....

Restart the computer. This usually has nothing to do with WinEdt.

Sometimes (eg. after something "bad" happened to Windows Explorer
or IE) this functionality is lost and it affects ALL applications:
dragging from explorer simply ceases to work.

I cannot recall this ever happening on my Win8 and I would not be
able to do anything about your particular situation anyway. There
is little you can investigate here (beyond restarting the computer
and checking how dragging (the same file on the same computer)
works into other applications [32-bit or 64-bit might be relevant
if the problem persists on one computer]...

Best regards,

alex