Closing Applications with red X prevents restarting of applications

Hi,
first of all, I switched from PC to Mac just 2 days ago, so forgive my lack of common iKnownledge of macLingo.
My system is OS X 10.5.6 running on the latest MacBook (standard model).
I performed the software update.
As former windows user (and every other OS user, btw.) I assumed that clicking on the red X button closes the application, which it apparently doesn't. I found out the pressing the button with the swirly symbol + Q is the way to go.
Anyway, sometimes I just want to close an application with a click, so I push the X button and restart the closed application later, although - as I understand it - the application is still loaded (which is indicated by the small white dot in the dock). Just to be clear: Closing e.g. Safari with the red X closes the window but doesn't minimize it to the dock.
However, every so often a red-X-closed application remains white-dot-active but can't be restarted or maximised again, unless I first go to the dock and close it manually by use of the context menu.
This is an eminently stupid behaviour of OS-X if that was intended.
So, ist there a fix for this ? Or a way to tell the red X to close an application for good ?
What's the use of three colored window control buttons anyway, if two of them just basically minimize an application ?
Thanks for the help.
PS: Maybe I should mention that this behaviour is not reliably reproducable. Sometimes it works, sometimes it doesn't. It happens way too often to ignore, though.
Message was edited by: arotto

I was hoping you'd say that. It is as it's supposed to do in that particular case at least.
Now just so you know, (though I suspect you already have some idea). That red cross will as a general rule close just that window. In some cases, (usually where the app only ever has that one window), clicking the X will close the app down, otherwise the app will still run in the background. This is normal. To close the program down you need to Quit it, ⌘Q.
You are right that it can't be maximised again, +that's because you didn't minimize the window you closed it.+ To minimize you need to press ⌘M, or click the minus symbol.
Strictly speaking the buttons do not both minimise, one maximises.
I think the minus button is there to put the window in the dock.
I think the plus button is there to alternate between minimum and maximum window sizes while that particular window is active on the desktop.
I think once you understand how it works you should find it consistent. Give it a shot and let us know.
Message was edited by: gumsie

