LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: arinko

This has happened twice to me.

Saves .brg file and some weird error msg says error in .ini file and disconnects from the server.
When I close and open the brg again, something about syntax error on some line (no server connection).
Close down LAE and server.
Open LAE with new blank brg. No server connection.


To reinstall a working LAE, I have to use Revo Uninstaller to remove every bit of the installation and then reinstall.

I then try to open the same brg file I was working on, Syntax error on some line.

To try to salvage most of my custom nodes, I opened the .brg file in notepad++.

I noticed the new parameter I declared was

prop:X_MOC_ACCESS_TYPE_NAME
=true

(broken into 2 lines)

instead of

prop:X_MOC_ACCESS_TYPE_NAME=true

and

editor:propdef=X_MOC_ACCESS_TYPE_NAME
|boolean|1||None

(broken into 2 lines)

instead of

editor:propdef=X_MOC_ACCESS_TYPE_NAME|boolean|1||N one


Is this a Saving or trimming (getting rid of hidden special characters in a variable name) bug?
Why should this corrupt/affect the LAE .ini file?

Once I made the 2 broken lines into 1 line. I could open the file with all the missing custom nodes.

Edit: LAE Desktop 6.1.1

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Is there any chance that you are typing (or pasting) random text into the TraceField box on the menu? The value for TraceField is stored in BRE.INI
There is a known bug that if you type too much text into that box and/or random combinations of the characters {} or [] (or quotes) that it can break the BRE.INI file.
If you do break BRE.INI, the values for the server farm definitions are also inaccessible, which would keep you from connecting.

One of my top suggestions is to keep a backup copy of BRE.INI on hand. (and watch out when you hit Paste)

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: arinko

Will this also cause the brg to have lines split into 2 lines thereby causing the syntax error?

eg.
prop:X_MOC_ACCESS_TYPE_NAME
=true