PyQt5 Windows closes with notification close about windows-10-toast-notifications HOT 6 OPEN

Hi @studiozeroseven thank you for raising the issue.

I will look look into this and revert back.

from windows-10-toast-notifications.

@studiozeroseven Apologies for the delay I was caught up in work.

Please confirm if you still facing the issue and need help.

I'm not able to recreate this in my Python 3.5 environment. If you need help, could you please provide the PyQt version you are using and also the imports.

from windows-10-toast-notifications.

Hi, I'm getting the same thing. PyQt5 is latest version from pip, on python3.
Imports look as follows:

from PyQt5 import QtGui, QtCore, QtWidgets
import sys, os, shelve, time, threading, random, operator, copy, datetime, os, collections
from operator import attrgetter, itemgetter
from random import randint
from win10toast import ToastNotifier
from playsound import playsound

from windows-10-toast-notifications.

Hi guys,
I've sourced the issue in line 136 init.py in the library. Disabling PostQuitMessage(0) seems to fix the issue. I'm not sure of how this will affect the usage. If you have any experience in this please give your suggestion. I'll be investigating this further before pushing a change.

from windows-10-toast-notifications.

Heyo. Commenting out that line seemed to fix the crashing. The sleep(duration) a few lines before that hangs the program for a few seconds so I commented that out also.

from windows-10-toast-notifications.

Just want to add my 2 cents. I'm using PySide2 (which is basically PyQt5, so what I say should apply to PyQt5), and I was getting this problem as well with it crashing the app. Using multithreaded option works perfectly.

Please verify this. The issue should be fixed already.

Use threaded = True to fix the issue

--
Probably the issue here is that this module doesn't interface with the Qt event loop. @author, you might be able to fix this blocking issue by periodically taking breaks in a loop (that ultimately waits the entire 5 seconds, or however long) to call QApplication.processEvents().

--
But there's no need to try to make it Qt compatible. The correct way this should be done is by using another thread, and this is already the case. So this issue is now solved

from windows-10-toast-notifications.