-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: 'NoneType' object is not callable #11
Comments
I just rewinded to a former commit and discovered that this issue seems to have the same source as the issue#9, which I had closed, hoping that a one-time-reset of my docking station would prevent further problems. But this "new" state of my docking station seems to be a possible "normal", as all other operating system features concerning the monitor control seems to work properly. Just When I have time, I would try to track down the effect and look for alternative ways to handle the effect. Hoping that this would be a workaround. |
@nnako Aah, sorry, I added a method named Line 41 in f5d457e
You may update your theme configuration by adding the same function or make it optional |
Hi @klesh , thaks for your reply. I added respective parameters The other thing is that now, the old error from issue#9 has returned: Traceback (most recent call last):
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\wm\manager.py", line 142, in _consume_sync_queue
self._sync(init, restrict)
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\wm\manager.py", line 183, in _sync
monitor_state = virtdesk_state.get_monitor(monitor)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\wm\state.py", line 206, in get_monitor
theme = sorted(self.themes, key=lambda x: x.affinity_index(monitor.get_screen_info()), reverse=True)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\wm\state.py", line 206, in <lambda>
theme = sorted(self.themes, key=lambda x: x.affinity_index(monitor.get_screen_info()), reverse=True)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\w32\monitor.py", line 175, in get_screen_info
if monitor.name == self.name:
^^^^^^^^^
File "C:\Program Files\Python311\Lib\functools.py", line 1001, in __get__
val = self.func(instance)
^^^^^^^^^^^^^^^^^^^
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\w32\monitor.py", line 140, in name
return self.get_info().szDevice.decode("utf-8")
^^^^^^^^^^^^^^^
File "C:\Users\USER\_NEXTCLOUD\_TOOLS\_Python\APP__JigsawWM\src\jigsawwm\w32\monitor.py", line 159, in get_info
raise WinError(get_last_error())
OSError: [WinError 1461] Ungültiges Handle für den Monitor. I'd appreciate any help on these two effects. Thanks. |
The and return an For example, I have no idea what might cause #9 at this point.. |
here come some news about the strange issue described above and issue #9 .
I don't have a clue why it is the fact that Microsoft alters a lot of other system parts just through installing ordinary compiler tools. This is one reason, I don't like working (developing) on Windows. So much unnecessary complexity. Trying to figure out how to find and install a minimal set of compiler tools for a functional application of |
Hi again,
I just updated to the latest commit on
main
branch in order to prepare a small PR, but sadly,jigsawwm
throws an error. Now, the error occurs before the windows have been arranged on my big monitor (which is different than the now closed issue#9, where the error occured after it). In order to at least be able to letjigsawwm
arrange my windows, I will have to go back in commit history...Here are the details: After walking into the project and virtual environment (where I already updated the last new modules using
pip
) I start the tool. After startingjigsawwm
with the configurationnnako.pyw
from the examples folder (as I generally do), without any change on the window locations, I get the following error message in the calling terminal window:The execution stops within the function get_monitor() at this location (line 206):
After pressing
<CTRL> + <C>
within the terminal window, I see the application completely stops:I've tried to set a breakpoint to line 204, but it oddly seems to be ignored when executing. Maybe, the code is already running at some other thread / place and would thus rather be inaccessible for the debugger?
Any hints? Can I check something?
The text was updated successfully, but these errors were encountered: