Monitor isn't switching off with V4 beta caching version

[seelenfrieden]

No description provided.

[pritpalspall]

+1

[seelenfrieden]

@cDima can you help on this issue?

[cDima]

What a strange issue. 👍

[seelenfrieden]

i downloaded the latest release and it is working now :)

[seelenfrieden]

it still does not turn off the monitor. If the screensaver control panel is open the monitor is turning off, after the assigend time. If the control panel is closed (what should be the usual state) the monitor is not turning off. Any idea how to fix it?
@cDima where can i download the last version without caching? I remember that the problem does not appear with this version.

[alistairmcmillan]

All releases are available here.

https://github.com/cDima/Aerial/releases

[scuba-fan]

Same reported issue as seelenfrieden. sorry for the dup. latest release installed, monitors won't turn off.

[jimmyfortune]

It just sucks, doesn't work and there's no support

[alistairmcmillan]

@jimmyfortune You posted a new issue about an hour ago. One. Hour. Ago. Pretty hasty to start complaining there is no support.

[jimmyfortune]

It was the simple conclusion after seeing how many people are experiencing issues and how many issues have been unresolved or unanswered.

[cDima]

You can send payments through PayPal to sadakov@gmail.com since this is a free personal project instead of complaining like a child.

On May 19, 2016, at 6:02 AM, jimmyfortune notifications@github.com wrote:

It just sucks, doesn't work and there's no support

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[jimmyfortune]

You are a true real life example of how customer service should work.
Kudos to you!

You can send payments through PayPal to sadakov@gmail.com since this is a
free personal project instead of complaining like a child.

On May 19, 2016, at 6:02 AM, jimmyfortune notifications@github.com
wrote:

It just sucks, doesn't work and there's no support

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

---

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#54 (comment)

[alistairmcmillan]

@jimmyfortune This is not customer service. You are not a customer. The definition of customer is "A person who buys goods or services from a shop or business."

And it is worth noting that you mentioned two problems in #67. I gave you a solution to one and in response you've just demanded the solution to the other. You couldn't even be bothered to say thanks for that first assistance. Why do you think anyone else should give up more of their own time to assist you with the way you are choosing to talk to us?

[jimmyfortune]

Alright, we can go on about this, but you are right, I shouldn't have let my frustrations take over and comment in the way I did. I apologize for that. I was really enthousiastic after seeing it on a Mac and then it just crashed time in time again and I read the issues and saw that they were not solved.

Just tried it on two different machines and it made everything crash on both. I guess the machine is just not strong enough to get it running, which is a bit silly for a screensaver. I guess this won't be for me then.

[cDima]

@alistairmcmillan I think the description for the error is best described by Louis CK 😜

[jimmyfortune]

Thanks for your resolution to the second issue.

[alistairmcmillan]

@jimmyfortune I don't think it's anything to do with the strength of your machine. I think it's a network problem. Perhaps you are behind a corporate network or a proxy of some sort? If one of your machines is a laptop I'd try connecting it to another network and trying there to see if it behaves any differently.

[alistairmcmillan]

I've tried to replicate this bug. But it's a bit hit or miss for me. Sometimes the screen stays on past the cut off time as people are saying here, some times it works as it's supposed to. Frustrating.

[scuba-fan]

Can I help? It never turns off for me. Ever. Doesn't matter what timeout setting.

Cheers,

Doug

On Jun 5, 2016, at 10:59 AM, Alistair McMillan notifications@github.com wrote:

I've tried to replicate this bug. But it's a bit hit or miss for me. Sometimes the screen stays on past the cut off time as people are saying here, some times it works as it's supposed to. Frustrating.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[alistairmcmillan]

@scube-fan Thanks. The code in the caching version isn't that different. Could you try turning the caching option off, leaving the screensaver running and let me know if the screen turns off?

[alistairmcmillan]

No reply for months, closing issue.