Similar Messages

  • My battery drained. Screen shows battery with red line but doesn't seem to be recharding after 20 min.  Should I wait or do a hard restart? I haven't backedup in ages and don't want to lose pics, contacts etc.

    My battery drained. Pluged in to wall but screen shows battery with red line but doesn't seem to be recharding after 20 min.  Should I wait longer or do a hard restart? I haven't backedup in ages and don't want to lose pics, contacts etc.  Will a hard restart wipe all that out?

    Agree with Richard:
    -Your device needs both the CR and LF. To accomplish this:
    option 1: Concatenate the "end of line" string constant (this is a combination of CR and LF, located in the string pallete) to all your outgoing commands. Make sure in the "Visa configure serial port" the "Termination character enable" flag is false.
    option 2: Concatenate only a CR to your command's strings. Make sure in the "Visa configure serial port" the "Termination character enable" flag is TRUE AND that the termination character is set to 10 (meaning LF) which I think is the default.
    Details can be seen in this link:
    http://digital.ni.com/public.nsf/allkb/862567530005F09C862565BE005AB500
    "Adding Termination Characters to VISA Serial Writes in LabVIEW"
    Interesting would be to configure the serial port to accept not one but two termination characters. The above links refers to the document "Developer Zone Tutorial: Termination Characters in NI-VISA.", where this is supposed to be possible. The document however is 404'ed.
    If someone find a working link please post it.
    Regards

  • My Imac is showing gray screen with red line when booting and restarts again

    My Imac is showing gray screen with red line when booting and restart again, I can load it in windows 7 safe mode with red lines across the display, pls help

    The graphic card is damaged. You can't do anything more than taking your computer to an Apple Store or reseller and getting your graphic card replaced.
    Sometimes, when the graphic card is damaged, operating systems can't start. That's caused because the drivers that make the graphic card work detect an error, telling the operating system that the graphic card is unusable, so the operating system can't start and it restarts. However, you can start in safe mode because operating systems use a basic driver in this startup mode

  • WHY DO PICTURES-NOT ALL-IN MY EMAIL APPEAR IN A BLANK BOX WITH RED 'X'-NO PICTURES ON MY PC AND LAPTOP BUT DO SHOW UP ON MY 4G PHONE?

    PICTURES DO NOT SHOW UP IN EMAILS ONLY BLANK BOX WITH RED 'X' IN UPPER LEFT HAND CORNER

    Photostream only syncs photos over Wi-Fi, make sure you are connected to Wi-Fi to begin with.
    Photostream only syncs when the camera app is closed, ensure it is closed.
    Photostream only syncs when the battery is above 20%, try recharging the device
    Try disabling photo stream on your device (settings > iCloud), restarting your device and then re-enabling photo stream.
    Note: disabling photostream and re-enabling it will result in any photos that are currently in the photostream album on your device, that are older than 30 days old, not being added back.

  • MBP not closing applications upon shutdown

    I was very happy with Lion, until I noticed that my applications are not closed on shutdown. When my computer restarts every application that I do not force quit prior to shutdown opens.
    Any help would be appreciated.

    This is not a bug, it is a feature !  From Apple's description of Lion:
    Now apps you close will reopen right where you left off, so you never have to start from scratch again. And when you install software updates, you no longer need to save your work, close your apps, and spend valuable time setting everything up again. With Resume, you can restart your Mac and return to what you were doing — with all your apps in the places where you left them.
    In the System Preferences --> General pane, there is an option you can unclick that says "Restore windows when quitting and re-opening apps".  That may help.

  • My iMac G5 (with Sight) won't restart

    My iMac G5 (with iSight) won't restart, every time I restart it the screen goes black and nothing happens, not even the startup chime sounds and the keyboard and mouse won't work, I can't even restart the PMU nor do anything, about a minute later the fans turn on making a very loud sound so I have to turn it down by holding the power button, after some time I manage to turn it on and everything works perfectly, but when I restart it again the samething happens, I've tried everything that appears in the support page, not even the hardware diagnostics detected a problem, even when I'm reinstalling Mac OS X when it comes to the part where it restarts itself the same thing happens.
    Does anyone have a suggestion?
    Thanks

    Contributed by Fumiaki Kawashima;
    There are many reasons to become unable shutting down or restarting from Apple Menu. Some were explained by other posters.
    Most importantly, loginwindow (the parent process is launchd.) close out the user session, continue to set the device permissions and user preferences to their defaults in a restart action, or the process power off the system in a shutdown action. However, the issue proves that somewhere in those routines cannot be performed.
    Users authentication system seems to be intact because you can restart or shutdown from the login window. However, the admin account authenticated by the Tiger security systems could confuse somehow and affect loginwindow process for setting up the user environment. This may result in interfering with the process for the shutdown and restart mentioned above.
    Test if you can shutdown from the keyboard-- Holding down controloptioncommand keys, and then press the eject key.
    Check if the loginwindow plists are corrupted. To do this test, remove the followings to temporary folders on the desktop, and shutdown from the keyboard shortcut combination. Restart the computer to test the recurrence.
    /Library/Preferences/com.apple.loginwindow.plist
    /Users/HOME/Library/Preferences/com.apple.loginwindow.plist
    Try disabling Login Items for third-party applications via the Accounts system preference, if any.
    Verify whether any third-party kernel extensions (including device drivers) interfere with the loginwindow hooks process-- Start up with a Safe-mode, then test the Restart from Apple Menu to see whether it works. Also, boot into a Single-user mode, and test if "reboot" command is available from the BSD layer. The I/O Kit API for software developers provides a shutdown hook so that ".kext" troubleshooting may need to be considered. Besides, some bad programmed extension may not be unloaded automatically at a shutdown or restart.
    If the computer is configured with Irish language Input method and/or third-party Irish keyboard, try disabling them to test.
    A third-party application or custom script may interfere with the loginwindow hooks for the Shut Down or Restart. For example, if you install an application that prevents casually powering down a system, the Shut Down and Restart buttons may not work. Also, if you install a P2P file sharing application, try uninstalling it.
    As last resorts, troubleshoot a bad RAM and consider "Erase and Install" solution.
    OPTION:
    Post a part of system.log that indicates events from "localhost kernel[0]: standard timeslicing quantum is 10000 us" to the next same line.
    This may help to narrow down because restarting or shutting down the system process can initiate the procedure programmatically by sending an appropriate Apple event to Mac OS X Tiger's system process (loginwindow).
    Likewise, check console.log whether any failures is reported.
    Corrections:
    Most importantly, the loginwindow (the parent process is launchd.) close out the user session, continue to set the device permissions and user preferences to their defaults in a restart action, or the process power off the system in a shutdown action.
    However, the admin account authenticated by the Tiger security systems could confuse somehow and it may impact on the loginwindow process for setting up the user environment. This may result in interfering with the process for the shutdown and restart as mentioned above.
    Addendum:
    If you post a copy of system.log, consider to edit the Ethernet interface ID to a fake value.
    API = Application Programming Interface
    Cheers!
    DALE

  • Solo Button in Channel Strip with Red Line

    Solo Button in Channel Strip with Red Line through it and it won't solo?
    How'd it happen and how do you get rid of it?
    Thanks!

    Try This----From the Manual
    Logic Pro, Express: Solo Safe mode may not remain disabled for a particular channel strip
    Symptoms
    In certain projects, "Solo Safe" mode for a channel strip may enable each time you load the project, even after you disable it and save the project.
    Resolution
    When a channel strip in Logic is "Solo Safe", it remains audible, even when other channel strips are soloed. Solo Safe is indicated by a diagonal red line through the solo button on a channel strip.
    You can manually toggle the solo safe status of a channel strip by Control-clicking its solo button. There are times when you may find that a particular audio channel strip in a project reverts to solo safe mode when you load the project, even after you manually disable solo safe. Here is why that may happen and steps you can take to prevent it from occurring.
    A Logic project contains a special audio channel strip used for pre-listening to audio in the Sample Edit window, Audio Bin, and Loop Browser. When you create a Logic project from one of the factory templates, this channel strip is assigned to "Audio 256". This channel strip stays in solo safe mode so that you can always preview audio. The image below shows the channel strip for a new, empty project.
    If there is no audio channel strip in a project assigned to "Audio 256", Logic will use the highest-numbered available audio channel for pre-listening. When the project is loaded, that channel strip will be put into solo safe mode. You may find this happens in older projects that you open in Logic 8, or in cases where you have deleted the "Audio 256" channel strip in a Logic 8 project. To prevent this from affecting channel strips you are using in a project's arrangement, follow these steps:
    Choose Window > Environment.
    From the Environment window menu, choose New > Channel Strip > Auxiliary. A channel strip will appear in the environment.
    Select the channel strip. It will highlight.
    In the Device parameter box in the upper left of the Environment window, click the arrows to the right of "Channel" and choose Audio > Audio 256 from the menu.
    Select the text tool, click on the name below the channel strip and name it "Prelisten".

  • IMac Reboots Are Needed More Frequently With Lion - Any Preventive Ideas?

    My two-year old iMac was totally stable when running Snow Leopard. Since installing Lion I am noticing a new phenomenon. Various tasks I perform with Lion are now causing my computer to freeze from time to time, and requiring a reboot to get things working correctly again. It's turning out that I need to reboot about once a day to keep everything running right, while I used to be able to just put my computer to sleep each day, for weeks at a time, with no need to restart. Is anyone else noticing this? Any ideas?

    How much RAM is installed? How much free space do you have on your hard drive? Have you tried reinstalling Lion:
    Reinstalling Lion
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alterhatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion: Select Reinstall Lion and click on the Continue button.
    Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

  • Documents rows cannot be closed concurrently with the other document modify

    Hello Experts !!!
    Now  i am using SAP BUSINESS ONE 2007 B PATCH LEVEL 19.
    problem is that previously i was using patch level 4.
    when i was using patch level 4 , i used to punch sales order.
    now when i upgraded to patch level 19 .SAP is not allowing to update the so which was punched in patch level 4.
    SCENARIO
    1.so is raised of 10 pcs in patch level 4.
    2.delivery was punched of 5 pcs.
    3.now sap upgraded to patch level 19.
    4.now m modifying that so.
    5.particular so which was of 10 pcs , m reducing that 10 pcs to 5 pcs.
    5.now that particular is closed .
    6. when i add remaining 5 pcs below that row and update.it is throwing me an error "Documents rows cannot be closed concurrently with the other document modifications you have made"
    PLEASE HELP EXPERTS
    Regards
    A S VAMSI KRISHNA

    Dear krishnavamsi,
    I would like to ask you to read these notes and check if they are relevant to your issue:
    1036601
    1131943
    1298236
    Also, I would like to know how did the customer add the document in the previous version, manually by application or by DI API, ADD ON or any customization?
    Regards,
    Marcella Rivi
    SAP Business One Forums Team

  • GPIB-ENET/100 Issues with Red Hat Enterprise Linix 3.0

    Does anyone know of issues with Red Hat Enterprise Linux 3.0?
    Using Red Hat Linux 8.0, I am able to run EthernetConfig and identify all the GPIB-ENET/100 devices on my Ethernet.
    Running EthernetConfig under Enterprise Linux does not work properly. No devices are detected.
    Everything else appears to be working.
    I can ping the device.
    I can also detect the device using my Windows based program NI-488.2M for Windows NT/GPIB-ENET100 Utilities/Device Configuration.

    I do not know of any issues with RHEL 3.0 and the Beta 488.2 driver. I believe that you have started a support request via e-mail so I will deal with your issue there.
    Thanks,
    Scott B.
    Applications Engineer
    National Instruments

  • After Effects CC Render Errors with RED footage and ProRes 4444 proxies

    Working on an 8 Core, 2008 Mac Pro with 16GB of RAM running Mountain Lion.
    I just upgraded to After Effects CC and I'm having a whole bunch of errors ...
    -- the 'MooV' file is damaged or unsupported
    -- error getting package info for file "..." ( 3 :: 164 )
    -- Error (4) reading frame from file "..." ( 86 :: 2 )
    I'm trying to make ProRes 4444 proxies from RED files (sometimes as big as 4K), which will eventually end up in a 1920x1080 project. I'll make a 4444 proxy, work on it all day with no problems, then when I try to render (or save a RAM preview) any one of the previous errors will show up.
    My projects seemed to work just fine fine in AE CS6, and I've worked with RED footage in AE before with little issue. I've completly restarted my system, re-installed everything, worked off an external drive, worked on my internal (software) RAID, rendered to local and external hard drives, adjusted my multiprocesser render settings (on and off), cleared the cache ... nothing is fixing it.
    Does anybody else have any ideas? Or insight. Or anything?!
    Thanks for your time,
    Eliot

    I'm working on a MacbookPro, Early 2013, OS X 10.8.4, and I'm having the same exact error:
    However instead of using RED footage, I'm using a 3rd party plugin called Element 3D and Optical Flares from VideoCopilet.net.
    I'm not sure if the bug is related, I'm just wondering if anyone else has any idea on how to fix this problem. I have a fresh install of CC so I can't downgrade to CS6.
    Another error popped up during multiple trys in export:
    In case the old file was actually corrupted, I checked all my backups that worked perfectly fine with CS6 in the past, and I get the same error when I copy them over to my hard drive on my mac.
    My current setup is:
    Processor: 2.8 GHz Intel Core i7
    Memory: 16GB
    Graphics: NVIDIA GeForce GT 650M 1024 MB
    I really don't want to recreate this entire file from scratch. That would be a lot of hours wasted... any suggestions would be greatly appreciated.

  • The default priority setting in Mail is set to "normal"  and is causing emails I send to be sent with red priority flag. How can I set default priority to low = no flag?

    The default priority setting in Mail is set to "normal"  and is causing emails I send to be sent with red priority flag.
    I have found the flags to reduce the priorty level manually to "low Priorty", but how can I set default priority to low = no flag?
    Thank you for advising,

    Try deleting the .plist.
    Quit the application.
    In Finder hold down the option/alt key while selecting the Go menu item. Select Library. Then go to Preferences/com.apple.mail.plist. Move the .plist to your desktop.
    Open the application and test. If it works okay, delete the plist from the desktop. 
    If the application is the same, return the .plist to where you got it from, overwriting the newer ones.
    If you want to make your user library permanently visible, run the below command in Applications/Terminal.
    chflags nohidden ~/Library/
    You will need to do that after any updates.

  • Closing application

    i see that if i want to closing application i must do that
    To close an app completely : from the home screen (i.e. not with the app  that you want to close 'open' on-screen) double-click the home button  to bring up the taskbar, then press and hold any of the apps on the  taskbar for a couple of seconds or so until they start shaking, then  press the '-' in the top left of the app to close it, and touch any part  of the screen above the taskbar so as to stop the shaking and close the  taskbar.
    my question is there an easy way instead of that method to closing application i think that my cause soon the home key crash cause of many press on it when closing every application hope you give me a solution

    You really do not need to close previously used apps completely. When you leave an app and go to the Home screen or another app, the previous app quits running.
    There are a few exceptions to this like in Mail where the app will finish a task like sending or receiving email.
    But most apps just stop working and have there state saved. Then when you go to that app again you go back to where it was and it starts running again.
    The only time I close or quit an app by double clicking the Home button is when an app freezes or misbehaves.

  • When I start recording with Captivate 4 it restarts

    It is so strange, since it was working fine, I believe it should be because an update, when I start recording with Captivate 4 it restarts showing for less than a second a blue screen.
    What can I do?

    Hi,
    Try after deleting the preferences folder.
    you can find the preferences folder [Adobe Captivate] in the following location:-
    - on Xp C:\Documents and Settings\<USER NAME>\Application Data\Adobe
    - on Vista/Win7 C:\Users\<USER NAME>\AppData\Roaming\Adobe
    Regards,
    Vikranth.

  • How do I remove an "orphaned" window from a closed application?

    Hi,
    Every now and then, I end up with an "orphaned" window on my desktop, left over from a closed application. Currently, I have a login window from the Screen Sharing application that's been spinning the spoked progress wheel next to "Connecting..." for an hour or so. I've already closed the Screen Sharing app, so it's not a straightforward thing to go into Activity Monitor and kill the process. I know that I can reboot the machine to fix this, but I'm wondering if someone might know how to fix this sort of thing without a reboot. Is there some app that I can use that can tell me what process is the "owner" of this window? Since the progress wheel is spinning and I can drag the window around, it would seem that some process has control of it, but I just don't know which one.
    Thanks,
    Ken

    Hi Carolyn,
    Thanks for the information, but maybe I didn't clearly explain what happened. I had the Screen Sharing app open, and then I properly closed it down by quitting the application. But one of its windows remained on the desktop. I went into Activity monitor, and the Screen Sharing app wasn't listed in the process list at all. So I'm guessing that this window isn't owned by the Screen Sharing app itself, but from some other process that was spawned by the Screen Sharing app that didn't close when I shut down the Screen Sharing app. Granted, this situation doesn't come up very often, but I've also seen it happen with Norton Antivirus, if I dismount a volume while there's a popup window doing a "scan on mount", with the result that the "scan on mount" window doesn't go away. So given that the process with the "friendly" app name no longer appears in Activity monitor, can you suggest any way to determine which of the running processes "owns" the still-present window?
    Thanks,
    Ken

