Recent Posts

Pages: [1] 2 3 ... 10
1
News / Re: Version 7.4 has been released
« Last post by Andreas on August 28, 2017, 11:46:03 AM »
See the changes at the WinFIG main page
2
Bug Reports / Re: LaTeX/Rigid flag status hardly visible
« Last post by CrazyL on August 17, 2017, 07:46:41 AM »
Quote from: Andreas
I can also modify the style and change the pressed state color. Perhaps that's what I will do.

Thanks for your reply, that would be great. I guess a background of dark gray could do the trick and would not be offensive.
3
News / Re: Version 7.3 has been released
« Last post by Andreas on August 16, 2017, 10:08:58 PM »
See the changes at the WinFIG main page
4
Bug Reports / Re: LaTeX/Rigid flag status hardly visible
« Last post by Andreas on August 16, 2017, 03:11:27 PM »
Yes, that's the look of the Fusion widget style. The light look is lacking some contrast. Here you can see the available styles: Qt Widget Gallery. The problem is that only Fusion is available on all platforms and each style has a little bit different layout metrics, so I would have to make widget layouts that fit all possible styles, which can be a lot of fiddling around. Havin one style makes it easier.

I could use a checkbox instead of a push button, but it needs addditional horizontal space for the label. I can also modify the style and change the pressed state color. Perhaps that's what I will do.

However, on my monitors the pressed state is quite distinguishable, but I have IPS panels on both my desktop and my laptop. I know that TN panels are lacking contrast and are fading colors.
5
Bug Reports / LaTeX/Rigid flag status hardly visible
« Last post by CrazyL on August 16, 2017, 12:04:27 PM »
Version: 7.2

In the "Text" sidebar, it is very hard to see whether the "LaTeX/Rigid" flags are set or not:


Rem.: I added the big black frames to put both sidebar snippets right next to each other.

On the right side where both flags are set, the label text has a very slight shadow. That's the only difference between the two. In previous versions I remember that the label background was darkened when one of those flags was set -- I'd like that solution better as it's a lot easier to see.

Thanks for your on-going work on that great tool!
6
WinFIG and LaTeX / Re: Problem with special text and export
« Last post by mgwerder on March 12, 2017, 10:07:23 AM »
I think I got somewhere. The following envelope seems to work:
Code: [Select]
\documentclass[11pt]{standalone}
\usepackage{xcolor}
\usepackage[pdftex]{graphicx}
\pagestyle{empty}
\begin{document}
\input{\jobname_temp.pdftex_t}
\end{document}

Make sure that you do not scale when exporting (as this seems to mess up a lot). If there is one day a better  export function to PNG I will welcome it with open arms. In the meantime this does the Job for me.

Thanks for the help.
Martin
7
WinFIG and LaTeX / Re: Problem with special text and export
« Last post by mgwerder on March 09, 2017, 04:26:35 PM »
Hmmm ... that causes a Major headache. The files generated by pdftex scale ugly as the font size is not adapted.

I could use the PDF generated as you sugested but the envelope is currently (on my Installation) just the documentclass. I tried to use the envelope from the preferences tag with COLORTOKEN and TEXTTOKEN but that did not work. any Chance you know a valid envelope for this function?

Regards
Martin
8
WinFIG and LaTeX / Re: Problem with special text and export
« Last post by Andreas on March 09, 2017, 02:58:56 PM »
The on-screen rendering is only a convenience feature. It does not mean that LaTeX can be rendered like that in all output formats. When you export directly to PNG or PDF, no LaTeX processing is applied, and therefore you won't see LaTeX formatting. I'm contemplating about adding such a feature, but it's not trivial.

Usually you would export to pstrickts, pstex or pdftex and include the resulting files in a LaTeX main document. That's what you usually do when you write a paper and include WinFIG/Xfig draings.  See the FAQ and the forum for info. But remember that the actual look of the LaTeX texts depends on document class, styles etc in the main document. When WinFIG generates the graphics snippets for viewing on screen, it uses an envelope as a replacement for a main document in which it wraps the LaTeX texts. You can edit that envelope in the preferences (TeX view) to match your main document.

However, there is a convenience option in pstex/pdftex exports called "export both parts and create a document..." that can be used to create a one page PDF or PS in one step. WinFIG will create the envelope on the file and send it through LaTeX tool chain.
9
WinFIG and LaTeX / Problem with special text and export
« Last post by mgwerder on March 09, 2017, 01:22:31 PM »
Hi everybody

I have a Problem driving me currently up the wall. When drawing Images text flagged as "Special" renders perfect on screen as shown in the first attachment. Whenever I export an image (I checked Export to PNG and PDF) Special text is no longer rendered (as shown in the second image attachment).

Additional information:
  • It does not change when closing and reopening WinFig.
  • Winfig is a registered winfig Version 6.2. The "About WinFig" says "Ghostscript binary found in: not found".
  • Ghostscript and Latex are in the System path
  • OS is  a Windows 7 64 Bit
  • Ghostscript is Version 9.2 (32 and 64 Bit binaries available). Path to 32 Bit Version is manually specified (using the browse button and picking the gswi32 executable) in preferences (behaviour does not Change regardless of the used Version or Setting to "automatically determine...").
  • Flush Latex Images does not solve the problem
  • When text is edited the Rendering within WinFig is updated

Any suggestions where to look for the problem?

Regards
Martin
10
WinFIG on Mac OS / Re: Libraries folder location
« Last post by Andreas on July 04, 2016, 10:13:23 PM »
Put it under WinFIG.app/Contents/MacOS/Libraries in another subfolder i.e. "mine". So, the full path to the drawing foo.fig would be
"WinFIG.app/Contents/MacOS/Libraries/mine/foo.fig".

You can navigate inside the WinFIG.app with Double Commander or with finder using "Show package contents". I'm thinking about moving the libraries to the user home, because the installation folder has access restrictions on Windows. But this will be only in a future release.
Pages: [1] 2 3 ... 10