Auto-Save &Auto-Close after inactivity

I'm new to JavaScript, so please be patient. I am using Acrobat XI
I have a document that I am trying to have auto-save and auto-close after 10 minutes of inactivity. I've found where I would enter the JavaScript under the document actions, and I see the "Will Save" and "Will Close" functions, but I guess I don't understand what JavaScript I need to put in these fields to get them to do what I want.
I can get the document to run JavaScript that will close the document after being open for 10 minutes, but I need it to save and close after 10 minutes of inactivity. Is this possible, and if so how do I go about this?
Thanks SO MUCH in advance.

The "Will Save" and "Will Close" events are only triggered after an action to save the PDF or close the PDF has started.

Similar Messages

Auto-Save and Auto-Recovery

I hope the is a differnence between auto-save (as listed in you document properties) and Auto-Recovery (as set in Prefs). I would like some "protection" but I don't want flash saving over my file unless I tell it to save. I got burn last night while "experimenting" and and did a "revert" only to find that flash had saved over my file, what a pain. I went to find the "recovery" file only to not find one anywhere. My search on the net are conflicted with wheather or not these 2 features are the same. In my case both items where checked and both set to 10min (the default). soooo....
Please tell me that Auto-Recovery is different, is that it doesn't save over my file, ie it keeps a real back-up someplace, AND where i can find this "recovery" file. ?
This feature seems strange, why not do a std auto back-up to a user selected number of versions in a user selected location ?
Thanks
Joel

Thanks. After poking around for a while I kinda figured this out. I was just glad to find out I could get some kind of "back-up" function from Auto Recovery, because "Auto Save" is a nightmare. I can't understand where anyone would want to use this feature at all. Anything that saves over what your working on before your ask for the file to be saved is looking for trouble. I found it out the hard way. I had "auto Save" on and after messing around trying a few different things, none of which worked or I liked, I thought I would simply close and re-open the original file only to find "auto save" had saved over my original file. I can't see any place where this feature would be anything but a pitb. If they want a auto save feature it should be saving versions of the original (up to a user specified number of instances) in the seperate folder. Never under any curcumstances should the original file be saved over unless the users presses SAVE. Auto recovery would be more useful if it didn't erase everytime you restarted the app. Flash needs to look at the back-up and versioning systems that AE and PPro use.
It's one of those things that bother you about the whole "suite" concept. Adobe owns all these apps and while some of them do play well together to an extent, for the most part it is still a collection of indiviuals. While there have been some changes to get the "look" of the apps to be close, the actual functioning of the UI in the differnt apps isn't where it needs to be. There needs to be a Suite "czar" that makes all the apps do std UI things the same using the same keys etc. for example AE, PPro, Flash, Photoshop, fireworks, all use different keys to zoom in/out or of your image/stage/comp/viewer/monitor window ie main workspace or to enable the mouse "wheel" for zooming. PPro still refuses to use the spacebar to toggle the hand tool like every other "suite app". anyway. a std system for back-up and versioning is need across the suite.
thanks
Joel

Feature Request: Auto-save in Background

Here's a feature request I've submitted. If you agree, please submit your request to:
http://www.adobe.com/go/wish/
*******Enhancement / FMR*********
Brief title for your desired feature:
Background Auto Save
How would you like the feature to work?
Auto-save would work just as it does today, except it would work as a background process, as it already does in Photoshop (without the Autosave popup getting in the way of the edit).
Why is this feature important to you?
The current autosave feature is terrifice and expected in any application today, but the current autosave popup dialog is useless. It only has a "Cancel" button. What's the point? I can't imagine when I would ever want to cancel an auto-save. And let's say I *did* want to cancel. The dialog is only on screen for a second or so. That's not enough time for user interaction, but it is just enough time for my work to be interupted, and for me to potentially hit the enter key as I go to Render something at precisely the same time.

