tdesktop
tdesktop copied to clipboard
telegramdesktop
Allow users to change which Monitor to show Notifications on
Steps to reproduce
- Open Settings.
- Open Notifications Position and Count.
Expected behaviour
User should be able to select which monitor the notifications appear on.
Actual behaviour
There is no option for this yet. Telegram Desktop will always show alerts on the same monitor as the application itself.
Configuration
Operating system: Windows 7
Version of Telegram Desktop: 1.1.10
Used theme: N/A
Hey there!
We're automatically closing this issue since there was no activity in this issue since 445 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.
Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
(Please note that this is an automated comment.)
Please reopen. If we're using a bot to auto-close tickets then it should be issuing a warning before doing so, giving users a chance to keep it alive.
Giving this another bump (sorry) to say that I'd really like to see this as well. Often, notifications for other chats will pop up in front of a text box that I'm typing in for a different chat, which is extremely annoying. Being able to set them to always show on my other monitor would be a lot nicer. I'll add that I'm using the Telegram client for Linux.
@psjf If notifications pop-up in front of a text box, why not just move them to a different corner?
@23rd They'd still be on the same monitor, which means they'd likely be blocking something else (I've experimented with that before). Being able to shove them over to the monitor I use less often would make them a lot less intrusive.
The workaround I've settled on is enabling "Use native notifications." Content-wise, they're slightly less versatile than Telegram's built-in notifications, but on my KDE desktop, they pop up next to the task tray on the other monitor by default.
Hey there!
This issue will be automatically closed in 7 days if there would be no activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Yes we still want this feature.
I'd much rather be using Telegram's notification system than the Windows 10 default, but because I have multiple screens I have no other choice.
I've seen the github-actions bot has been aggressively locking issues recently, so I'm just bumping this to make sure it stays open. I sympathize with the team if they're having trouble reading through all the incoming tickets and I hope they get more contributors to help out, but continued use of Ghost bot, Stale bot etc. is just going to annoy users.
Ima perform a sin and bump this ticket because I really want this to be a feature
bumping up... we stream what we do on YouTube LIVE (https://gridnet.org).. the lack of it gets in a way
OK. Real talk for a second...
Someone at Telegram HQ is paying for the developers to add stuff like this to TDesktop. So, how do we, the users, request and pay for features/fixes that we need? Because it seems like these things aren't being prioritized based on ticket age or the number of people who actually want them.
I'm also going to casually point to issue #151 - the three-digit issue ID should give a hint at how long we've been politely requesting a basic volume control for notification sounds.
If anyone wants to see a test build with this feature, you can download it from here for Windows.
https://github.com/telegramdesktop/tdesktop/actions/runs/18122313173
So, how do we, the users, request and pay for features/fixes that we need?
This bug tracker is powered by community and no one deciding priority for tasks to the paid developer (preston) is reading this. I'm not sure there's a way you can supply your request for those people. The closest way would be the in-app support. But then this support consists of volunteers and you may never get an answer. The next thing would be the official bug platform but it looks like there's not enough moderators to read each issue, rather the other way around - it looks like a few issues in the constant flow get noticed.
Personally I guess even if a request gets to the right person, they likely decide based on internal business metrics rather than user requests.
If anyone wants to see a test build with this feature, you can download it from here for Windows.
i was told that notifications on monitor 1 goes to monitor 2.
i was told that notifications on monitor 1 goes to monitor 2.
Do you mean it always displays on monitor 2 or monitor 2 is monitor 1 while monitor 1 is monitor 2? If the second, that might be just that Windows internal enumeration (that's what those DISPLAY1, DISPLAY2 and etc) is different from what it presents via settings or the user thinks.
Do you mean it always displays on monitor 2 or monitor 2 is monitor 1 while monitor 1 is monitor 2? If the second, that might be just that Windows internal enumeration (that's what those DISPLAY1, DISPLAY2 and etc) is different from what it presents via settings or the user thinks.
I configured the notification to DISPLAY 1 and it shows on DISPLAY 2. Configuring them to display 2, 3 or 4 works as expected, it shows on the monitor enumrated as per windows settings:
Do you mean only display 1 doesn't work while everything else works? Which scaling do you have on the displays?
I've 100% scaling on the 4 displays.
When it's configured as this:
It behaves like:
The notification shows on the display 2 when it should be on display 1. The rest of the options (2, 3, 4) work as expected.
n = 1, someone else could try to reproduce this.
edit. Wrong screenshot, replaced the third image.
From reading the code, it looks like when you set the primary screen, it will prefer the screen the main window is on instead. So if display 1 is your primary screen, it works as expected it seems.
I find the UI confusing then, but I've no suggestions on how to re-word the primary screen option to "monitor where the app is on". Thank you for adding this, with 3~4 monitors I appreciate being able to look always at the same corner of the same monitor.
A new build is here. https://github.com/telegramdesktop/tdesktop/actions/runs/18162243322
It works as expected. Default = Primary, I tested it by changing the primary monitor without restarting telegram and that works too.
Though naming when genericName is used is a bit confusing. I think that that array is zero-indexed and it may need a +1 to be equal to windows enumeration. https://github.com/telegramdesktop/tdesktop/commit/7c43f5f55b9753484678075157581f37b2109c00#diff-6bfee15b48cdaeed617b7fb459260679c352d6efdf3c99158d77a34cf47f3156R842
@Astu04 it looks like the enumeration starts from 1, just the order is different, H257HU is 4th in the list. That's likely unfixable though as that's the order as provided by the underlying framework (Qt).