> -----Original Message----- > From: Michael Wojcik [mailto:[EMAIL PROTECTED] > Sent: Monday, March 31, 2008 2:46 PM > To: lyx-users@lists.lyx.org > Subject: Re: WRB - Observations > > rgheck wrote: > > Michael Wojcik wrote: > >> > >> I don't think this is a bug in Qt, though arguably it's a missing > >> feature. Shortcuts are not first-class filesystem objects > in Windows. > >> They're files that are treated in a special manner by > Windows Explorer. > >> > > LyX uses Qt for its file dialogs, etc, so if this doesn't work > > correctly, it's got to do with Qt, bugs or otherwise. > > Agreed, though it would be good to know why people report > different behavior in different dialogs, and different > behavior on different systems. It's conceivable that > something LyX is doing is either triggering a Qt bug in some > circumstances (which might be avoidable), or at least causing > differing behavior where we could be consistent. > > If I weren't in the middle of about a zillion other things > I'd grab the current sources and take a look. (Maybe over the > summer I'll finally get a chance to dig into the LyX source.) > > Though, pace William, the *real* problem, as I wrote above, > is that shortcuts are not part of the Windows OS. They're > purely an application-layer artifact. Certainly not all > Windows programs handle them the way William would like. > (Windows users can try cd'ing across a shortcut in a shell > window - no go. cd'ing across junctions works just fine, > however, because they *are* first-class filesystem objects.) > > -- > Michael Wojcik
Please, it is not about how I would like things. Rather, it is not what one would expect, given familiarity with Windows. I do not expect that this is of concern to all, or even to any. It is only a noted behavior, which looks inconsistent with typical expectation. If the issue is indeed a Windows idiosyncrasy, then by all means just document it as unsupported. If the inclination is beyond just documentation, then by all means. Actually, I have not typically experienced this behavior, because I typically don't use shortcuts. Typically, I will use Windows Explorer and drill down manually in the hierarchy, typically shown to the left in the WE gui. In this one case, I have recently created the shortcut, in order to speed my access to the subtree that contains the papers I write. So, it was just by serendipity that I found this *bug* So, in truth, I don't think I've previously tried to use a shortcut in this way. wrb
