How to avoid reopening many application windows when starting iMac?

everytime i start iMac, many application windows open automatically. how can i do to make sure it wont reopen these windows? thank you for your help.

Take a look at this thread:
https://discussions.apple.com/thread/3197405?start=15&tstart=0
And these:
http://osxdaily.com/2011/08/01/turn-off-resume-per-app-in-mac-os-x-lion/
http://hints.macworld.com/article.php?story=20110918051930924

Similar Messages

  • Avoid opening last application/window when starting

    hi,
    im currently using osx lion, I have a behaviour to shut down my computer and let the application that currently running closed by itself during shut down (including massive finder windows). But when I turn on my computer again, those windows reappears. While it might be a nice feature, its really bothering for me. Is it possible to tell osx lion NOT to open the last windows opened during shut down?
    Im also curious if its possible to do this on safari. I have limited bandwidth, and opening the last windows is annoying.
    can anyone help me on this one?
    Thanks in advance.

    Welcome to the iOS world of nonthinking, wherein the OS decides everything for you, whether or not that's what you want. Salient details described in http://www.apple.com/macosx/whats-new/features.html#resume 
    See these for steps to resolve:
    http://hints.macworld.com/article.php?story=20110918051930924
    http://osxdaily.com/2011/08/01/turn-off-resume-per-app-in-mac-os-x-lion/

  • How do I change the default windows when starting indesign

    The default when I start up Indesign is “only the applications bar is showing”. I would like to be able to change the default to having the Tools and Control showing as well as a few windows like pages, styles, swatches, hyperlinks – not ALL of the windows. I’ve tried setting this up when I first open up Indesign and no documents open. But it still changes back to the default whrn I reopen Indesign. Is there anyway to change this?

    launch indesign--open and position the panels you want--then go to the workspace menu and save your workspace--then, when you launch Indesign it will appear like your saved workspace
    see these articles:
    http://www.tech4pub.com/2012/10/24/indesign-cs5-5-tip-work-efficiently-with-custom-workspa ces/
    http://help.adobe.com/en_US/indesign/cs/using/WSa285fff53dea4f8617383751001ea8cb3f-6d6ea.h tml#WSa285fff53dea4f8617383751001ea8cb3f-6d6ca

  • How do I keep an application window hidden when not accessed?

    I have an application running constantly to control my FW audio interface outputs etc. I use system events applescripts to control it's UI with a USB controller (PowerMate) - and that by necessity brings the application window to the front every time accessed. That's fine.
    But I want to have a script that hides this application window when it's not used after 2 seconds. Maybe there is an "on idle" script that could run to check if that window is visible. I imagine something including lines like this:
    -- a routine that checks if the window is visible every 2 seconds or so.
    -- the window reference
    window "Studio Monitor Express" of application process "Studio Monitor Express"
    -- if it is, then hide it
    -- for hiding the window/app
    keystroke "h" using command down
    -- if it's not, then ignore
    I'm not sure whether to use system events or finder events etc. I have a bunch of other apps running obviously, but I just want this particular window to disappear when not needed.

    I solved it. I know. Easy:
    on idle
    tell application "System Events"
    set visible of process "Studio Monitor Express" to false
    end tell
    return 2
    end idle

  • How to avoid printing a blank page when there is 'no data' in the report.

    how to avoid printing a blank page when there is 'no data' in the report.

    try like this
    if@section:IND=1
    this template
    end ifsectionbreak
    if@section:IND=2
    this template
    end if

  • How to avoid shut down BPELPM Server when creating a user?

    Hi,
    How to avoid shut down BPELPM Server when creating a JAZN user and after doing changes to user-properties.xml?
    Thanks,
    Jorge

    this configuration is only supported on a midtier - there is a work around for a standalone install, nevertheless I would not recommend this for production ..
    if this is NOT a production enviroment - I can try to get you the information .
    /clemens

  • How do I eliminate the flashplayer window when it interferes with my viewing (e.g.) Weather Channel?

    How do I eliminate the flashplayer window when it interferes with my seeing the full window in (for example) the Weather Channel? I use Windows Vista, IE9, flash version 11.6.

    What you mean by "flashplayer window"; can you post a screenshot?  See http://forums.adobe.com/thread/1070933

  • Cannot see the application window when the program is run

    I wrote a java GUI using Jbuilder. I cant see the application window when i run the program. THe program compiles successfully but the application window pops up only showing the blue title bar and minimize maximaize and x out icon on it. I done see my GUI or anything below the 1 inch long blue title bar. Can someone plese tell me what i am doing wrong. Thanks.

    A quick look-up in the API confirms that pack is not deprecated. Setting the size of the window to a specific size is quite a bit different than what pack accomplishes. Pack determines the preferred size of all of the components, lays out the layout manager and then sets the size of the window based on the size of the components inside of it. Calling setSize, however, will force the window to be a specific size no matter what the components want and thus creates a window that is probably not the right size for the components inside of it.

  • Re: How do I keep an application from being started morethan once?

    Here are some quick ideas. None of them should be too hard to implement,
    although each has some drawbacks.
    1. Have a login server track who is logged on, and if there is already a
    logon for a given user or a given machine, then deny the application
    startup. The nice thing about this is that a user will not be able to have
    multiple logins even by going to another machine. Then again, this may not
    be so nice, and you also get a possible single point of failure on the
    login server for which you will have to prepare.
    2. Drop to the operating system, and get a list of processes for the client
    machine. If the name of one of them matches the name of application that
    is being run, then deny startup. This avoids a network hit, but requires
    some OS specific code. Also, a clever user could change the name of an
    executable to get around this. Note that a user could have another login
    on another machine.
    3. Write to a file on the local machine. You can hide the file in some
    suitable place, and can also scramble some information so that a user
    cannot get around having this file present by reading from the file at
    startup and then writing to it. Based on the state of your application,
    the file will have some scrambled information indicating if an instance of
    an application can be started. If you retain the write lock (i.e. do not
    close) the file for the duration of the application, you increase your
    security at the risk of a confused user if the application gets terminated
    without releasing the lock. Depending on the OS where the client will run,
    this could be an issue. If you like this option, perform some experiments
    first on all configurations of an example client machine to determine the
    behavior. Again, this only works to prevent an extra login on a single
    machine, not system wide.
    If you are not concerned about your users hacking around too much and don't
    care about a login on another machine, I would opt for some version of
    number 3. Otherwise, I would venture number 1.
    Regards
    CSB
    At 07:47 AM 2/18/98 -0500, Martin G Nystrom wrote:
    A user can launch an application, then launch it again. How do we make it so
    that the user can only run one instance of the application?
    Martin Nystrom
    Eli Lilly and Company
    ([email protected])
    Curtis Bragdon, Senior Consultant, Forte Software
    [email protected]
    Voice Mail: (510) 986-3807
    Paging: (888) 687-6723
    "I've seen dozens of triggering towns." - Richard Hugo

    Yet another quick and dirty solution is to use local ExternalConnections.
    This is a single instance per machine solution.
    Example is attached.
    (See attached file: TestOne.pex)
    [email protected] on 02/18/98 10:01:07 PM
    Please respond to [email protected]
    To: [email protected]
    cc: [email protected]
    Subject: Re: How do I keep an application from being started more than
    once?
    Martin,
    there are two ways to read your question
    (a) no more than one instance of an application per machine
    (b) no more than one instance of an application per "user"
    now if a user has only one machine, and your system has "userids" and you
    only want
    one active "session" per "user" then the distinction is irrelevant.
    However, many systems
    let people share logins, so a token based thing enforcing one login will be
    problematic.
    The downside of #1 approach suggested by Curtis happens when a machine gets
    hosed without "logging" the user off the security system, then they can't
    get in until their ticket expires or a sysadmin gets involved. Should be
    manageable, however. But this enforces one application
    instance per user, unless you check both for the presence of an active
    token for that user as well as the presence of a token tied to that
    particular node name. Otherwise there is nothing to prevent the same user
    from launching the app again and logging in as a different user. This is
    definitely the best approach of the bunch, and can be adapted for either
    (a) or (b).
    Suggestion # 2 won't work unless the application is built as a compiled
    client,
    since the process name will be 'ftexec' and not the "name" of the
    application. And it doesn't
    prevent a user from launching the app from a different machine (or people
    sharing logins). So again it depends on what you are trying to achieve.
    #3 also only prevents multiple instances per machine, not necessarily by
    user. Of course
    most people don't have multiple machines. The point is that you may be
    trying to
    prevent your users from sharing logins. In which case the file thing won't
    do it.
    Some other ideas:
    1. You could, however, enforce one application per machine using the
    installed partition agent's ExecutingPartition instrument name. As long as
    the user doesn't run the app in a different environment, you can have the
    app check at startup time if there is another
    ActivePartition running under the same InstalledPartition name.
    (ActivePartitions are child agents
    of InstalledPartitions).
    2. use the ObjectLocationManager and bind a simple object into the naming
    system using a naming scheme such as
    /MyApplication/MyNode or
    /MyApplication/MyUserId
    the presence of either one would indicate that another instance of that
    application is running on either that machine or that user. Of course
    these have to be cleaned out, and subject to similar downside as
    alternative #1. So you'd essentially be using the forte naming system as a
    distributed lock manager (ouch).
    3. Have the application remove the shortcut to launch it upon startup, and
    recreate it when it is finished, or move it to a hidden place. There it
    is - the worst idea I've ever come up with. Don't
    do this!
    Regards,
    John
    From: Curtis Bragdon <[email protected]>
    Date: Wed, 18 Feb 1998 16:36:58 -0500
    Subject: Re: How do I keep an application from being started more than
    once?
    Here are some quick ideas. None of them should be too hard to implement,
    although each has some drawbacks.
    1. Have a login server track who is logged on, and if there is already a
    logon for a given user or a given machine, then deny the application
    startup. The nice thing about this is that a user will not be able to have
    multiple logins even by going to another machine. Then again, this may not
    be so nice, and you also get a possible single point of failure on the
    login server for which you will have to prepare.
    2. Drop to the operating system, and get a list of processes for the client
    machine. If the name of one of them matches the name of application that
    is being run, then deny startup. This avoids a network hit, but requires
    some OS specific code. Also, a clever user could change the name of an
    executable to get around this. Note that a user could have another login
    on another machine.
    3. Write to a file on the local machine. You can hide the file in some
    suitable place, and can also scramble some information so that a user
    cannot get around having this file present by reading from the file at
    startup and then writing to it. Based on the state of your application,
    the file will have some scrambled information indicating if an instance of
    an application can be started. If you retain the write lock (i.e. do not
    close) the file for the duration of the application, you increase your
    security at the risk of a confused user if the application gets terminated
    without releasing the lock. Depending on the OS where the client will run,
    this could be an issue. If you like this option, perform some experiments
    first on all configurations of an example client machine to determine the
    behavior. Again, this only works to prevent an extra login on a single
    machine, not system wide.
    If you are not concerned about your users hacking around too much and don't
    care about a login on another machine, I would opt for some version of
    number 3. Otherwise, I would venture number 1.
    Regards
    CSB
    At 07:47 AM 2/18/98 -0500, Martin G Nystrom wrote:
    A user can launch an application, then launch it again. How do we make itso
    that the user can only run one instance of the application?
    Martin Nystrom
    Eli Lilly and Company
    ([email protected])
    Curtis Bragdon, Senior Consultant, Forte Software
    [email protected]
    Voice Mail: (510) 986-3807
    Paging: (888) 687-6723
    "I've seen dozens of triggering towns." - Richard Hugo
    John Jamison
    Vice President of Technology
    Sage IT Partners, Inc.
    415 392 7243 x 306
    [email protected]

  • How do I prevent multiple applications opening on start up with Lion?

    how do I prevent multiple applications opening on start up with Lion?

    It's the Resume feature of Lion:
    Managing Mac OS X Lion's application resume feature.
    If you shutdown your computer you should get a dialog asking if you want applications to resume on the next startup. Simply uncheck the box to prevent that from occurring. Open General preferences and uncheck the option to Restore windows when quitting and re-opening apps. You can also install a third-party utility to control resume features on individual applications: RestoreMeNot or Application State Cleaner.

  • How to swf auto fit to screen when start

    how to swf auto fit to screen when start without any menu bar or window screen, i had use adobe flash player convert swf to ex, will fit to screen works in exe format?

    Dear Josephine,
       There is no option the way you want of autofit. Rather while opening the CSV in excel u can do the required formatting.
    Regards,
    Deva.

  • How can I implement a comfirmation window when closing javafx application?

    hi,guys
    I'd like to add a confirmation window when user is closing my javafx application,if user click yes, I will close the application,if no ,I wouldn't close it ,how can I implement this function?
    primaryStage.setOnCloseRequest(new EventHandler<WindowEvent>(){
                   @Override
                   public void handle(WindowEvent arg0) {
                        try
                             //todo
                        catch(Exception ex)
                             System.out.print(ex.getMessage()+"\r\n");
            });

    Hi. Here is an example:
    import javafx.event.ActionEvent;
    import javafx.event.EventHandler;
    import javafx.geometry.Pos;
    import javafx.stage.*;
    import javafx.scene.*;
    import javafx.scene.paint.Color;
    import javafx.scene.layout.*;
    import javafx.scene.control.*;
    public class ModalDialog {
        public ModalDialog(final Stage stg) {
         final Stage stage = new Stage();          
            //Initialize the Stage with type of modal
            stage.initModality(Modality.APPLICATION_MODAL);
            //Set the owner of the Stage
            stage.initOwner(stg);
            Group group =  new Group();
            HBox hb = new HBox();
             hb.setSpacing(20);
            hb.setAlignment(Pos.CENTER);
            Label label = new Label("You are about to close \n your application: ");
            Button no  = new Button("No");
            no.setOnAction(new EventHandler<ActionEvent>() {
                public void handle(ActionEvent event) {
                       stage.hide();
            Button yes  = new Button("Yes");
            yes.setOnAction(new EventHandler<ActionEvent>() {
                public void handle(ActionEvent event) {
                       stg.close();
             hb.getChildren().addAll(yes, no);
             VBox vb =  new VBox();
             vb.setSpacing(20);
             vb.setAlignment(Pos.CENTER);
             vb.getChildren().addAll(label,hb);
            stage.setTitle("Closing ...");
            stage.setScene(new Scene( vb, 260, 110, Color.LIGHTCYAN));       
            stage.show();
    }Test:
       import javafx.application.Application;
    import javafx.event.ActionEvent;
    import javafx.event.EventHandler;
    import javafx.scene.Group;
    import javafx.scene.Scene;
    import javafx.scene.control.Button;
    import javafx.scene.paint.Color;
    import javafx.stage.Stage;
    import javafx.stage.*;
    * @author Shakir
    public class ModalTest extends Application {
         * @param args the command line arguments
        public static void main(String[] args) {
            Application.launch(ModalTest.class, args);
        @Override
        public void start(final Stage primaryStage) {
            primaryStage.setTitle("Hello World");
            Group root = new Group();
            Scene scene = new Scene(root, 300, 250, Color.LIGHTGREEN);
           primaryStage.setOnCloseRequest(new EventHandler<WindowEvent>(){
                   @Override
                   public void handle(WindowEvent arg0) {
                                    arg0.consume();
                        try
                         ModalDialog md = new ModalDialog(primaryStage);
                        catch(Exception ex)
                             System.out.print(ex.getMessage()+"\r\n");
            primaryStage.setScene(scene);
            primaryStage.show();
    }

  • How do I get my application window back on my desktop?

    I use an extra LCD display with my G5 which I have temporarily disconnected.
    When I use Sorenson Squeeze 4.3 it usually appears on the second screen but since I have disconnected it, the application window has disappeared off-screen. I have made sure that the computer doesn’t still think that the extra display is connected but this makes no difference.
    Please Help
    G5   Mac OS X (10.4.9)  

    Open the Script Editor in the /Applications/AppleScript/ folder and run the following:
    tell app "Sorenson Squeeze 4.3"
    set bounds of window 1 to {122, 132, 897, 517}
    end tell
    Press the Run button; changing the first number in the second line may be needed. This method does not work with all applications.
    (21042)

  • How to avoid the transport request popup when changing real-time load behav

    Hello experts,
    I'm often switching between the two loading mode, and I already worked in systems where I don't have the popup for transport request : (so I guess there is a possible tuning anywhere)
    How to avoid the "asking for a transport request" popup in BW when changing real-time load behaviour of an infocube
    Thanks in advance, I will save precious time
    Guillaume P.

    Hello Krishnan,
    i tried to switch all object types from "not changeable" to "changeable original", but still get the popup when switching cube loading mode.
    Do you know the particular object type to manage ?
    Hello Vishnu,
    same thing, whatever the option is (switch on / off standard) I have the transport popup.
    Anyway thanks for your try.

  • How can I stop Yosemite resizing windows when I turn off my screen?

    I have a 2012 mac mini running Yosemite. It's hooked up to an LG TV via the thunderbolt port and an adapter.
    When I turn off the TV and the turn it back on again, all of my windows get moved over to the leftmost 2/3rds of the screen (approx). It's super annoying constantly moving windows back to where I left them.
    Can someone explain why this is happening and suggest how I can fix it?

    Windows stuck in top left hand corner of screen

Maybe you are looking for