If a feature sounds like it is in any way UI related it won't be available in the legacy build.įeatures that can be set using the ini manually will work in the legacy build, but you will have to configure them in the ini.Īny security or compatibility improvements are implemented in the shared components and are available in booth builds. To help you differentiate in the change log for yourself:
So ideally all users should move to the Plus build as its now no longer missing any features in comparison with the classical UI. I have to be efficient with my time and every minute not wasted on cumbersome 90's technology is a minute I can spend on actually relevant core functionality. First make a backup of your C:\windows\sandboxie.ini just in case Than uninstall old sandboxie and when prompted opt for keeping the sandboxie.ini Than install sandboxie plus release, it will use the existing sandboxie.ini with all the settings and configurations. Second, and more important, its immeasurably more convenient to create and maintain Qt based UI's that those obsolete MFC based UI's from the late 90's. I will not add any new major features to SbieCtrl.exeįeatures like Snapshots, user interactive prompts that will be expanded upon in future builds, and other will not be supported when using SbieCtrl.exeįor once the UI is really dated and not that user friendly, for example you need to save each page in the sandbox settings before you can switch to an other, etc. As the classical UI is deprecated and provided only for legacy use there is no point in splitting the change log.
0 kommentar(er)
