I don't have a problem with it, I was just curious, that's all.Robin wrote:FTFY.Nixola wrote:Closing the console kills LÖVE whatever programs are associated with that console instantly on every OS.
If you don't like what it does, take it up with Microsoft.
love.conf not using love.quit when closed
Re: love.conf not using love.quit when closed
GitHub | MLib - Math and shape intersections library | Walt - Animation library | Brady - Camera library with parallax scrolling | Vim-love-docs - Help files and syntax coloring for Vim
- Jasoco
- Inner party member
- Posts: 3727
- Joined: Mon Jun 22, 2009 9:35 am
- Location: Pennsylvania, USA
- Contact:
Re: love.conf not using love.quit when closed
Or Apple, or.. uh.. whoever is in charge of Linux, or rather Unix in general. lolRobin wrote:FTFY.Nixola wrote:Closing the console killsLÖVEwhatever programs are associated with that console instantly on every OS.
If you don't like what it does, take it up with Microsoft.
I didn't know closing the console on Windows closed the Löve app too. I thought the console was something Löve opened for Windows to print to since it didn't work like Unix does and needed to have something for printing to. Interesting to know.
But keep in mind that the console is for debugging anyway and a finished product won't need nor want the console to open. Think of having the console closable as a way of killing the Löve app in an emergency. (Like in my case on OS X if I end up in an infinite or very long loop. Closing the Terminal window will kill the love process immediately so I don't have to force quit it. Very convenient. I just tried it out myself on Windows. Yep. Works. Does the Console run as a separate process on Windows though like Terminal does on Unix?)
Re: love.conf not using love.quit when closed
Yes and no. The consoles are handled by a Windows service and the processes just request their allocation or attachment. The console window itself is associated with the process that allocated it (Not that this reflects ownership or something). When the console gets closed, Windows terminates the processes that are attached rather abruptly.Jasoco wrote:Does the Console run as a separate process on Windows though like Terminal does on Unix?
Applications can also target the console subsystem in which case they automatically inherit the console of the parent process or allocate their own if the parent doesn't have one. When such an application is started from cmd.exe it works similar to what you know from the other platforms.
Shallow indentations.
Who is online
Users browsing this forum: Bing [Bot] and 3 guests