> ... but my original issue didn't have anything to do with the case of
file names

It surely did.

In all Windows systems up to now, the capitalization of filenames was
irrelevant. Two filenames that differ only in capitalization represent the
same file. Jqt ensures that they are treated equally by using the lowercase
name internally.

You are trying to open a file whose full pathname has uppercase characters
in a case-sensitive drive. That won't work, and requires changes to support
both case-sensitive and case-insensitive folders on the same platform.

Incidentally, the internal use of lowercase names on Windows has been our
practice since at least J6, so is not new to Jqt. JHS doesn't do this, so
should work on the new folder.


On Thu, Feb 1, 2018 at 2:05 PM, Skip Cave <[email protected]> wrote:

> The issue with case sensitivity for file names is an interesting problem,
> but my original issue didn't have anything to do with the case of file
> names. I just waned to be able to double-click an .ijs file in the JQt
> editor nav pane to open a file. This scheme doesn't work for ANY .ijs file
> names, regardless of case. This scheme works fine for .ijs files on a local
> drive, and doesn't work for files on remote derives like a Google File
> Stream drive. I can enter the G: file path in the JQt path field and SEE
> the list of .ijs files on my remote drive, but double-clicking the .ijs
> file icon will not load the file.
>
> I discovered a convoluted workaround for this problem by selecting File >
> Open from the JQt editor menu instead of using the JQt editor nav pane.,
> This results in the launching of a Windows Explorer window. Then I can
> enter the G: file path in the Explorer's path field, or navigate to the
> file/folder I want. Finally, I can double-click on the file, OR highlight
> it and click the Open button, to load the file.
>
> This tells me that there is just something wrong with the file access
> protocol in the JQt editor, not anything to do with the case of file names.
>
> Skip
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to