Maybe you are looking for

  • Unable to Install Framemaker 10 on Windows 7

    I am trying to install Framemaker 10 (x64) on a Windows 7 computer. I have already uninstalled my previous Framemaker 7 version. Even after that i could notice the following error messages in the log file. Collected advanced path check information fo

  • Edit in ... disabled?

    I have tried today to edit an image but Photoshop, as well as other editor and all other choices, are greyed out in the Develop module under Photo. I've certainly often used this and don't know why it's not working today. I'm using 2.3 under Win XP P

  • Canvas gone, functionality gone?

    Canvas used to have CanvasDropEvent, now Canvas is gone and the functionality doesn't seem to be supported elsewhere. I want to incorporate the ability for the user to drag a url into the applet and capture it. Does JavaFX 1.0 have a way to accomplis

  • Comms 6 upgrade help

    Greetings all, I'm needing some advice on how I should proceed with an Upgrade of Comm's. We currently have a small setup with a backend cluster and a couple front ends running the multiplexor. Everything Comms 5 Sun Java(tm) System Messaging Server

  • Will Labview 5.0 work on Windows XP

    I am currently upgrading systems to Windows XP and need to know if my old Labview 5.o version is compatible with Windows XP. Does anyone know? The application I created on Windows 98 is currently operating on Windows XP with out any concerns. Future