Activity for Igor
-
Igor modified a comment on discussion VirtuaWin questions
Here's a similar thread https://sourceforge.net/p/virtuawin/discussion/257054/thread/8075fec747/ . Some people there reported that they were able to fix this by using "Hide by moving window" (works for me). Also, here's ( https://aka.ms/AArflbo ) a Microsoft Feedback Hub Problem report I just posted - consider upvoting it - sometimes they do listen and fix things (maybe 1% chance or so...).
-
I'm using VirtuaWin 4.5 on Windows 10 (22H2, 19045.4529). The Metro-style application windows (e.g. Feedback Hub, Settings, Microsoft Store, Calculator, ...) are not getting hidden from my taskbar when I switch to another virtual desktop with my VirtuaWin 4.5. The window itself is getting hidden OK, though. This seem to be a bug in the Metro-style windows framework, because all the other windows (e.g. Notepad) do get their taskbar buttons hidden OK. Although I found "Modern" (Metro) apps in background...
-
I'm using VirtuaWin 4.5 on Windows 10 (22H2, 19045.4529). The Metro-style application windows (e.g. Feedback Hub, Settings, Microsoft Store, Calculator, ...) are not getting hidden from my taskbar when I switch to another virtual desktop with my VirtuaWin 4.5. The window itself is getting hidden OK, though. This seem to be a bug in the Metro-style windows framework, because all the other windows (e.g. Notepad) do get their taskbar buttons hidden OK. Although I found "Modern" (Metro) apps in background...
-
Here's ( https://aka.ms/AArflbo ) a Microsoft Feedback Hub Problem report I just posted - consider upvoting it - sometimes they do listen and fix things (maybe 1% chance or so...).
-
Here's a similar thread https://sourceforge.net/p/virtuawin/discussion/257054/thread/8075fec747/ . Some people there reported that they were able to fix this by using "Hide by moving window". Also, here's ( https://aka.ms/AArflbo ) a Microsoft Feedback Hub Problem report I just posted - consider upvoting it - sometimes they do listen and fix things (maybe 1% chance or so...).
-
Currently, this is really the most disturbing issue in Notepad++, IMHO.
-
I do not see any issues with brackets in TeXstudio: 2.12.14, but the last point still stands for me. I'm not sure, whether Jan Sundermeyer's reply was "just explicitly define ifThisIsSotrue and ifThisIsSofalse in your own cwl" or not, thus I've just created github 532, hoping it would be a bit more illustrative.
-
I do not see any issues with brackets in TeXstudio: 2.12.14, but the last point still stands for me. I'm not sure, whether Jan Sundermeyer's reply was "just explicitly define ifThisIsSotrue and ifThisIsSofalse in your own cwl" or not, thus I've just created github 532, hoping it would be a bit more readable.
-
I do not see any issues with brackets in TeXstudio: 2.12.14, but the last point still stands for me. I'm not sure, whether Jan Sundermeyer's reply was "just explicitly define ifThisIsSotrue and ifThisIsSofalse in your own cwl" or not, thus I've just created github 532.
-
I do not see any issues with brackets in TeXstudio: 2.12.14, but the last point still stands for me. I'm not sure, whether Jan Sundermeyer's reply was "just explicitly define it in your own cwl" or not, thus I've just created github 532.
-
Too long bib tool-tips
-
The Qt bug mentioned above should be fixed in Qt 4.8.6/5.3.1. We now have builds with theses versions. Do they fix the problem? Nope. Not for me, at least. The "TeXstudio 2.12.6 (hg 6632:7777b2b8a906)" behaves just the same. Moreover, the built-in pdf viewer (txs:///view-pdf) opens on my "main" (#1) screen each time as well. (I have 3 monitors, and I'd like to put TexStudio main window to the 2nd and the viewer to the 3rd.) I move the viewer to the monitor I'd like Do not maximize it, just close...
-
I continiously run into the same thing using "TeXstudio 2.12.6 (hg 6632:7777b2b8a906)", Win7 x64. Probably, a large enough pdf is required to reproduce this (mine is 690MB when built with no compression xelatex.exe -synctex=1 -interaction=nonstopmode -output-driver="xdvipdfmx -z0" %.tex). If I scroll pdf back and forth during the compilation process - there's a ~99% chance that the bug do occur. If I don't touch it - there's still a ~5% chance to run into this. Reopening the viewer within TXS alone...
-
I continiously run into the same thing using "TeXstudio 2.12.6 (hg 6632:7777b2b8a906)", Win7 x64. Probably, a large enough pdf is required to reproduce this (mine is 690MB when built with no compression xelatex.exe -synctex=1 -interaction=nonstopmode -output-driver="xdvipdfmx -z0" %.tex). If I scroll pdf back and forth during the compilation process - there's a ~99% chance that the bug do occur. If I don't touch it - there's still a ~5% chance to run into this. Reopening the viewer within TXS alone...
1