Hi cscouper2013,
Thanks for taking the time to point out that my BSODs might be a problem with my RAM! Yes, I'll test it with the program you mention.
cscooper2013 wrote:
While I'm thinking of it, too. Sometimes Premiere will do an auto save only moments after I've done a hard save. That also seems like something to address in the next auto save feature update. If I have my autosave increment set to 5 minutes, then it seems to me there's no need to do an autosave for another 5 minutes after my last manual save.
I fully agree! That's something I requested during the CS5 beta program. I requested that every time a user does a manual save, the Autosave reset its counter. So for example, if the delay is 10 minutes between auto saves, and the user does a manual save two minutes before the next scheduled autosave, the autosave counter resets to 10 more minutes. But with the better solution of the current project constantly being saved after each edit, as Jim suggested, this feature wouldn't even be needed anymore.
MonkeyEatsMonkey wrote:If Premiere could "borrow" that functionality, while still retaining a "save as" option for versioning, I feel like we'd have the best of both worlds. It would even make dynamic linking more seamless, since changes wouldn't require saving. Any thoughts from the community on this?
That would be a perfect solution IMO! And yes, retaining the 'Save As' option would be very important!
I also like the idea of automatic versioning/backups (could be renamed to 'versions' since with a constantly saved project file, automatic 'backups' would no longer be necessary.
To resume, based on what has been discussed in this thread, I believe these would be the ideal saving options in Premiere:
Autosaving of every edit in the background without slowing down editing performance (as suggested by Jim).
Ability to create a user defined number of automatic backup versions, by setting maximum number of versions and time intervals (as is currently the case with Premiere).
In other words, the current project file would constantly be updated as the user edits. The automatic backups/versions would be created at user defined intervals.
Users would retain the ability to create a copy of the current project at any moment through the 'Save As' and 'Save a Copy' commands that already exist in Premiere.
Pop-up Auto-save dialogue boxes and the 'Save' command would be a thing of the past!
IMO, this would truly give us the best of both words as MonkeyEastMonkey suggests: constant saving as per FCPX, with the comprehensive versioning options Premiere currently offers.
Anything missing?

Feature request: auto-save timer reset

The auto save timer currently runs continuously: every n minutes, it auto-saves if the project has changed. It should auto-save n minutes after the last save whether auto or not. That is, any save action should reset the countdown timer. Also, auto-save shouldn't start while a manual save action is in progress.

There is a better way.
http://forums.adobe.com/thread/1369232?tstart=0

Auto-close after signature?

I would like to know if it's possible to auto-close a document after signing and saving. I've been having an issue at the company with two (or more) people having a document open for electronic signature at once, and of course only one of them can save at a time. If a document could close automatically after signature, this problem would greatly be reduced.
If there is a code that allows auto-closing the file after the signature save prompt and the person signs, I would love to know about it.
Is this possible?
Win XP, LS 8.2, Acrobat Professional 9.4

Ok tried that, and get the message, "Object contains a feature not supported by target version"
The Report log says, "Target Version does not support PostSign event".

Upgraded to Lion. Numbers is stalling to auto save after every keystroke. Isn't auto save supposed to run in the background?

Upgraded to Lion. Numbers is stalling to auto save after every keystroke. Isn’t auto save supposed to run in the background?

It's supposed to save when the processor isn't triggered by the user. If you type slowly, time between two strokes may be sufficient to allow it to start the save process.
Yvan KOENIG (VALLAURIS, France) lundi 17 octobre 2011 23:27:47
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community

After I upgraded to OSX Mountain Lion, QuickTime no longer auto names and auto saves, my recorded files.

After I upgraded to OSX Mountain Lion, QuickTime no longer auto names and auto saves, my recorded files.

Try using one of these video players. VLC usually works with most files.
Video Player - Divx
Video Player – Flip4Mac
Video Player - VLC

After I upgraded to OSX Mountain Lion, QuickTime no longer auto names and auto saves, my recordings

After I upgraded to OSX Mountain Lion, QuickTime no longer auto names and auto saves, my recorded files.

HI,
In Message Menu > Preference > Accounts you should at least have the iMessage Account (Which is Enabled) and th Bonjour one that most likely is not.
After that if you had iChat type AIM valid Screen Names or Jabber IDs in an earlier OS then the System Preferences > Mail, Contacts and Calendars should list them and have them set to be used with Messages.
There is a vague chance that you have not set these up yet (you can do it in Messages or Mail, Contacts and Calendars)
Once you have a t least one other "Account" other than th iMessage one in Messages then the Buddy List option will appear next to CMD and 1 in the Window menu list.
NEXT
If you go to the General Section of the Messages Preferences you can unlink several Buddy lists if you have them (By default they are shown as one gathered Buddy list)
I Have several Accounts logged in (AIM valid and Jabber ones)
Uploaded with Skitch!
And I separate them in to individual lists which then gives me this in the Window Menu
Uploaded with Skitch!
8:06 PM Thursday; August 2, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Photoshop cc auto-close after opening.

I am new here with adobe cc 2014. i have tried using my photoshop once but after that i can't use it because it auto-closes after loading the program. I don't know how to fix this problem. Can anyone help me with this?

Good day!
Please read these and proceed accordingly (restoring Preferences might be of special interest):
http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
http://forums.adobe.com/docs/DOC-2325
Regards,
Pfaffenbichler

Auto logout or disconnect of Lync 2013 client after inactivity

Is there any way to configure the Registry or perhaps a GPO so that Lync 2013 clients running on Windows 7 will auto logout or disconnect from the server if they have been inactive after a certain amount of time? Searched around and could not find anything.
I found the link below but it uses Preferences which have undesirable side affects.
http://unifiedme.co.uk/2014/01/lync-2013-group-policy-enforce-ringtones-centrally/

Hi,
There is no method naturally to auto logout of Lync 2013 after inactivity. You may need to configure auto-logoff Windows after idle time to log off the Lync can check
the thread below to configure auto-logoff Windows:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/2d618fdb-faf7-41a1-9207-ff07b8d29091/how-to-automatically-log-off-idle-users?forum=winserversecurity#c7c21990-73b4-41ac-a9b5-4d571372ec10
Or you may need to custom your own Lync client, you can post the question on MSDN Lync SDK forum. Thank you for your understanding.
Here is the link to MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/communicatorsdk/threads
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Reader 11.0.0.3 auto closes after an install

I downloaded Reader 11.0.0.3
When I open it prompts me to accept the license
The license window stays up bu the application closes within a second.
Opening any pdf file post that point allows the application to open... then auto closes after 1 sec
I have installed with Chrome, without Chrome
I have rebooted between installs
Google search led me to Eula.exe - which is the accept license
That has no affect
I am running Windows 7 64 bit on a Lenovo laptop

Two more things things to try...
Can you open Adobe Reader by itself? If so, try disabling Protected Mode [Edit | Preferences | Security (Enhanced)].
It could even be a malware issue; see http://helpx.adobe.com/acrobat/kb/reader-core-dll-error.html

FCP 7 lost sequence after exporting - auto save vault not working

I started a project a couple of days ago. Today I worked from 11.00 - 20.00 hrs. I exported at 20.00 hrs. to compressor (i got a self contained compressed .MOV file out of that pffff)
But then, returning to FCP 7, the sequence I exported (and worked on all day) was completely empty. Everything in the project folder is still there, but the cuts / edits in the main sequence i worked on are all gone.
Inside the Auto Save Vault are only four saves from between 11.00 - 11.30 hrs. (not properly every 5 min.) and one from 20.00 hrs. The one from 20.00 hrs. is a version that also has the empty sequence. The whole afternoon FCP 7 seems to have made no auto saves, even though i set the Auto Save Vault to "every 5 min." in the preferences. Auto Save Vault files (of this same project) from a couple of days earlier are all there inside the Auto Save Vault folder.
Tried already: Looked inside the other two locations where i have autosave folders of other projects but the files were not there either.
Had a Tiff in the sequence, and a couple of very simple text-motion things.
Can anybody tell me whats going on?
And if there is a way to retrieve?
Never had this before, is this a FCP7 Yosemite issue?
Thanks in advance!

could be a yosemite issue. Hard to know. fcp was never meant to work in Yosemite, so it's hit or miss.
Autosave misbehavior can happen and resetting your fcp preferences usually solves the problem. Digital Rebellion makes a great utility to reset your preferences (and it's free).
www.digitalrebellion.com

Would a 347 MB file be slow? Auto save and auto type turn off?

I am doing an art inventory and add jpegs of the art. I don't resize them they range from 750k to 3MB. I guess if it is slowing the program down i should? It currently is 267 rows by about 18 columns.
Thanks in advance.
Oh can I turn off auto save and auto type? That may help. How do I do that?

Done.
Enter Scrip Editor
paste the posted script
File > Save > as Script on the Desktop
Move the script to the folder :
Macintosh HD:Library:Scripts:Folder Action Scripts:
CAUTION, you will be asked to enter your pasword.
Create a folder to do the job. I named mine Normalized. I created mine on the Desktop where it's easy to reach.
Go to :
Macintosh HD:Library:Scripts:Folder Actions:
Double click the alias : Configure Folder Actions
Below the left column, click
navigate to select your new folder
Below the right column, click
select the script image - normalize400.scpt
After that, drag and drop a picture file onto your folder.
The original will be move in the folder Originals (isn’t it original ?)
and a reduced copy 400 x height will be stored in the folder Normalized images.
And now, here is the script :
--{code}
Image - Normalize
This Folder Action handler is triggered whenever items are added to the attached folder.
The script rotates the image counter-clockwise (left).
Copyright © 2002–2007 Apple Inc.
You may incorporate this Apple sample code into your program(s) without
restriction. This Apple sample code has been provided "AS IS" and the
responsibility for its operation is yours. You are not permitted to
redistribute this Apple sample code as "Apple sample code" after having
made changes. If you're going to redistribute the code, we require
that you make it clear that the code was descended from Apple sample
code, but that you've made changes.
modified by Yvan KOENIG (VALLAURIS, France)
2011/12/08
This version normalize pictures so that
(1) the greater dimension become the width one (rotate left if needed)
(2) this greater dimension is ruled by the property maxWidth defined below.
property maxWidth : 400
-- set it to fit your needs
property done_foldername : "Normalized Images"
property originals_foldername : "Original Images"
property newimage_extension : "jpg"
-- the list of file types which will be processed
-- eg: {"PICT", "JPEG", "TIFF", "GIFf"}
property type_list : {"TIFF", "GIFf", "PNGf", "PICT", "JPEG"}
-- since file types are optional in Mac OS X,
-- check the name extension if there is no file type
-- NOTE: do not use periods (.) with the items in the name extensions list
-- eg: {"txt", "text", "jpg", "jpeg"}, NOT: {".txt", ".text", ".jpg", ".jpeg"}
property extension_list : {"tif", "tiff", "gif", "png", "pict", "pct", "jpeg", "jpg"}
on adding folder items to this_folder after receiving these_items
          tell application "Finder"
                    if not (exists folder done_foldername of this_folder) then
make new folder at this_folder with properties {name:done_foldername}
                    end if
                    set the results_folder to (folder done_foldername of this_folder) as alias
                    if not (exists folder originals_foldername of this_folder) then
make new folder at this_folder with properties {name:originals_foldername}
                              set current view of container window of this_folder to list view
                    end if
                    set the originals_folder to folder originals_foldername of this_folder
          end tell
          try
                    repeat with i from 1 to number of items in these_items
                              set this_item to item i of these_items
                              set the item_info to the info for this_item
                              if (alias of the item_info is false and the file type of the item_info is in the type_list) or (the name extension of the item_info is in the extension_list) then
                                        tell application "Finder"
--set name of this_item to "YK#" & (text -4 thru -1 of ("0000" & i))
                                                  my resolve_conflicts(this_item, originals_folder, "")
                                                  set the new_name to my resolve_conflicts(this_item, results_folder, newimage_extension)
                                                  set the source_file to (move this_item to the originals_folder with replacing) as alias
                                        end tell
process_item(source_file, new_name, results_folder)
                              end if
                    end repeat
          on error error_message number error_number
                    if the error_number is not -128 then
                              tell application "Finder"
activate
display dialog error_message buttons {"Cancel"} default button 1 giving up after 120
                              end tell
                    end if
          end try
end adding folder items to
on resolve_conflicts(this_item, target_folder, new_extension)
          tell application "Finder"
                    set the file_name to the name of this_item
                    set file_extension to the name extension of this_item
                    if the file_extension is "" then
                              set the trimmed_name to the file_name
                    else
                              set the trimmed_name to text 1 thru -((length of file_extension) + 2) of the file_name
                    end if
                    if the new_extension is "" then
                              set target_name to file_name
                              set target_extension to file_extension
                    else
                              set target_extension to new_extension
                              set target_name to (the trimmed_name & "." & target_extension) as string
                    end if
                    if (exists document file target_name of target_folder) then
                              set the name_increment to 1
                              repeat
                                        set the new_name to (the trimmed_name & "." & (name_increment as string) & "." & target_extension) as string
                                        if not (exists document file new_name of the target_folder) then
-- rename to conflicting file
                                                  set the name of document file target_name of the target_folder to the new_name
                                                  exit repeat
                                        else
                                                  set the name_increment to the name_increment + 1
                                        end if
                              end repeat
                    end if
          end tell
          return the target_name
end resolve_conflicts
-- this sub-routine processes files
on process_item(source_file, new_name, results_folder)
-- NOTE that the variable this_item is a file reference in alias format
-- FILE PROCESSING STATEMENTS GOES HERE
          try
-- the target path is the destination folder and the new file name
                    set the target_path to ((results_folder as string) & new_name) as string
                    with timeout of 900 seconds
                              tell application "Image Events"
launch -- always use with Folder Actions
                                        set this_image to open file (source_file as string)
                                        set {oldW, oldH} to dimensions of this_image
                                        if oldH > oldW then
                                                  set {oldW, oldH} to {oldH, oldW}
rotate this_image to angle 270.0
                                        end if
                                        set |échelle| to maxWidth / oldW
                                        if |échelle| < 1 then scale this_image by factor |échelle|
save this_image as JPEG in file target_path with icon
close this_image
                              end tell
                    end timeout
          on error error_message
                    tell application "Finder"
activate
display dialog error_message buttons {"Cancel"} default button 1 giving up after 120
                    end tell
          end try
end process_item
--{code}
Yvan KOENIG (VALLAURIS, France) jeudi 8 décembre 2011 21:25:33
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community

Auto Save & Versions a bust ... bring back "Save As"

Having upgrading my laptop to Lion and discovering that along with Auto Save and Versions comes the elimination of the Save As command and the inability to turn these new features off I will be reinstalling Snow Leopard and definitely not upgrading our household's other machines.
The new scheme is cumbersome in it's insistence that I duplicate the document to give it a new name.
I do not like the idea that previous drafts are accessible from inside the document by anyone who might access my machine.
I do not like that new versions are created and saved without my say-so. I do not like that I am not asked to save/discard changes upon quitting.
In short, the 248 great new features provide me little reason to upgrade but the 249th and 250th features are deal-breakers. Until they can be turned off I will not use Lion.

RichBP wrote:
File>Duplicate creates a new duplicate of the changed file. You then have to go back after you've duplicated, and "revert" the file or you will have two identical changed files. If you want to leave the original untouched, and forget to "revert" before you close the file, you're original file will be lost and your original file will be identical to your new "duplicate" file.
Or you could just click the "Duplicate and Revert" button:

Text Edit auto save

Starting recently whenever I edit a text file with Text Edit a second file appears in the same folder of the main text file, with the +same name+ but with a tilde appended to the file name just before the .txt postfix.
I understand this is the result of the Text Edit auto-save function, however, different from the previous behaviour (probably before the 10.5.5 MacOS update) these auto-save files are no longer automatically removed when the application is successfully closed.
Does anybody have the same behavior ?
Is this a correct behavior ?
Thanks
Piero

They should close after saving or quitting the application. I have no idea where the tilde came from. Have you created a fresh account to test? If it works in TextEdit in the test account try this by logging back into your problem account...
Quit TextEdit, go to Users/yourname/Library/Autosave Information/com.apple.TestEdit.plist and move it to your desktop then relaunch Test Edit? You may also need to move Users/yourname/Library/Preferences/com.apple.TestEdit.plist to your desktop also.
-mj

Auto-Save &Auto-Close after inactivity

Similar Messages

Maybe you are looking for