OK. I will try some tests to see if I can pinpoint the problem. I have lots of .ijs files in a remote cloud folder, and many of these files have all-lower-case file names. I have a copy of that same folder of .ijs files on my local drive. When I try to use the JQt editor to open a file with an all-lower-case file name on the local drive (axis.ijs) by double clicking on the file in the JQt nav pane, the file loads, no problem. When I navigate to the same file with a lower-case file name on the cloud drive, double-clicking on the all lower-case file name does nothing.
So it isn't the file name. Maybe it's the full path. Here's the path to the file on my cloud drive: G:/My Drive/11-Jsoftware/1work/axis.ijs Yes, there are upper-case letters in the cloud file path, so maybe that is the problem. Let's check the path to the same file on my local drive. Here's the path: C:/Users/Skip/j64-806-user/1work/axis.ijs Well, that path has upper case letters in it as well, but the JQt editor has no problems with loading this file. So there is something different about the cloud drive that prevents the file from loading in JQt. How can I test to see if a drive is "case-sensitive"? Skip On Thu, Feb 1, 2018 at 5:09 PM, chris burke <[email protected]> wrote: > > ... 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 > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
