Skip to content
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

Folder icon with telegram client #6998

Closed
belnet opened this issue Jan 14, 2020 · 7 comments
Closed

Folder icon with telegram client #6998

belnet opened this issue Jan 14, 2020 · 7 comments

Comments

@belnet
Copy link

belnet commented Jan 14, 2020

Steps to reproduce

  1. install a custom icon on the client folder
  2. run telegram client
  3. the read-only attribute is erased by the folder and the icon ceases to be displayed

problem play video: https://klikr.org/33843cc95c8acf3f4f5d137d1d43.gif

Expected behaviour

Tell us what should happen

Actual behaviour

the client erases the read-only attribute from the directory where telegram.exe is located
this should not happen.
even if recording is allowed in subfolders and files (which is logical), the attribute of the EXTERNAL directory should remain unchanged.
I suggest tracking this by the presence of the desktop.ini file in the directory.
if this file is present, then the client should check the attribute of the directory in which it is located, and not mindlessly erase it.
Windows OS processes desktop.ini which is responsible for displaying the icon on the folder ONLY if the read-only attribute is set on this folder

for example, I can set this attribute from the console:
https://klikr.org/7c7f0dc9e628adbb4e3c815be429.png
an icon on the folder will appear, BUT only until the first launch of telegram.

Configuration

Operating system:
Win 10 LTSB (1604) x64.
Version of Telegram Desktop:
1,0 + 1.9.3
Used theme:
any

@Aokromes
Copy link
Collaborator

1.0.3? update the current telegram client version is 1.9.3

@belnet
Copy link
Author

belnet commented Jan 14, 2020

https://klikr.org/c39828479815b5c19b02c9cb4675.png
it was a typo.
current client 1.9.3
but this problem has been going on since the first version.

@belnet
Copy link
Author

belnet commented Jan 14, 2020

You copy a desktop.ini file into a folder to customize and maybe localize it. You have correctly set the file’s attributes to Hidden, System and Read-Only, but still your customizations do not work. To make it work you need to set the Read-Only or System flags on the folder where the desktop.ini file resides. As I am sure you know, folders cannot be read-only, neither can they “remember” your settings so that all new files placed in the folder become read-only as well. So this flag is purely to tell Windows that this is a special folder and that it should look for a desktop.ini file inside it.

TNX to Asura for this.
thus Read-Only or System
I set one of the attributes, as the specification requires, it works for the folder, but it’s worth starting the telegram as the attribute is overwritten (

@Aokromes
Copy link
Collaborator

i wonder if you can use this way on windows #1908 (comment)

@belnet
Copy link
Author

belnet commented Jan 26, 2020

Unfortunately, the topics have nothing to do with my problem and it is character only for windows.
the telegram client should be able to correctly read and process the attributes of folders, and not stupidly overwrite them at its start, this is the bug.

it is a pity that the developers do not look into this thread.
Anyway, thank you for trying to help with my problem!

@stale
Copy link

stale bot commented Oct 23, 2020

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 stale bot added the stale label Oct 23, 2020
@stale stale bot closed this as completed Nov 22, 2020
@github-actions
Copy link

github-actions bot commented Mar 4, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants