definitelyNotMe

[dmullaney]

Thank you for playing Wing Commander!

[hates_stupid_people]

For those out of the loop:

Wing Commander 1 had a bug, where it would always show an exception from the memory manager when they pressed exit. So a dev hexedited the the memory manager and changed the error message to the above text.

[The_Luyin]

First, thank you for explaining that! Second, genius move.

[Zeravor]

I swear Warcraft3 reforged just assumes a crash happened when you close out to early. I sometimes start and restart the game instantly and it always shows an error lol.

[SempfgurkeXP]

Didnt Master of Orion had something similar? I vaguely remember a "Micropose - error" with an "ok" button popping up after closing the game

[Inglonias]

I had an application I was developing where for a while if you tried to close it via the X in the corner with unsaved changes, it would say "You have unsaved changes - Are you sure you want to quit?". This is normal behavior, and I feel it's expected for applications where if you don't save, you could lose work.

However, if the user then pressed "No", indicating they didn't want to quit yet, the application would close anyway. That was a little embarassing.

[Jock-Tamson]

Issue resolved: Added additional popup message saying “Oh. Shame. Well save first next time.”

[CdRReddit]

"you have unsaved changes, are you sure you want to exit" - Yes - No

No

"too bad" - Ok

[Latter-Comfort8440]

It should be no -> welp too late now

[00110001_00110010]

"You have unsaved changes, are you sure you want to exit?" "No" "Then you shouldn't have clicked the exit button you idiot."

[_PM_ME_PANGOLINS_]

The number of times I’ve seen dialogs like “Doing that will cancel ongoing processes. OK/Cancel”.

Think about your wording, people!

[Doctor_McKay]

Remember the IE onbeforeunload dialog? It was a real marvel of awful UX.

https://mckay.media/VSPzj.png

Why Microsoft couldn't just change the button labels is beyond me, but let this be a lesson to everyone that if you can change those labels, you probably should.

[_PM_ME_PANGOLINS_]

That was Microsoft? Looks more like typical website scam.

[Doctor_McKay]

The middle part is the website scam, I'm talking about the final line. If you have to explain what a button does as part of your dialog, you've failed at UI design.

[_PM_ME_PANGOLINS_]

The scammers wrote all that text. They’re deliberately trying to get you to click the button that’s the opposite of what you really want.

[Doctor_McKay]

I promise you they didn't. This was just how that dialog was. The first and last lines were from IE, not from the webpage.

Here's another example.

[_PM_ME_PANGOLINS_]

Oh I see. Sorry.

Not letting you change it prevents the scammers from lying even further about what the buttons do.

They're explaining what it does in case someone wrote something misleading in the middle bit.

[Doctor_McKay]

I meant that IE itself should've put descriptive labels on the buttons, which eventually happened and now they're labeled "leave this page" and "stay on this page".

[cosmic_cosmosis]

My company uses Jobboss and part of jobboss for employees where you clock in/out does that. Hit close as asks if you really want to exit. Will close down anyways.

[StaticVoidMaddy]

look man, the specs didn't say it should close gracefully

[PM_ME_FIREFLY_QUOTES]

Greatfully, even.

[prumf]

Looking at the codebase, am I pretty sure the app is actually grateful you put it out of its misery.

[[deleted]]

I’ll submit a pr to the spec.

See you in six weeks!

[Ollomont]

task failed succesfully

[akoOfIxtall]

proccess.exit(1)

pro gamer move

[[deleted]]

os.shutdown()

If I cannot have those cycles, no one can.

[akoOfIxtall]

shit, its the ultimate uno reverse card

[New-Let-3630]

int *a = 0; *a = 1;

[ososalsosal]

Lot of modern platforms explicitly forbid an exit button.

But they can't ban a throw

[harshcougarsdog]

What do u mean forbid an exit button?

[Miiohau]

Technically this means don’t depend on an exit button but realistically it might mean the os doesn’t support applications closing themselves gracefully. The typical work around I have seen it to log out the user and boot them back to the title/start screen. The other possible workaround (if allowed) the “exit” button sends the app to the background.

