Hi Marina,
This has happened to me a couple of times, I neglected to save a new workspace and lost all the work. Please consider having MC automatically save workspaces on closing MC. Perhaps I am the only one who has done this but it would preclude forgetful people like me from losing their work. Thank you for any consideration about this request.
Tim
SUGGESTION
- TJ
- Posts: 7745
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1033 times
- Been thanked: 2224 times
MC is poor in this area. It should default to automatically offering to save changed workspaces on exit like TS (and almost every application that modifies data files).
At the moment, you have three options:
1. Always offer to save even if the workspace hasn't changed, which is an unnecessary nag.
2. Never offer to save, just save automatically. Potentially dangerous if you have made a change you don't want to save.
3. Never offer to to save, and never save. Potentially dangerous as could lose work as happened in this case.
None of these are satisfactory. The default state should be to only save a workspace if it has changed. Please match TS and general software design standards.
At the moment, you have three options:
1. Always offer to save even if the workspace hasn't changed, which is an unnecessary nag.
2. Never offer to save, just save automatically. Potentially dangerous if you have made a change you don't want to save.
3. Never offer to to save, and never save. Potentially dangerous as could lose work as happened in this case.
None of these are satisfactory. The default state should be to only save a workspace if it has changed. Please match TS and general software design standards.
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
- RobotMan
- Posts: 375
- Joined: 12 Jul 2006
- Location: Los Altos, California, USA
- Has thanked: 31 times
- Been thanked: 13 times
- Contact:
Hi brendanh,
A technique that I learned from Jimmy Snowden of the "Omega List" (He was an expert with TS2000i and uses MC now and might even be in this forum), is to save workspaces by name and date, then if you screw something up, just re-open a backup. Also, You might try creating a template and everything is instantly set up the way you like it.
I have set MC to automatically save when I shut down. I really like it.
Hope that helps.
A technique that I learned from Jimmy Snowden of the "Omega List" (He was an expert with TS2000i and uses MC now and might even be in this forum), is to save workspaces by name and date, then if you screw something up, just re-open a backup. Also, You might try creating a template and everything is instantly set up the way you like it.
I have set MC to automatically save when I shut down. I really like it.
Hope that helps.
This is not an issue. Once a user created the workspace, they save it. They are the responsible for saving it, not the software (maker).
If I consciously change my workspace, and not saved it, it's my problem. But if the workspace changed by accident, then not being asked to save it, is the right software behavior.
Less pop-ups is a good thing.
General design standards are mediocre at best and becoming increasingly obsolete. An example would be a conventional Blackberry interface compared to interface of the iPhone.
I am not affiliated in any way with TS Support by the way.
Cheers,
If I consciously change my workspace, and not saved it, it's my problem. But if the workspace changed by accident, then not being asked to save it, is the right software behavior.
Less pop-ups is a good thing.
The problem with the general design is that you getting general user experience, which is frustration for majority of computer users today. That creates a burden for tech support, eventually driving Up the cost of software. General design standards can be observed in it's full grace here http://www.ted.com/index.php/talks/davi ... sells.html.Please match ..... general software design standards.
General design standards are mediocre at best and becoming increasingly obsolete. An example would be a conventional Blackberry interface compared to interface of the iPhone.
I am not affiliated in any way with TS Support by the way.
Cheers,
Last edited by geizer on 28 Jan 2009, edited 1 time in total.
Bob, it wasn't me that had the original problem. I'm glad you are happy with the auto save option, however I sometimes make changes to workspaces that I don't want to save.
My suggestion isn't earth shatteringly important, but when you open a workspace to look at a chart, then close it without changing it and are prompted to save your changes, it is an annoying nag that reminds you that MC is an unpolished product.
My suggestion isn't earth shatteringly important, but when you open a workspace to look at a chart, then close it without changing it and are prompted to save your changes, it is an annoying nag that reminds you that MC is an unpolished product.
brendanh,
I do challenge the general design standards in a much broader sense - as a paradigm if you will, which is trying to substitute the user ability to do mental work consciously. General software design standards is the result of inability of software companies to make a tough decision about each and every software detail - once, so their users would not face the same tough choice every day. In this context the Multicharts behavior concerning the subject is right on the money.
Users edit workspace once, and use it 365 days.
When you actively creating/customizing workspaces you choose "Save always". When you're done editing you choose "Never Save". In all other cases you're working with real money and take full responsibility for your actions. Such software behavior forces you to take responsibility for your actions, so your computer no longer controls you. You limited to choices, none of which will take away from you the responsibility for your actions.
Perhaps TS Support could add another option like this:
Always ask all users the same pop-up questions assuming users don't know what they are doing.
All I am just saying is this: if software does not ask questions, it assumes that user in front of the computer knows what they are doing. Nothing else.
I do challenge the general design standards in a much broader sense - as a paradigm if you will, which is trying to substitute the user ability to do mental work consciously. General software design standards is the result of inability of software companies to make a tough decision about each and every software detail - once, so their users would not face the same tough choice every day. In this context the Multicharts behavior concerning the subject is right on the money.
Users edit workspace once, and use it 365 days.
When you actively creating/customizing workspaces you choose "Save always". When you're done editing you choose "Never Save". In all other cases you're working with real money and take full responsibility for your actions. Such software behavior forces you to take responsibility for your actions, so your computer no longer controls you. You limited to choices, none of which will take away from you the responsibility for your actions.
Perhaps TS Support could add another option like this:
Always ask all users the same pop-up questions assuming users don't know what they are doing.
All I am just saying is this: if software does not ask questions, it assumes that user in front of the computer knows what they are doing. Nothing else.
geizer, I don't understand your point. Are you saying that the general software design standard to only be prompted to save data files when they have changed is incorrect, and we should be prompted every time?
- TJ
- Posts: 7745
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1033 times
- Been thanked: 2224 times
I take your point. I'm not denying there should be an option to disable the prompt completely and rely on experienced users to remember to save if they want. It would be dangerous to make this the default though, as new users may forget and lose their work.
In TS, the default is to only prompt if the workspace has changed. So because I usually CTRL-S before exiting a workspace that I'm developing, I rarely see the prompt anyway and it effectively behaves like the no-prompt option. In MC, if I CTRL-S then immediately exit a workspace, it still prompts to save.
In TS, the default is to only prompt if the workspace has changed. So because I usually CTRL-S before exiting a workspace that I'm developing, I rarely see the prompt anyway and it effectively behaves like the no-prompt option. In MC, if I CTRL-S then immediately exit a workspace, it still prompts to save.
- Marina Pashkova
- Posts: 2758
- Joined: 27 Jul 2007
Could you please list the bugs we're overwhelmed with?brendanh,
Indeed, prompt to save workspace, if modified would be useful for some users. It's seems that TS Support is overwhelmed with existing bugs to be fixed.
Meanwhile I remain waiting for the MC Gold release. See what they will come up with.
Marina,
This was just my humble opinion. I could only list those that I reported myself, but will not reiterate, since they have received enough attention from your tech support team. The thing is, we (the users) don't know, which of the issues previously reported on this forum have been already fixed in your developer's Lab and which have not. And we will not know it until the next release comes out. Besides I am using a Beta version, so that is expected, I would think.
This was just my humble opinion. I could only list those that I reported myself, but will not reiterate, since they have received enough attention from your tech support team. The thing is, we (the users) don't know, which of the issues previously reported on this forum have been already fixed in your developer's Lab and which have not. And we will not know it until the next release comes out. Besides I am using a Beta version, so that is expected, I would think.