Enable missing disclosure triangles in Finder

The problem is with the arrangement chosen for the list view. Using any of the following methods, choose Arrange By | None:

The View menu from menubar
The gear icon in the Finder window
The contextual menu (right + click mouse button)

The Finder in Mac OS X is the application is always running and provides access to the file system of the computer. This is the Windows Explorer on Windows systems, or something like Nautilus on Gnome-based Linux systems. The primary interface is a folder paradigm that presents files and folders in a number of different views.

On the Mac, these views are icons, list, columns, and Cover Flow. To the Finder, the list view is a "stacked" presentation of the files with alternating background colors and a nice feature Apple calls a "disclosure triangle." This control is present on directory items, and when clicked, will either expand the listing to show a nested view of the contents of that folder or contract an already expanded listing.

Finder in Mac OS X with disclosure triangles in list view.

The problem is that sometimes these disclosure triangles aren't present.

Disclosure triangles not present.

Setting the Arrange By option to "None" will restore the disclosure triangles.

Comments

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ). From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE: At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned. If it solves an authentication problem, then great. The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward. It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE: Step 1 assumes a connection being made from a Windows machine. If the connection is being made from something else, user credentials may actually be necessary. If the connect...

Orsburn (Static Content)

Search This Blog