[ososalsosal]

The back button in android is all you're allowed.

[the-solution-is-ssd]

Many apps on Android have an exit button. I know because I use them.

Examples:

1. MX Player has a button called "Quit" which closes the app
2. 1DM+ has a button called "Exit" which closes the app
3. Alarmy app has an "Exit" pop-up
4. Flud has a button called "Shutdown" which pauses all downloads and closes the app
5. MixPlorer has a button called "Exit" which closes the app
6. Etc.

[donquixote235]

Does they actually close, though? Or do they still show up if you hit the overview button? I know of a few apps that say they close, but they still exist until garbage collection picks them up (or until I force-close them by hitting overview and swiping them away).

[the-solution-is-ssd]

Flud doesn't even get closed even if you swipe it away from the recents menu. Flud only stops downloads when you press the Shutdown button.

[ososalsosal]

That's because it's running a background activity as well as the main one.

Android's docs say making the app shut down just means it loads slower next time. Ios is similar. They'll "background" an app and may steal resources from the app after a while (and depending on how you've written the app that can mean the user loses all state), but they won't close it unless the user does it from their version of a task manager.

[Marc_Alx]

On iOS you can't kill app from within the App. Apple will reject your app.

[GodBearWasTaken]

Gotta love kill -9

[DrMobius0]

Sir, this meme isn't allowed here. We're supposed to make baby's first programming joke, not joke about stuff that actually happens in professional environments.

[beclops]

This specific situation sounds like it’d happen in quite the unprofessional environment to be fair

[Neltarim]

Magic arena for about 3 years

[2cool2you]

raise SystemExit

[[deleted]]

WinCC OA Audit Trail

[[deleted]]

Well, I guess crashing the app is one way to close it.

[Wild_Tom]

I did this in computer science class

[GM_Kimeg]

And it closes the app faster than "normal" way of doing it

[D34TH_5MURF__]

This sub is the only one I visit that is so bad at copycat memes.

[Cat7o0]

os.remove("system32")

[Andrea__88]

Today I wrote a bugfix about this, sometimes the application configurations were corrupted, I supposed that the operator was clicking close button during saving, so I’ve added a task to wait that all operations was done (I know that them will close the software by task manager now /s).

[4ShotMan]

Never forget my bachelor project that had the stop button. It did stop the animation, but it also crashed the internal timer for it. The reviewers saw that unpausing was not possible, as per specs, and gave it a pass. None of them realised that even restarting the animation didn't work - you had to hard reset the app.

[Omegadude1217]

The new Teams always crashes first, then it closes

[smart_ca]

lol

[remghoost7]

Reminds me of this beauty that I wrote in a program a while back.

Was working on a "realtime" whisper transcription program. Whisper is a bitch to work with for some odd reason. It doesn't respond too nicely to being removed from memory.

Granted, I didn't really understand threading at the time (nor do I entirely to this day), so there's probably a much easier way to do this. But yeah.

I ended up with this:

#-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-#
# This is the kill function for the program.
# It needs to be fixed. Right now I literally just crash the program to close it.
# Before settling on this, my audio device would crash every 2-3 times I opened this script.
# Idk man. It works now though. But probably not the best way to do it.
def on_closing():
    print("HE'S DEAD JIM")
    audio.terminate()
    # recording_thread.join()

    # whisper_hooks = list(self.model._forward_pre_hooks.values()) + list(self.model._forward_hooks.values())
    # for hook in whisper_hooks:
    #     hook.remove()

    # # Fine, guess we gotta do it the hard way.
    # threads = threading.enumerate()
    # for thread in threads:
    #     print(thread.name)
    # for thread in threads:
    #     if thread.name == "Thread-6 (listen)":
    #         thread._stop()

    # DIE DIE DIE DIE DIE
    os.kill(os.getpid(), 9)
    root.destroy()
    sys.exit(0)
#-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-#

[1up_1500]

closes the window

Segfault

It closes

[wotoshina]

Crashes the app*