[flagged]
Is my vision that bad? No, it's just a bug in Apple's Calculator
281–290 of 408 posts
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#282Earlier quoted context omitted.
> Apple's greatest weakness is that many of it's fans and I'd assume people in house assume they are the epitome of UI design when actually it's not. Which led to people like me making a fool out of themselves. Always been using Android, and listened to iPhone users singing the praise of the amazing UI and UX of iOS. Well, eventually iPhone 12 Mini released so I figured, "why not give it a try, can't be worse than my…
> Edit: I just remembered the most egregious issue: How can I see the current year without having to open up a separate calendar application/put a huge widget on my home screen? I'm not a fan of Apple for many reasons and I agree with your overall sentiment (though not with the same voracity), but I'm really curious how _this_ is the most egregious issue for you. The calendar year changes so infrequently, why would y…
> but I'm really curious how _this_ is the most egregious issue for you.
Because it's so basic. Add a switch that lets me decide how I want the date to be displayed on the lockscreen/notifications centre.
> why would you need it featured so prominently?
It doesn't need to be more prominently than where the date is right now, I just want the current year next to it as well.
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#283Earlier quoted context omitted.
> And then CarPlay is just an abomination! Even the most basic things like "I'd like to answer a call while still being able to see the map I use for navigation" seems to be completely ignored and it honestly doesn't make any sense at all. I totally agree that this is terrible. But this kind of behavior always makes me wonder if this is a "passive aggressive safety" thing. I have a 2019 Subaru Impreza, and I can't ch…
> I totally agree that this is terrible. But this kind of behavior always makes me wonder if this is a "passive aggressive safety" thing. I'm 99% sure no one of the designers who created those UX flows have ever actually used CarPlay in real life, like the users do. It's really hard for me to imagine a designer coming up with an appropriate reason for blocking the map view because you answered a call.
I don't know why you are being down voted.
I know from first sources that it is true. The car dash design is completed independently of the UX/UI work.
And the designers/programmers never test it in the car. There is almost no iteration there. In fact the people I talked to worked remotes. They couldn't even try to get into a prototype car if they wanted.
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#284Here's something that really irks me. On macOS I'll use Spotlight (Cmd+Space) to do some quick math. For example, press Cmd+Space, type "1.2+3.4", and it sort of displays 4.6. Now to copy the results you either have to click the copy option in the dropdown, using your mouse (no thanks), or press enter to get the results in Calculator.
Assuming you last left the calculator in "Programmer" mode the calculator displays the value "4".
Ideally, pressing enter in Spotlight would simply replace the text in the input bar with the result. The equivalent Alt+Space tool in KDE (Plasma Search) performs math this way and it's amazing. I haven't used Quicksilver or Alfred in a decade but I'm sure they do the right thing, too.
Otherwise both Spotlight and Plasma Search are both pretty great. Type something like "14oz to lb" and they both display the result (though Plasma Search displays the exact "0.875 pounds" while Spotlight displays the rounded "0.88 pounds").
Overall I'm mostly disappointed with first-party Apple software. Being one of the richest companies in the world I have higher expectations.
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#285Here's something that really irks me. On macOS I'll use Spotlight (Cmd+Space) to do some quick math. For example, press Cmd+Space, type "1.2+3.4", and it sort of displays 4.6. Now to copy the results you either have to click the copy option in the dropdown, using your mouse (no thanks), or press enter to get the results in Calculator. Assuming you last left the calculator in "Programmer" mode the calculator displays…
Sounds like Alfred could solve this problem quite easily? I wouldn't give spotlight too much hope from Apple's end. Have seen some very nice Alfred workflows
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#286Earlier quoted context omitted.
I do a lot of stuff with blue/purple gloves, and I can unlock my touchId device wearing those. Doesn't matter why/how. The fact I can shows how it is easy to bypass.
Can someone else wearing the same gloves unlock your device? Otherwise seems more likely the capacitive sensor isn't bothered by a few tenths of a mm of nitrile.
I've assumed it's enough oil/residue left in place that just pressing a clean solid surface to contrast the residue is enough to detect the pattern.
Can someone else do it? Quite probably, as I've tried using a different finger from the the registered finger with the glove and it unlocks.
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#287> I would contact Apple, if there was a feedback option, but there isn’t There is: https://feedbackassistant.apple.com/ That said, it isn’t very user-friendly, and I find that they don’t seem to pay much attention to it. When they do respond, it tends to be some form of “#wontfix. Please close this.” That looks like a fairly ugly little bug. I suspect they know about it now, thanks to the HN Bug Reporter. It tends to…
"We cannot process this report. Please attach 50GB of logs that may or may not include PII".
I've had enough cases where a simple screenshot or log snippet should have been enough to accept the bug report but instead they were closed because I cannot in good conscience attach all the data they want from a Mac that I use for my day to day work.
:shrug:
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#288Earlier quoted context omitted.
> You cannot sideload apps that are Open Source. You cannot install emulators or fullspeed VM software. You cannot switch the browser out for one you would prefer with controls amenable to your satisfaction. Worth noting that while this used to be true, those things are now/soon geofenced features that only Europeans get to enjoy. Too bad if you happen to live in the home country of Apple.
I don't believe you're allowed to run fullspeed VM software or JIT-enabled browsers, even with the DMA. Nothing has been super set-in-stone yet, but those are the terms Apple is intent on promoting.
> I don't believe you're allowed to run fullspeed VM software or JIT-enabled browsers, even with the DMA.
You can. There's a new JIT entitlement for web browsers in Europe. It's still limited to _only_ browsers, so emulators are out of luck.
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#289Earlier quoted context omitted.
CarPlay is a thing because carmakers just can't seem to make a decent "radio" with a touchscreen no matter how they try. It would be nice to see a business school case study that reveals why.
Radios don't need a touch screen. Old button radios are pretty intuitive. The display/touch aspect is because people want navigation, apps like deezer/itunes/Spotify, etc. Then you have to think about updates/real time data. How does that work? Does the car need its own data plan? Or do we do everything via usb and just do everything offline? And then people still expect to connect their phones to the car, for calls/…
In theory you could use a smartphone as data provider for updates etc
Re: Is my vision that bad? No, it's just a bug in Apple's Calculator
#290A friend doing homework for a university assignment, circa Leopard or Snow Leopard, noticed that Calculator produced negative values when raising a negative number to an even power.
The bug turned out to be in CFNumber, in Core Foundation. CFNumber does a lot of fiddly stuff at the bit level for performance, and one of their optimizations for exponentiation was incorrect. Somehow it was never found by tests or due to buggy behaviors it created in other apps, but by someone clicking buttons and thinking critically about the output.