-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Plus UI] Multiple issues with custom box order #1358
Comments
Infact there is a "Move Box / Group" option, but for some reason I can't get it working anymore on 0.9.8, 0.9.8b, 0.9.8c and 0.9.8d:
|
@isaak654 @olliebean Also column Name seems to not have Descending order.. possibly intended / replaced by custom order |
Thanks - I hadn't noticed the "Move Box/Group" option. Seems easier to use the Alt+Up/Down keys than the menu entries. Things were moving a bit erratically at first, a hangover I think from the order I had them in in Sandboxie Control, but after fiddling with it for a while it seems to be working properly now. Spoke too soon - just after posting that, I created a new box and suddenly all my previous changes to the box order were undone - including some groups I'd created, they were gone and all the boxes I'd put in them were back in the main list. So I guess this is a bug, after all. |
I think this is another sorting issue. If you came from Sandboxie Classic, you will need to replace |
Workaround # 2 :
Issue # 3 : The Move box/group context menu will create more than 1 [None] on related actions |
Thanks, the trick seems to be to quit and restart Sandboxie Plus after making any changes to the layout. It doesn't seem to be saved under |
Just discovered there's a second I've deleted the old |
1 is intended you can only move up and down in the non alphabetic view, rest will be fixed in the next build |
In Sandboxie Control, the option "Set Layout and Groups" allows a custom ordering of the boxes, so I can have my most used ones at the top of the list. Is there a similar option in Sandboxie Plus?
The text was updated successfully, but these errors were encountered: