Development ⇒ TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
When installing Alpha 2 over Alpha 1, I get several times the message, that files which I want to overwrite are newer than the ones in the installation package.
Happy new year to all of you!
Learn LaTeX easily with newest books:
The LaTeX Beginner's Guide: 2nd edition and perfect for students writing a thesis
The LaTeX Cookbook: 2nd edition full of practical examples for mathematics, physics, chemistry, and more
LaTeX Graphics with TikZ: the first book about TikZ for perfect drawings in your LaTeX thesis
Re: TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
2. If TXC 2.0 Alpha 2 has been so installed, then it crashes on startup. Deleting HKCU\Software\ToolsCenter fixes the problem (while loosing customizations!).
3. Toolbars still flicker (refresh) during compilation (see: http://www.latex-community.org/forum/vi ... 487#p26104).
And a happy New Year!
TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
I can't reproduce this problem on Windows 7. Which toolbars flicker exactly? All of them?Izmi wrote: 3. Toolbars still flicker (refresh) during compilation (see: http://www.latex-community.org/forum/vi ... 487#p26104).
If possible start regedit.exe, navigate to HKEY_CURRENT_USER\Software\ToolsCenter\TeXnicCenterNT\Workspace, export it as a .reg file and attach it here.
http://www.texniccenter.org/
TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
Thanks for your quick reply!
All toolbars with icons flicker when I compile a larger tex-file (compilation takes 20-30 seconds). I use Win 7 x64 (fully patched); I'll create a short movie with my digicam when I'm home to illustrate the issue.
From the current installation (which works) or the one which lead to crashes on startup? - I attached the current working one.Sergiu wrote:If possible start regedit.exe, navigate to HKEY_CURRENT_USER\Software\ToolsCenter\TeXnicCenterNT\Workspace, export it as a .reg file and attach it here.
- Attachments
-
- txc-2a2_workspace.zip
- (51.45 KiB) Downloaded 1492 times
Re: TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
http://www.texniccenter.org/
Re: TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
http://www.texniccenter.org/
TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
Yes, this is what I mean (or more precisely: I believe that we mean the same).Sergiu wrote:I could observe some flickering of toolbar grips on the left and right side of every toolbar when running Windows 7 x64, is that what you mean?
Re: TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
The bug is not fully reproducible. The following steps trigger it sometimes:
1. Open TXC 2a2 with a project.
2. Let Windows go to standby.
3. Resume.
4. Repeat steps 2 and 3 some times.
5. Let Windows hibernate.
6. Resume.
Expected result: TXC 2a2 is in the state as before.
Observed result: TXC's window is not correctly painted. In the screenshot, the red area is of interest. I colored the area red. The actual color is white.
Re: TeXnicCenter 2.0 Alpha 2 (Build 1071) Issues
However, there is one serious problem that prevents me from switching to 2.0 Alpha: it crashes with the Visual C++ runtime error when a non-Unicode (such as ANSI) tex file (including template) is opened or saved. Choosing the UTF-16 (not just UTF-8) encoding avoids the crash, but MikTeX seems unable to compile such tex files.
I did some experiments and found the reason. In "Control Panel / Regional and Language Options", I have chosen to use the "Chinese (PRC)" code page for all non-Unicode programs, which is necessary for me as I still have many native Chinese programs on my machine. This bug is reproducible. Using the Chinese edition of "Visual C++ 2008 Redistributable Package" instead of the default one does not help. Using the English code page makes everything return to normal. Chinese (and many other Asian language) code pages are quite different with western language code pages as multiple bytes are required for each character. I suspect that some earlier reported "runtime error" bugs are also related to this.
The 1.0 Stable version does not have this problem.
I would be very grateful if the development team could fix it.