Quote:
Originally Posted by JSWolf
The issue is not who uses FullScreenReading=true or not but that some are calling bugs when it doesn't work as expected when it's not even a beta feature.
It's not a bug when it's not beta and not meant to be used. Find some other term to call it because bug is incorrect.
|
Not discussing again,but even when you use an undocumented option that causes a device to act this strange, you can still call it a bug,because it wasn't there before, since a lot of functions are integrated into each other,you can never know which "legal" option can trigger it to as the resfresh part is used a lot more then only by reading.
Imagine how much (more sigh) disaster by example Windows would be if the Microsoft designers are acting the same "oh it is not documented so don't bother it.. "
"Messing around" and find something that is not intended to be found but still can let,in the worse case scenario and not with this "bug", crash the device is something that must be told to the developers.
A bug is a bug,even when it isn't in a documented part of the software, we can not know which else it does,and what else can trigger it.
Kobo build it into their software so they are going to do something with it, a lot of other options in the config file doesn't work anymore,this option is still there and we have no idea if it can be triggered by a normal feature of the device until someone discovers it.
If a never used software routine would be still in the I.S.S. station (i know there are some) and an action of one of the astronauts by accident trigger it,and the whole station vaporised.. i know for sure the developers down here would call it a bug, documented or not.