Thanks but be prepared...
Posted: Sat Aug 13, 2016 9:50 pm
First off, I'd like to give you all a HUGE thanks for the back to school sale. It was perfect timing and very much appreciated here! We grabbed another license and I'm currently working on integrating SBIE into the PC [PC in my wording being 'a' computer not necessarily a desktop] our kid(s) will be using shortly.
I already ran into one hiccup regarding 'User Accounts' but managed to figure that one out just as I was writing a PM to nag Craig about it [my mistake there]. Be prepared though I may soon have thoughts or questions with areas or scenarios I haven't encountered on my own machine and of course I will desire quick aid! :P So yeah, end of this random rant... /yay 'Anything Else'
P.S.:
First question:
I normally visit often [and hate auto-updates for anything in general (even windows), I like to control all that on my machine] and so I normally have auto-updates disabled.
I currently have the SBIE beta on that PC so will it still get an update alert for an official release with a beta installed?
Second Question:
I'm hoping to have the ability to delete certain sandboxes on close (which requires sbiectrl at this time) [along with quick recovery? maybe?] but want to avoid having the icon displayed/accessible in the tray for my kid(s) account.
Is there any type of /hide option where it could remain running and operational but not be in the notification area to be seen or messed with?
I've already enabled the edit and admin only options for the ini so it can't be disabled/changed etc but would like to take it a tad further to the mostly 'invisible' but still fully operational sector. I'm tempted to loop back around to an old suggestion where I thought deletion should be handled by the primary sbie service anyway but for this instance I'd really be happy with just a way to prevent sbiectrl from being shown in the notification area on the initial start (logon for a specific user) through a simple option/flag/switch... eg altering a specific run link or adding a switch such as /hide:kid [kid being a username in this case] that could be appended to the startup shortcut or someplace in the ini that is later processed but still results in no tray sbiectrl for said user via that path. Obviously I'm not asking for anything that prevents them from launching sbiectrl manually and seeing it later but for kid(s) the age I'm talking about that's unlikely to happen anyway.
I already ran into one hiccup regarding 'User Accounts' but managed to figure that one out just as I was writing a PM to nag Craig about it [my mistake there]. Be prepared though I may soon have thoughts or questions with areas or scenarios I haven't encountered on my own machine and of course I will desire quick aid! :P So yeah, end of this random rant... /yay 'Anything Else'
P.S.:
First question:
I normally visit often [and hate auto-updates for anything in general (even windows), I like to control all that on my machine] and so I normally have auto-updates disabled.
I currently have the SBIE beta on that PC so will it still get an update alert for an official release with a beta installed?
Second Question:
I'm hoping to have the ability to delete certain sandboxes on close (which requires sbiectrl at this time) [along with quick recovery? maybe?] but want to avoid having the icon displayed/accessible in the tray for my kid(s) account.
Is there any type of /hide option where it could remain running and operational but not be in the notification area to be seen or messed with?
I've already enabled the edit and admin only options for the ini so it can't be disabled/changed etc but would like to take it a tad further to the mostly 'invisible' but still fully operational sector. I'm tempted to loop back around to an old suggestion where I thought deletion should be handled by the primary sbie service anyway but for this instance I'd really be happy with just a way to prevent sbiectrl from being shown in the notification area on the initial start (logon for a specific user) through a simple option/flag/switch... eg altering a specific run link or adding a switch such as /hide:kid [kid being a username in this case] that could be appended to the startup shortcut or someplace in the ini that is later processed but still results in no tray sbiectrl for said user via that path. Obviously I'm not asking for anything that prevents them from launching sbiectrl manually and seeing it later but for kid(s) the age I'm talking about that's unlikely to happen anyway.