Could someone (who does not - or no longer - experience this issue) try to open a file from "My network places" (without mapping it to a drive letter), then disconnect from the respective network and restart yes, the code lines you mentioned are a very likely candidate for the cause of the issue.Could someone (who does not - or no longer - experience this issue) try to open a file on a mapped network drive (one that has a drive letter), then unmap the drive and restart Tw?.a USB drive), then remove the drive and restart Tw? Could someone (who does not - or no longer - experience this issue) try to open a file on an external hard disk (e.g.Could someone (who experiences this issue) try with just deleting the openDialogDir key?.Could someone (who experiences this issue) try with just deleting the recentFiles key?.It seems that this problem relates to network drives. It may also be related to something in the underlying Qt framework, which could make it hard to track down, however. Another thing that has caused some problems in the past was spellchecking and highlighting huge documents, but that does not occur if you run Tw without opening a file in it. This requires crawling through directories (as given in the preferences), which may take some time although it should not amount to several minutes. One thing that has caused some issues in the past was checking which typesetting tools are available. Loading settings is one thing, of course, but that shouldn't be resource intensive. Some background: there is not very much Tw does during startup. what versions (of Tw and Qt) are shown under Help > About TeXworks.?.what is shown under Help > Settings and Resources.?.what paths are shown under Edit > Preferences > Typesetting?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |