▲ 8 r/iphone

Months of Chasing a Mysterious Green Camera Dot… Solved

For months I kept noticing the green camera indicator on my iPhone randomly lighting up. I was worried that some app was accessing the camera in the background without my knowledge.

I went through all my apps, changed settings, searched online, and couldn’t find any explanation.
One thing I did notice was that it happened most often while scrolling through my Home Screen looking for apps, but I never figured out why.

Today I accidentally solved the mystery.

I was swiping to the widgets screen and saw the green dot light up again. This time I paid close attention and realized my Camera app icon is 2 rows above the dock. Even a slight touch on the Camera icon while swiping, without actually opening the app, is enough to trigger the green camera indicator.

It looks like iOS starts preparing the camera even before opening it.

So after months of thinking something shady was happening in the background, it turned out it was just my fat thumb grazing the Camera app while swiping. 😅

Has anyone else noticed this?

reddit.com
u/ganeshrnet — 2 hours ago

TODO comments are suddenly highlighted in Android Studio Quail 1, and LSP4IJ is causing issues. Anyone else?

I upgraded to Android Studio Quail 1 | 2026.1.1 Patch 2 on macOS 26, and ever since then every comment that starts with // TODO: gets this warning style/highlight. (todo)

It wasn't happening in the previous Android Studio version. The only thing that changed was upgrading to Quail 1.

Example:

// TODO: Some todo message here (todo)

Now it gets highlighted like this (see screenshot).

https://postimg.cc/3dWmnr8F

Apart from that, Quail 1 also forced me to install and use com.redhat.devtools.lsp4ij. Since then I have been running into a lot of annoying issues with formatting, linting, and editor behavior in the Android Studio IDE. Overall the editing experience feels much worse than before.

Is this a known issue with Quail 1 or LSP4IJ?

  • Is there any way to disable the TODO highlighting?

It's becoming pretty frustrating since this wasn't a problem before the update.

u/ganeshrnet — 1 day ago

Dart TODO comments are suddenly highlighted in Android Studio Quail 1, and LSP4IJ is causing issues. Anyone else?

I upgraded to Android Studio Quail 1 | 2026.1.1 Patch 2 on macOS 26, and ever since then every comment that starts with // TODO: gets this warning style/highlight. (todo)

It wasn't happening in the previous Android Studio version. The only thing that changed was upgrading to Quail 1.

Example:

// TODO: Some todo message here (todo)

Now it gets highlighted like this (see screenshot).

https://postimg.cc/3dWmnr8F

Apart from that, Quail 1 also forced me to install and use com.redhat.devtools.lsp4ij. Since then I have been running into a lot of annoying issues with formatting, linting, and editor behavior in Flutter/Dart files. Overall the editing experience feels much worse than before.

Is this a known issue with Quail 1 or LSP4IJ?

  • Is there any way to disable the TODO highlighting?
  • Has anyone else using Flutter/Dart run into these issues after upgrading?

It's becoming pretty frustrating since this wasn't a problem before the update.

u/ganeshrnet — 1 day ago

Looking for the Finder/NSTableView multi-selection algorithm

I am building a non-SwiftUI/non-AppKit macOS application with a custom table view. Right now I am implementing multi-selection, and I want the behavior to match Finder/NSTableView as closely as possible.

I am looking for the underlying selection algorithm for interactions like:

Click
Cmd + Click
Shift + Click
Up / Down
Shift + Up / Down
Cmd + Shift combinations

I am looking for the actual selection logic, not AppKit APIs. Things like how the selection anchor is managed, how different mouse and keyboard interactions affect the selection, and all the edge cases that make the native experience feel consistent.

I have searched quite a bit but have not found anything comprehensive.
Does anyone know of an article, GitHub repository, gist, reverse-engineered implementation, or any other reference that documents the complete macOS multi-selection behavior?

Any help would be greatly appreciated. Thanks!

reddit.com
u/ganeshrnet — 12 days ago
▲ 0 r/MacOS

Looking for the Finder/NSTableView multi-selection algorithm

I am building a non-SwiftUI macOS application with a custom table view. Right now I am implementing multi-selection, and I want the behavior to match Finder/NSTableView as closely as possible.

I am looking for the underlying selection algorithm for interactions like:

Click
Cmd + Click
Shift + Click
Up / Down
Shift + Up / Down
Cmd + Shift combinations

I am looking for the actual selection logic, not AppKit APIs. Things like how the selection anchor is managed, how different mouse and keyboard interactions affect the selection, and all the edge cases that make the native experience feel consistent.

I have searched quite a bit but have not found anything comprehensive.
Does anyone know of an article, GitHub repository, gist, reverse-engineered implementation, or any other reference that documents the complete macOS multi-selection behavior?

Any help would be greatly appreciated. Thanks!

reddit.com
u/ganeshrnet — 12 days ago
▲ 6 r/dartlang+1 crossposts

I just released a new Dart package: pathify

Pub: https://pub.dev/packages/pathify

GitHub: https://github.com/ganeshrvel/pub-pathify

I was working on a project where I needed proper Windows path parsing and handling. Dart's standard path utilities don't really handle Windows paths fully, especially things like UNC, verbatim paths, device namespace, etc. I needed something reliable for that.

Rust has really solid path handling, especially on Windows, so I decided to port Rust's std::path into Dart.

I should admit this upfront, a bit embarrassingly. I ended up using Claude to translate most of the Rust code into Dart. I am generally not a fan of blindly relying on LLMs for code like this, especially for something this low level. But I simply didn't have the time to manually port the entire thing.

So this is not me claiming this is perfect or battle-tested in every scenario. It passes 850+ tests, but that doesn't mean it won't break in some edge cases. If you use it and something blows up, please open an issue or a PR.

Some highlights:

• Byte-level path handling instead of string-based
• Works with both UTF-8 (POSIX) and UTF-16 (Windows)
• Full Windows prefix support: UNC (Universal Naming Convention), DeviceNS (Device Namespace), Verbatim, VerbatimUNC, VerbatimDisk, Disk
• Platform-agnostic. You can parse Windows paths on Unix and vice versa
• No normalization or mutation. Paths are preserved exactly as given
• Handles emoji, foreign scripts, and even invalid sequences safely
• Lightweight with no third party dependencies

If you're doing anything low-level with file paths or need proper Windows support in Dart, this might help.

Would love feedback

u/ganeshrnet — 2 months ago