How do I properly update BED?

Started by Quin, June 18, 2024, 11:44:26 AM

Previous topic - Next topic

Quin

I started storing my entire bed/bcx config in a git repository, that way I always have my bcx.ini and anything else I could possibly want. On a new machine? Just grab it down from gitolite.

djsb

I have just updated my version and did (and do regularly) the following (I just overwrite everything).
1/ Changed the path of Pellesc in C:\bed\Bat\Pelles\Config.bat to match my installation path.
2/ I opened (right click then open with "open with" -> Microsoft HTML help executable and then UNCLICK  "ask before running this app" (or similar wording) both C:\bed\Help\BCXHelp.chm and Win32.chm

Quin

Ah, so it is mostly just the executable that changes, unless others are mentioned. Gotcha, thanks!

MrBcx

Quote from: Quin on June 18, 2024, 11:44:26 AM
I installed the new update to BED (3.62 I believe), by extracting the zip to c:\BED, the same place where my old version was. However, I had to go and manually replace the paths in all my batch files again. Is there some way around this, or do I have to do this after every update?

Existing BED users should unzip updates to a Temp folder then overwrite the old BED.exe with the new BED.exe.

Additionally, I usually summarize what was updated, like updated syntax files. 

Not mandatory to update those but those nice to have.

This was my most recent post on the subject:

https://bcxbasiccoders.com/smf/index.php?topic=420.msg5668#msg5668

BED version 3.62 has been uploaded.

Find it at the usual link:  https://bcxbasiccoders.com/smf/index.php?topic=420.0

' Added ALT-DownArrow and ALT-UpArrow for shifting focus between
' the current editor window and the OUTPUT window.
' ALT-DownArrow will open the OUTPUT window, if it is closed.

' Added focus handling code to the main Event Loop

' More additions to the Win32 syntax file



Quin

I installed the new update to BED (3.62 I believe), by extracting the zip to c:\BED, the same place where my old version was. However, I had to go and manually replace the paths in all my batch files again. Is there some way around this, or do I have to do this after every update?