Chrome OS fixes my biggest complaint about “Tote” storage space



[ad_1]

Chrome OS 89 rolled out a few weeks ago with a treasure trove of new features heavily focused on productivity. One of these features is designed to give users quick access to downloaded files and screenshots. Formerly known as “storage,” “Tote” is a simple yet powerful addition to the Chrome OS shelf that’s guaranteed to improve the workflow of Chromebook-ers who do graphic design or frequently manage files uploaded to. from the web. When you click on the tote (located on the shelf to the left of the Phone Hub icon), you’ll see recently uploaded files and screenshots. Users can pin files to the top if they need quick access and don’t want specific files kicked from the queue.

As innovative as the Tote is, it has a glaring flaw. When the feature first appeared in Chrome OS Canary, I honestly thought it was just an oversight or maybe this feature hadn’t been added. I’m talking about the ability to delete files from the storage spaceā€¦ I mean Tote. In the Stable channel, the only way to delete a file from the Tote is to download more files and push back the previous ones. There is no granular control and I don’t like it at all. If you are recovering a lot of files and screenshots, you might need them to stay in the tote. You can still pin them for this, but you don’t have the option to completely delete the files.

Thankfully, the Chrome OS team recognized this omission, and the latest Canary Channel update brings a small, albeit powerful, change to Tote. Now when you right click on a file in the tote you have the option to delete it and it really made my day. I know. It sounds basic, but it is the behavior most people would expect from a “storage space” that contains shortcuts to files. This adds the ‘remove‘to the list of tools that already included the ability to copy an image, show parent folder, and pin files to the top of the tote. This just appeared in Chrome OS Canary 91, so I’m not sure how fast it will go to Stable. Having said that, this is a minor change. It’s plausible that the Chrome OS team can push it up the ranks in an incremental update as soon as they’re satisfied it’s stable and ready.

[ad_2]

Source link