|
The same problem has been reported frequently over a long period of time. It would have taken virtually no effort for the people doing this software to put a simple notice advising downloaders about this, and saving the waste of time on the part of first-time users, not to mention the waste of their time.
Did you not understand this is open-source software, and the folks doing it are volunteers ?
Like I said, this experience is really unique in my long and happy use (and occasional contribution to) open-source software.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Please don't take offence as I certainly didn't intend any.
Your initial post said Quote: I noticed other similar issues reported there.
which is different to Quote: The same problem has been reported frequently over a long period of time
Warnings would be useful but as the dev said there may well so many that it might be difficult to see the specific one that would affect you and you may well have still gone ahead anyway
I do understand your frustration at the time you have wasted trying this software but there is always the possibility that it might have been so good that it might have been worth replacing your monitor with something that could work with it
|
|
|
|
|
Since it's "open source", why don't YOU volunteer to fix it ....
|
|
|
|
|
Bill,
I get that you have some vision issues that require a specific environment.
I have watched my co-workers ruin their vision with ultra high res screens, that they squinted at.
I avoid that. If I can't read the screen without ANY stress/tension in my eyes I use larger screens,
or bigger pixels.
The challenge we face today is the digital screen. In the analog days, they scaled better between resolutions without the pixelation.
But as a developer, I have long fought layout issues in my applications for various users who want to use large fonts. Oh, large fonts killed us. We literally had to spend a month going through hundreds of screens to make sure they sized properly because of large font settings. We had to RAISE OUR minimum requirements of the monitor size along the way.
==
I am curious. Is there any solution you can apply to your end that would allow you to work around the problem? (Having purchased well over 12 monitors for myself over the years to find the right ones for me, I understand that it takes work on my side as well)...
Do you run dual monitors already?
For example, I have a small 1024x768 monitor as my third monitor, above my other two. I have to use this because some clients have these old small screens, and when I try to do screen sharing, it sucks for them.
Do I use it every day? Nope. Does it get around the problem? Yep.
Sometimes it is better to solve the problem in a different way.
HTH,
Kirk Out!
|
|
|
|
|
Honestly, your use of a low resolution screen with other tweaks to make things larger on it is definitely out on the end of the bell curve. Expecting that any given user interface to work way out there is asking a lot, especially of free software.
The developer could have handled the situation better, but they've done their part in verifying that it works at 1366x768 for people with typical monitor settings.
I wouldn't bother to post a response. It may be seen as someone who is trying to get the developer to accommodate them way out on the end of the bell curve by shaming them into it, which won't be taken well. Instead, I'd investigate some virtual desktop products so I could use my monitor as a window I could pan around on a larger desktop. Such a tool would probably make many other user interfaces useable for me. When I find one, then I'd post a response about how you solved your usability problem, not directed at that developer, but directed at other users who may be in a similar situation.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Speaking as a developer with limited vision, usability problems are a tremendous pain, making a great application unusable for me. That said, complaining that a free tool doesn't meet your needs and its author should 'fix' it, is...I dunno, a waste of everyone's time?
Sometimes the user can fix the problem inexpensively by just purchasing a bigger monitor, though depending on the particular vision problem, this may not work as well as the uninformed may expect. Ah, but that's paying money to use a free application.
The author even looked at the request and determined that a fix would be expensive and demand for the fix was low. Which, for accessibility problems is very often the case (sigh).
|
|
|
|
|
That creepy reply from HandBrake's dev came off as so-o rude. It almost seems to escalate with condescension. When will people learn to be polite firstly? Rudeness is so-o time-consuming. This is the sign of a low-end type person, and no amount of proffered aid or insight will help them to grow up.
Remain Calm & Continue To Google
|
|
|
|
|
What surprises me most about this thread is the clear split between people that seem to feel the dev was perfectly within his rights, and the people that think he was rude. Nobody seems to be somewhere in the middle.
First of let me say that when it comes to Open Source I agree that if a bug bothers you, or a feature is missing, it is foremost our responsibility as developers to rather assist and implement it than file a bug report about it. The issues page is for users.
But sometimes, even us developers are just users, so we want to use software without having to write it first... and that's perfectly fine too. I can't be a contributor to every open source software package I use!  I would never be able to do anything for myself.
And that's the case with you Bill I think... in this case, you are just trying to be a user. And what happened is you got treated like a user by the developer.
As for the devs reply, I think the first part was perfectly polite and understandable. The second part is rather snarky though, and very dismissive. Perhaps it was just frustration at this issue being reported "again", or perhaps he is just an idiot. 
|
|
|
|
|
Sounds like they just need to enable scroll bars!
|
|
|
|
|
Okay, here's the bug.
You can see a picture of it (wish I could post inline) here ==> : http://raddev.us/images/mswin10Bug.png[^]
Here's how you reproduce it:
1. right-click your task bar
2. float over Toolbars >
3. move down to [Desktop] menu item and click it
4. Desktop appears at bottom of toolbar.
5. click the little double down-arrow and sometimes the menu will not move above the taskbar.
Sometimes!!!
Yes, my taskbar is on the left side (not at the bottom). 
Hello, Satya. Are you there? Can I have $500USD now? I'm reporting this and I'm doing your QA team's work so...
|
|
|
|
|
You are kidding, right?
MS have a QA team?
You could have fooled me... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: MS have a QA team?
Yeah, what was I thinking?
|
|
|
|
|
Will you pay your customers for finding bugs in your software? 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Absolutely - their payment is us fixing the bugs!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Absolutely - their payment is us fixing the bugs!
If only microsoft paid that way, even.
|
|
|
|
|
Who says I have bugs?
Who says I have customers?
|
|
|
|
|
raddevus wrote: Who says I have customers?
If you don't, then lucky you. They are the worst. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
If there weren't any customers, there wouldn't be any bugs.
Hey, maybe this is Microsoft's new marketing ploy!?!
|
|
|
|
|
Thats why they have so many preview builds, So they get reported for free.
|
|
|
|
|
Yes they just do heat mapping across the globe.
Microsoft Dev: "Oh, look we just released Win10 update to Europe and it's glowing red hot....Better put a fix in on those new functions."
|
|
|
|
|
64,763,985 people have reported the bug where daring to use the Save comdlg instantly crashes the program that you're trying to save from (kinda the worst possible time for a program to crash), so it's no wonder ms' profits are down.
And no, they haven't done a damned thing about it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It's a feature 
|
|
|
|
|
Sander Rossel wrote: It's a feature
Right. I should've just changed my perspective and I would've instantly seen that it's a new font type.
The type you can't read because it's behind some other window. 
|
|
|
|
|
bar.Color = Colors.Transparent; 
|
|
|
|
|
Now we just need a catchy title for this new technology. We can always completely abandon it later and act like we've never heard of it.
Let's see...
ActiveX? Nah.
XNA? Nah.
SilverLight? Nah.
WinRT? nah.
Here's one I don't think is taken:
UWA -- I don't know. I think I'll abandon it soon.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
