seeseemelk/cool-retro-term
1
0
Fork 0
Code Issues 449 Pull Requests 12 Actions Packages Projects Releases 8 Wiki Activity

Phosphor burn-in #98

New Issue
Open
opened 2014-08-25 12:28:17 +02:00 by proedie · 2 comments
proedie commented 2014-08-25 12:28:17 +02:00 (Migrated from github.com)
Copy Link

Okay, I have a great idea for a new feature. (At least I think so.) Phosphor burn-in!

Of course, it probably would be too complicated to actually capture the screen and wait until a burn-in would have occured, but users could still choose something to be burned-in.

Default could be user@host:~$ in the first line, for example. Also, users could click on a 'Burn-in now!' button to burn-in whatever is on the screen in that moment.

Cheers!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Okay, I have a _great_ idea for a new feature. (At least I think so.) [Phosphor burn-in!](https://en.wikipedia.org/wiki/Screen_burn-in#CRT) Of course, it probably would be too complicated to actually capture the screen and wait until a burn-in would have occured, but users could still choose something to be burned-in. Default could be `user@host:~$` in the first line, for example. Also, users could click on a 'Burn-in now!' button to burn-in whatever is on the screen in that moment. Cheers! ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4024915-phosphor-burn-in?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>
Swordfish90 commented 2014-08-26 16:01:31 +02:00 (Migrated from github.com)
Copy Link

Hi, this is something very very neat that I will consider adding in the future. It was something already mentioned in the past but I really like the Burn-in now feature, I think this is simple and effective.

Hi, this is something very very neat that I will consider adding in the future. It was something already mentioned in the past but I really like the Burn-in now feature, I think this is simple and effective.
chungy commented 2014-09-11 14:30:57 +02:00 (Migrated from github.com)
Copy Link

A dynamic type of burn-in would be cool, not necessarily simulating something permanent, but if you can determine which pixels are stuck on for extended lengths of time, they could fade out much slower than other parts of the screen. Imagine exiting a screen or tmux session and their persistent status bars take a while to go away :P

A dynamic type of burn-in would be cool, not necessarily simulating something permanent, but if you can determine which pixels are stuck on for extended lengths of time, they could fade out much slower than other parts of the screen. Imagine exiting a screen or tmux session and their persistent status bars take a while to go away :P
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bounty
bug
duplicate
enhancement
help wanted
invalid
priority
high
priority
low
question
wontfix
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
seeseemelk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#98
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?