forum home | register | profile | members |search | faq
homepage | lost password? | chat room
|
|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > What if Helix Can No Longer...? > Give an Option for Save and Log | You are not logged in. Login or Register. |
| Pages: 1 |
|
| Author: | Topic: Give an Option for Save and Log | |||
Matt Posts: 107 Registered: 2003-02-16  mstrange@mac.com  |
 Posted: Jul 07, 2003 6:40:10 pm    
In order to avoid one unpleasant hurdle, we're considering making logging automatic.. any time you are running Server, Engine, or User Mode RADE, logging will happen with no user action required to activate it.
|
|||
keVin Posts: 30 Registered: 2003-04-09 |
 Posted: Jul 08, 2003 10:04:24 am
I have noted a few unpleasant situations in testing where logging presented problems. (Crash during AE process before all exceptions were trapped. As logging attempted to recreate files Collection was rendered useless. Had to go to a backup.) It would be preferred if a checkbox is added to the Preferences dialog for toggling the auto-on feature. It could be defaulted to on. |
|||
dkuchta Posts: 40 Registered: 2003-04-09 |
Posted: Jul 09, 2003 9:58:02 am
Although I wouldn't squawk too much if it were always automatic, I agree that there are times when it would be nice to be able to turn it off. I would, however, like to see the logging function be handled more "automatically". In other words, when going into Design mode, Helix should just ask if you want to save, but logging should be automatically turned off. When going back into User mode, logging should be automatically re-enabled. I've been burned by this before when I forgot to turn logging back on and lost data after a crash. Proxy-Authorization: Basic NTAyMjYxNTA6ZG96MTZlcg== -Dan Kuchta
|
|||
lucidlee Posts: 18 Registered: 2003-04-09 |
Posted: Jul 09, 2003 11:25:28 am
I assume that this a system level feature in OSX that you would be accessing, in which case it will also presumabley be well behave wrt the Helix app. So, why not do it? Matt sez: No, nothing 'system level' about it. Just looking for a way to simplify a chunk of code that would require serious rewriting. If you never tried it, you probably don't know that Helix doesn't store path info for the logfile, so if you put it in any directory other than with the collection itself, Helix can't find it next time you open the collection. Add to that the fact that all FS dialogs have to be changed to Nav Services, and you should understand that 90% of the "off/on" code has to be tossed and rewritten. We can simplify the code and remove the above mentioned problem that happen when a user forgets to reactivate Save and Log by just making it automatic. I should have mentioned before (but forgot) that we do want to make it a preference, along with the ability to choose the volume it goes on (similar to the scratch file control in Photoshop) so those who want to wring a bit more speed out of Helix can. - Edited by Matt on: Jul 09, 2003 12:40:55 pm
|
|||
| binfordjc Posts: 5 Registered: 2003-07-09 |
Posted: Jul 09, 2003 2:30:37 pm
Matt, Your last post clarified the subject well. So, instead of saying that we want to get rid of Logging, perhaps we should say we want to change it to Auto-Logging to help us get to 6.0 faster, with the option of revisiting the question later. (Of course, the coding should be done so as to enable revisiting later.) Your Preferences comment indicates that the Logging will be Automatic unless turned off in Helix Preferences. Could life be sweeter? Not much, but perhaps have two OFFs: one for Design mode, one for User Mode. Thus the Auto-Off (Design Mode) would provide immediate relief, should the new code produce the problem Kevin mentioned. The Auto_ON (User Mode) would solve the problem Dan mentioned having suffered some 2nd or 3rd degree burns in times past when he forgot to turn Logging back on.
|
|||
Sven Posts: 24 Registered: 2003-04-09 |
Posted: Jul 10, 2003 5:51:38 am
If logging happens automatically when moving to design mode, on a RADE application used for development work , it would be preferable to switch the automatic feature off. I asume we could then move back and forth between design mode and user mode as we are used to. As to 'wringing more speed' out of a running server application by running it without logging, it is not something that I intend to do. I could see some use for it, however if that server was just doing processing, not any storing of data, possibly in a setup where it served a special purpose. So please, it would be good to keep that option as well. As an aside: In switching a lot between design and user modes during development, it would be useful to have a setting which would cause Helix RADE to automatically compile when going from design to user mode. This because everything needs to be compiled to enable AppleEvent. Sven
|
|||
| dkuchta Posts: 40 Registered: 2003-04-09 |
Posted: Jul 11, 2003 9:53:45 am
Matt: based on your latest post, it sounds great! Count me as a vote: yea! p.s. - no idea why my posts now have tha "Proxy_Authorization..." string at the end. I'm on vacation and coming into the web through a very different route so who knows?
|
|||
| dougb Posts: 2 Registered: 2003-08-05 |
Posted: Aug 05, 2003 8:19:22 pm
Automatic logging would be great! One related feature we would like: the ability to control the quit/leave dialog in helix client - via a preference. As we are always tweaking our collections, we never save structure. It is confusing to my staff to not save, when we tell them to save all other files. The dialog option could simply ask if you wanted to quit/leave - or not. This is not a huge priority, but it would make training easier!
|
|||
| Robin Posts: 10 Registered: 2003-04-16 |
Posted: Sep 18, 2003 12:20:20 am
I see no need to be able to turn logging off except in design mode. I would be very happy if was always off in design mode and always on when running on the server. I have also been burned when I forgot to turn logging on again when putting a collection back on the server after some structure revisions. On the need for quiting clients without saving the structure. I have the opposite situation. My staff are trained to immediately quit and save, then re-launch, whenever they get the "reload structure" dialog on launch. Otherwise, when running on an unsaved structure, I find we get slowdowns and freezes.
|
| Pages: 1 |
|
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |
