English > Feature Suggestions

connecting database file to specific skin...

(1/2) > >>

katleeh:
It occurred to me the other day that having a specific skin load as default when certain databases are loaded would be a handy feature. After all, I have seperate databases for lots of things and would view each one using a different skin. Likewise there should be a way to attach specific custom fields to a database.

This would seem like the easy method: have pvd start a new data file which would store information specific for each database such as the skin used, custtom fields, etc.

- katleeh

rick.ca:
Custom fields are not an issue—they're created and saved in the database. Settings (like the skins to use) are saved in pvdconf.ini. Two versions of that may be used by running one in Portable Mode. Doing so forces the program to use a configuration file found in the Installation folder instead of the Application Data folder. If you need more than two different configurations, use multiple installations (each one in portable mode).

katleeh:
Um, rick.ca that's a little to much to have to do just to use a different skin. Having to reinstall a program each time I want to use a different skin sounds confusing at best.

- katleeh

rick.ca:

--- Quote ---Having to reinstall a program each time I want to use a different skin sounds confusing at best.
--- End quote ---

It sure does! But I didn't say anything remotely suggesting that. You can have any number of independent PVD installations—as long as they're all used in portable mode only.

nostra:
You can make a copy of the configuration file with the same name as the database file and it will be loaded automatically when you change the database.

Navigation

[0] Message Index

[#] Next page