Urgent: Unresolved Logic Regression in v4.9.5 Selection Algorithm

[NayeM Raj]

Hi Image-Line Developers,

I am writing this follow-up regarding a critical bug in FL Studio Mobile v4.9.5 that I have reported previously. Despite your assurances, the issue remains unaddressed in the latest update.

As a Developer and Power User, I am disappointed to see that such a fundamental Selection Logic flaw has made it into the production build.

The Technical Issue: The selection block algorithm currently lacks a filter for track visibility status. When performing a block selection, the engine is pulling all track IDs within the defined coordinate range into the selection array, completely ignoring the isHidden attribute.

Why this is a "Breaking Bug" for Professionals: For those of us working on complex, multi-layered projects, "Hidden Tracks" are used for archiving or clean workspace management. When the selection tool ignores the hidden status, it leads to accidental deletions or unintended movements of archived data. This makes the "Hide Track" feature practically useless during the editing phase.

My Expectation: I am not just another casual user; I understand the underlying logic of this software. I expect a professional-grade DAW to respect its own UI states (Visibility/Hidden).

Please escalate this to your core engineering team. The fix is a simple conditional check: if (track.inSelectionBounds && !track.isHidden) { addToSelection(); }

I hope this time my feedback is taken with the technical seriousness it deserves. I am waiting for a hotfix or a confirmation that this logic regression is being prioritized for the next build.

Regards,

[ NayeM Raj ] Advanced FL Studio Mobile User & Developer

file.mp4

[maxklint]

This bug is fixed in version 4.9.6, we are roll...

[Kafkatrap]

NayeM Raj wrote: ↑Sun Jan 18, 2026 4:21 pm Hi I...