Default.pgp

Asbjørn Værnes

 I seem to recall that a few (main) versions back, Bricscad would prompt me to overwrite default.pgp or keep the original upon first start after a program update. This was convenient, but never happens anymore. Now, Bricscad sometimes overwrites default.pgp without asking, and sometimes leaves it unchanged. 

Would it be possible to have the old prompt back, as I basically never want my default.pgp overwritten.

Robt Deans

I remember being prompted with last upgrade.

That said, It is always good practice / prudent to back up default.pgp, default.lin, default pat and any other customized files before upgrading should any files be overwritten or something go awry.

Scott McKenzie

What I think we need, and maybe this is possible, is the ability to create a custom.pgp file that is loaded after the default.pgp file.  This way, BricsCAD could change everything as they add new features yet the user still has full control over their shortcuts.  In terms of headaches after program updates or adding customizations, editing the default.pgp file is about the same as editing the default menu files and adding your custom menus to them. I once spent two full days at my last place of employment trying to move all of the customizations added to the default .mnu file to a new custom one before we upgraded our software.  

I would suggest that users do not edit their default.lin or default.pat files, rather create custom files for these items and store them in a folder who's location is listed in your support file search paths.  It makes backing things up (or setting up new users with a company template) very easy and avoids issues with potential changes made to the default files when the software is upgraded.

John Gaunt

I agree, don't try and edit or replace default files.

And custom linetypes, hatches etc I believe won't appear for any user downstream without the custom files containing the definitions.

Tacking on a custom menu makes transferring versions simple (I maintain mine in mnu format), but I would argue a tack on pgp file would likely clash with default shortcuts even if those aren't all your personal preference. Changes to the default pgp are often around advances in the program and it's a long job working yours around those in the default.

I maintain a few 'shortcuts' as small lisps defined within the on_doc_load.lsp - they each do more than one thing, using one or two letters or numbers as a command.

It's not hard to work out if one clashes with a pgp defined shortcut.