Bug 78315 - Provide Enhanced Path Checking capability
Summary: Provide Enhanced Path Checking capability
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Name
  Show dependency treegraph
 
Reported: 2014-05-05 22:44 UTC by Ewald Anderl
Modified: 2019-10-05 01:12 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Enhancement – Improved File Path Checking; screen shots and description (1.80 MB, application/vnd.oasis.opendocument.text)
2014-05-06 13:11 UTC, Ewald Anderl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ewald Anderl 2014-05-05 22:44:32 UTC
There does not currently exist an easy method to determine whether a path exists and is a directory, and  whether it is available for read and optionally for write access. Basic functions ( for example, the Dir() function, FilePicker dialog, and FolderPicker dialog ) do not operate as expected or consistently when confronted with error cases.

This functionality could be added as a new method of the Simple File Access object. There are numerous ways in which paths can have temporary of permanent failures due to permissions, SELinux violations, network failures, and network share security errors to name a few. Ideally with this enhanced method of checking for errors, the more obvious areas of potential failures would be screened out (e.g. – file does not exist) and it would provide a catch-all for all other failure cases. This method should also have the option to check for write access and return feedback if write access is not possible for any reason.

As another alternative, there is very similar functionality already included in the “setDisplayDirectory()” method of the FilePicker dialog when the LibreOffice dialog style is used. It will generate a user warning or error to the user but no feedback is provided to the program (for screen shots and more information see  3.2.2, “Debug Level Three (FilePicker Behavior)“ regarding Linux and 3.3.2, “Debug Level Three (FilePicker Behavior)“ regarding Windows).

I will upload a document with screen shots and other supporting documentation.
Comment 1 Ewald Anderl 2014-05-06 13:11:17 UTC
Created attachment 98560 [details]
Enhancement – Improved File Path Checking; screen shots and description

This document provides screen shots and supporting documentation for the desired capabilties incorporated in the enhancement request. Cross reference to other bugs found or confirmed while creating this document are also included.
Comment 2 Robinson Tryon (qubit) 2015-01-15 00:22:23 UTC
Noel: Thoughts on this rfe?
Comment 3 Robinson Tryon (qubit) 2015-03-15 15:31:14 UTC
(In reply to Ewald Anderl from comment #0)
> There does not currently exist an easy method to determine whether a path
> exists and is a directory, and  whether it is available for read and
> optionally for write access.

If such a method doesn't exist, then let's consider adding it.
Status -> NEW