Sometimes I think that those instructions should not be written by people who have been part of the development of a programme and therefore know the ins and outs of it. For most users here the responsive programmes represent a whole new way of thinking and approaching a task, and experts tend to take shortcuts where new users, especially those who were VSD users, need more details.
Having said that, if you play with a programme long enough, you'll always be able to get under the hood of it.
Then while saving after editing a while, it crashed and the resulting file was corrupt and could not be read any more.
I'd suggest adding an automatic rolling backup - when you save a file, it would rename the earlier good file as .bk1, .bk2, .bk3, etc. for about 9 generations. This way when something like this happens, we can revert to a good file.
My application is to have a slide show of artifacts found at an archaeology site. There could be a couple hundred slides and users may want to go to several slides without having to view all of them. If someone is interested in pipe stems, for example, I would like to direct them to the slider on the website with several suggested slide numbers to go to.
Now, instead of feeling daunted, like "Ugh, I've got a whole other program to learn," it's like all the work I do in learning one is being rewarded in the other.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.