 |
version history: changes/fixes/new features
- Version 2.6.1 (2005-05-15)
- Edit Dialog Fix: fix for the edit dialog bug: when the form terminates,
e.g. is closed by the "X" the LaTex source was replaced with the last edited and saved source.
Now using "X" is like pressing "Cancel". "Finish later" is also fixed (before it behaved like Cancel).
- New combined Documentation. The content still needs some extra work...
- new buildin symbol in Texify: to
- Version 2.6 SR1 (2005-02-15)
- Workaround for Windows: Latex and argument files are now flushed to disk before tex2bmp is executed - before it could happen that the file was not written to disk before tex2bmp is executed (VBA bug)
- Mac: fix for the path fix in 2.6. Secondary volumes are now supported.
- Version 2.6 (2005-01-17)
- internal change, but important: the floating point values for magnification, brightness and contrast are now saved in a country independent way (no decimal- point or "comma")
!Therefore displaytex equations modified with 2.6 can cause problems (with magnification, contrast, and brightness) when edited in older Versions of TexPoint!
- internal tex2bmp on windows enabled (new global options)
- new buildin symbols in Texify: varphi, Upsilon
- Mac: unix path problem partly fixed: folder and file names in the path can contain spaces now (Do not use slashes, backslashes, colons, umlauts and other special characters)
- Windows: path problem when switching presentations fixed
- Mac: eps format available
- extended information dialog (if you have a problem, include this information in your mail)
- unicode problem with Symbol font in PowerPoint 2004 (Mac) fixed (texify)
- Version 2.5.1 (2004-09-15)
- internal changes: booleans are converted to "1" and "0" in the string version. Before, those were saved in a language dependant way. Visible result:
- transparency, blend, etc. settings are now displayed correctly in the Edit Dialog when editing a LaTex display
- function "ReadAllFile" fixed: no additional empty line is inserted when returning from the external editor
- global Variable "AddInName" introduced: The ppa file now only needs "TexPoint" (case insensitive) in the filename to be recognized as the TexPoint plugin
- edit dialog event loops avoided (sometimes let to "stack overflows" on mac)
- configuration dialog has new information page: Version, Addin name&path, presentation name&path, .... (on mac, see below)
- internal Tex2Bmp better integrated (uses now the global configuration, as it should)
- unique file names for pictures (this was already part of 2.0.3, but unfortunately dropped out in 2.5)
- Version 2.5 compared to Version 2.0.x.
- TexPoint has now a new, more flexible configuration: It uses a global (machine dependant) configuration file [TexPoint.ini (Win) or TexPoint.mac (Mac)]. Your can configure, e.g., the external programs used for the display generation or the external editor or you can select a default Latex source file.
- Since the common usage is to produce only a single one-line equation, a new simple Editor is available ("New LaTex equation" in the TexPoint menu).
- LaTex files and sources can be edited with an external Editor on Mac and Windows (available in the main Editor or the Configuration Dialog).
- pdf support on Macs.
- many internal optimizations.
- Version 2.0.3 (2003-10-20)
- Version 2.0.2 (2003-10-15)
- Support for Office 2003!
- Added support for nested superscripts and subscripts
- Split the distribution depending on the version of Office. This should fix the problems of using TexPoint on Office 2003 and Office 2000.
- July 16, 2003.
- When TexPoint is initialized it makes itself AutoLoad. This is for those users for which the installation does not succeed to load the add-in, and they have to load it manually. Now, they only need to do that one.
- I added some more code to the script that is supposed to register TexPoint during installation. Hope that now it works on Office 2000 as well.
- Version 2.0.1 (2003-07-15)
- In the process of fixing the editing of a grouped display, in TexPoint 2.0, I have used a feature that does not work on Office 2000. This lead to "Compilation error in hidden module: DisplayTex". I have removed the offending code.
- I have fixed a couple of small errors in the encoding of macros for inline mode.
- I fixed a bug with the resizing of the display source edit box. The size was not saved in the object.
- I have fixed a bug with the inline mode. Characters from macro expansion would appear with the old font of the paragraph. Now they appear with the right font.
- Fixed a few errors in the EMF displays.
- The About message box and the error logs now specify the build date
- Fixed an error that was leading to trying to access "\tex2bmp.exe".
- Version 2.0 (2003-07-01)
- I have added some initial support for outline displays. Unlike bitmaps they are much more compact and can be scaled to any size without showing ragged edges. The disadvantage is that such displays will show correctly only on machine that have TexPoint installed (or more precisely the TrueType version of the Latex fonts). Thanks to Wolfgang Glunz for writing the pstoedit tool and to James O’Brien for figuring out how to fix some problems in it that prevented its use in TexPoint.
- Fixed a bug that prevented the editing of a TexPoint display that was grouped with other displays.
- I am using MakeMSI now to create the installation package. One of the benefits is that TexPoint will automatically uninstall itself if you try to install a newer version. Thanks to Dennis Bareis for writing this useful tool.
- You can configure now the name of the Ghostscript command to use.
- I added a number of entries to the FAQ.
- Version 1.5.4 Mac (2003-04-14)
release of the first Mac ported Version.
- December 20, 2002.
I have added support for using an external editor to edit the Latex sources.
- Version 1.5.4 (2002-12-19)
- December 19, 2002.
I have rewritten the section of this manual related to the Display mode to reflect the many changes that have occurred.
- December 19, 2002.
Added the 2400dpi resolution for displays. Added the PNG bitmap format and made it the default. You should use this one always because the bitmaps are MUCH smaller.
- December 18, 2002.
Added a workaround for a strange transparency bug. Sometimes PowerPoint will change the background of an imported image to rgb(254,254,254) while TexPoint was setting the transparent color to white. Thanks to Michael Isard for investigating this problem. Since I am not able to predict when this will happen I added a checkbox that allows the user to tell TexPoint that it should workaround this problem (on a per-bitmap basis). It seems that this might be due to a bug in Office XP (see MSKB article 318042) and that it should be fixed in Office XP SP2. However, I still see the problem even with SP2.
- December 17, 2002.
John Papandriopoulos [jpap@users.sourceforge.net] has contributed a number of changes:
- Rearranging the TexPoint menu so it is better partitioned into different sections based on functionality.
- Added accelerator keys to all controls for quick keyboard-only access.
- Added a 'word wrap' option for the LaTeX source editors
- Set the LaTeX source editors to use fixed with fonts, as well as respond to the Tab key (previously it would shift the focus to the next control)
- Rearranged the look of the configuration dialogue to make it more attractive and user friendly.
- Removed the height/width controls on the edit display dialogue and configuration dialogue. The edit display window can now be resized using the mouse by clicking and dragging the bottom-right corner of the window.
- It seemed the TexPoint GUI would get confused when clicking on different combinations of 'Transparent' and 'Blend' checkboxes. This has been fixed.
- The GUI for the edit display dialogue has been rearranged with the addition of a tabbed page separator, to also make it more attractive and user friendly.
- A status bar has been added to the bottom of the edit display dialogue to show the approximate image size.
- Setting the view for the documentation slides to "fit" so that they are best viewed on any resolution a user might have.
- December 16, 2002.
Nicoli M Ames [nmames@MIT.EDU] has contributed code that allows you to close the display source editor window by pressing the X and not lose the display.
- December 5, 2002.
Added support for incorporating EPS instead of bitmaps for the displays. This works on Office XP and might work on other versions. The results, however, are not great. As far as I can tell the fault is with PowerPoint that insists on translating Type 1 fonts into polygons. For now the PNG bitmap format looks better than EPS. I’ll try other ways to incorporate vector graphics into PowerPoint.
- Version 1.5.3 (2002-12-01)
Pretty much like the beta version except with the "transparency" fix disabled.
- Version 1.5.3-beta (2002-11-24)
- Added the cmr10 (Computer Modern Regular) and cmmi10 (Computer Modern Math) fonts to the Latex distribution. You can use these fonts in the text of your slides to ensure that your symbols and variables look the same as in the displayed equations. You can invoke the new fonts by selecting an area and pressing (ALT-X-M for math, or ALT-X-L for latex font). Alternatively you can use the TexPoint menu. Or, you can simply write "\cmr{xxx}\cmm{yyy}" to typeset xxx in the regular font and yyy in the math font.
- Complete change of the mechanism used to invoke the underlying tex2bmp script. The "interactive" feature is always turned on. The "timeout" feature is gone (now TexPoint waits until Latex terminates). And most importantly, TexPoint does not get stuck if you kill the Latex window with CTRL-C.
- Fixed a bug that led to "error 5 (position 162)" if the tex2bmp script cannot be found in the TexPoint directory. This could only happen if there is a problem with your installation of TexPoint. Now a message to that extent appears instead.
- Added entries to the FAQ related to copy/paste of Latex source, limitations of inline mode and the transparency problem that was fixed.
- September 11, 2002.
- Added an error message when a display is created without a slide on focus. Before it would just fail.
- Changed the names of the HTML files to have extension .html instead of .htm
- Version 1.5.2 (2002-09-04)
- Fixed a bug that disabled the Blend button if the Transparency button was toggled
- Redone the TexPoint configuration dialog box with multiple panes
- Added the option to save the default bitmap parameters on a per/presentation basis
- Made ESC work on the display edit box
- Version 1.5.1 (2002-06-26)
- From now I will generate minor version numbers when I make changes
- Fixed a problem with the generation of floating point numbers in the command line for Ghostscript. The previous implementation was sometimes using the "," as the decimal separator instead of ".".
- May 8, 2002.
Fixed a bug that led to Overflow exceptions when the resolution and number of colors were too high.
- April 24, 2002.
Added an entry to the FAQ about empty displays.
- March 11, 2002.
The timeout value is now saved with the display.
- Version 1.5 (2001-11-29)
Fixed a few more bugs that lead to errors on non-English installations of Office.
- November 26, 2001.
Improved the handling of different resolutions. Fixed a bug that introduced several seconds delay in displaying a newly edited display.
- November 26, 2001.
Fixed bug: when working with Office 2000 the TexPoint menu would not appear. Thanks to Alberto Bemporad, Dr. Moshe Idan for trying the beta and reporting the bug and especially to Tobias Preusser for actually localizing the bug.
- Version 1.5 BETA (2001-11-25)
- Much improved error handling including logging.
- Added better support for international versions of Office. Previous versions when loaded in non-English versions of Office sometimes failed with "Visual Basic Error 5" when resetting TexPoint or when right-clicking on the slide. This should not happen anymore.
- Added support for changing the font size in the edit box with the Latex source TexPoint display
- Added support for selecting between 300dpi and 600dpi resolution for the display. This is useful when you need to magnify a display to the point where it starts to look ragged.
- Fixed a bug that would result in loss of the changes to the source of a display after an error occurs.
- Added a workaround for a bug that manifests with a "Visual Basic Error 5" on Windows 95/98 when latex is processing the display. However, TexPoint behavior on Win 95/98 is likely to continue to be flaky due to a bug in these versions of Windows.
- Added a new button to the display edit box that allows the user to save the changes without regenerating the bitmap
- Fixed a bug that would result in loss of the TexPoint source when the bitmap is copied or cut and then pasted. This is rather a workaround a strange behavior in Office.
- Expanded the "Debugging" section of the manual.
- Many thanks to Jonathan de Halleux and Alberto Bemporad for actually going through the trouble of opening the Visual Basic Editor and giving me very precise error information. Thanks also to Dr. Moshe Idan for very detailed error reports.
- October 10, 2001.
I have fixed a problem that sometimes leads to empty displays. The cause was that dvips puts page size information in the Postscript file, which confuses Ghostscript. The current fix is to pass -E to dvips. Thanks to Jonathan E. Luntz for helping me track this problem.
- September 8, 2001.
Fixed a bug due to which the symbol characters would inherit the subscript or superscript attributes of the preceding characters.
- April 14. 2001.
Added error message about remote presentations. Fixed some missing macro symbols.
- February 13, 2000.
Fixed the blend in mode. Previously TexPoint failed to pick up correctly the color of the background if it was inherited from the master slide.
- Version 1.4.2 (2001-02-12)
- February 12, 2000.
Changed tex2bmp to clean up %%BeginPaperSize ... %%EndPaper size in the .PS file. This is a workaround a "feature" of dvips in Miktex 2.0. Added a --keep command line option to tex2bmp to instruct it to preserve the intermediate files that it produces.
- December 11, 2000.
Changed the most frequently used AMS symbols to use heavier strokes. Manually hinted some of the symbols.
- Version 1.4.1 (2000-12-05)
- December 5, 2000.
Added configuration options for the script that converts .tex into .ps.
- December 5, 2000.
Added transparency option for displays.
- Version 1.4 (2000-11-27)
- November 27, 2000.
Added configuration option to automatically use bold face for the symbol fonts.
- November 26, 2000.
Created the Windows Installer package. The entire installation and uninstallation is now automated.
- November 25, 2000.
Edited the symbol fonts to add space characters and changed the codes for \wedge, \vee and other symbols since the old ones conflicted with codes for ^ and _ and \ which TexPoint interprets. The symptom was that a \wedge (or \and) on the slide would turn into the right symbol at the first ALT-X-X and then it would disappear at the second ALT-X-X.
- October 29, 2000.
Added option for the default magnification of displays.
- Version 1.3 (2000-10-19)
- October 19, 2000
Got rid of the edittex.bat script since making that to work on win98 turned out to be a nightmare. This was replaced with a souped-up version of the previous ps2bmp.pl called now tex2bmp.pl
- October 19, 2000.
Fixed a bug that led to an error message "Path not found" if a display was added to a new but not saved presentation.
- October 19, 2000.
Added workaround the Win98 problem that the shell does not reliably return error codes.
- October 18, 2000.
Added timeout for the shell invocation and added workaround for shell bug in Win95 and Win98 (the shell function does not reliably return the error code in VB and in Perl).
- October 18, 2000.
Added various tools to the TexPoint menu: toggling font, bullets and paragraph numbering.
- October 18, 2000.
Fixed a bug that made the project refer to the Rich Text Control, which is not available if you do not have visual Basic installed.
- October 13, 2000.
Added color support and fixed a bug related to Windows 98.
- Version 1.2 (2000-10-12)
I changed completely the initialization process. I added dialog boxes for both TexPoint configuration and for display editing. This means that there is no need to use an external editor. I have created a special TexPoint menu instead of using the built-in Tools menu. This means that the new key shortcut start with ALT-X instead of ALT-T.
- October 10, 2000.
Fixed bug related to copying the style of the macro argument from the slide.
- October 10, 2000.
Thanks to Yummy I got my fonts cleaned up and I replaced my homemade amsextra.ttf font with a variant of the AMS stmary10.ttf font. I have also defined a few more (obscure) macros.
known, but so far unsolved problems (not essential ones though)
- on mac: after external edit, all controls in the TexPoint dialogs need double clicks instead of single clicks to do something
- in the simple equation dialog, the option "use font color" (=use the selected text color) does not work correctly.
- there seems to be a problem with eps format equations - so far I do not know the reason for this.
debugging/(modifying) TexPoint yourself
Basic has awful exception handling support. I did my best to use whatever it
provides but I am sure that there are situations that I have not provided for.
The typical manifestation is that you get a "Visual Basic Error
5". Should you be willing to understand more of what is going on (and thus
help me fix it) here is what you can do (it takes only a couple of minutes
besides reading the directions)
- Open TexPoint/TexPointmacros.ppt (this is
where the VB source lives. TexPoint.ppa is the compiled version; you can
get this file if you choose to install the sources as well). Follow the
instructions on the first slide of this presentation.
- Start using TexPoint and when you run into
an error then hopefully you will have the choice to press a button
"Debug" which will take you to the line containing the error.
You can then tell me what is going on or you can try your hand at using
the Visual Basic Debugger.
Here is the structure of the code:
- VBAProject/Modules/Init - initialization
code, Auto_Open, Auto_Close, help and the such
- VBAProject/Modules/InlineTex - the Tex
interpreter that implements Inline Tex, along with the definitions of the
macros
- VBAProject/Forms/Edittex - the main code
for the display mode. This contains the form that you get when you use the
display mode along with the user interface. Do View/Code to see the code
or View/Object to see the Form.
- VBAProject/Modules/DisplayTex - some more
user interface for when you use the right-click to work on displays
- VBAProject/Forms/TexPointConfig - the configuration form and user interface
If you make changes to the code here is what you need to do:
- In VBEditor: File/Save, followed by Debug/Compile (to make sure you do not have compilation errors)
- Switch to PowerPoint:TexPointmacros.ppt,
File/Save As, in Save as type choose "PowerPoint Add-In
(*.ppa)", and then select the location where you want to save. You
can ever overwrite an old PPA if it is not loaded.
- In PowerPoint do Tools/AddIns/Add New, select the saved PPA.
- Tell me if you want others to benefit from your work.
Consider that the complete code consists currently of about 6000 lines VBA.
Mac compatibility guidelines or How to keep TexPoint compatible to Office X/2004
Preliminary Remarks:
- External programs are called through Apple-Script commands on Mac
and with Windows SDK functions on Windows
-> use the TPexec command in the Tools module
- conditional code is used via "#if ... #else #end if" directives
- AddIns are OS-dependent, i.e., the Office XP PPA does not work with Office X/2004
-> for compilation of the mac ppa, a Mac is necessary
- A "nasty" problem is the MS-made name inconsistency of the VBA library
"Microsoft Visual Basic for Applications Extensibility":
-> under Windows it has a version number 5.3 attached
-> under Mac OS X not: if not corrected, some simply VBA function do not work
solution: change it manually in VB editor: Tools->References
- The windows version uses an external Tex2BMP program, the Mac version the internal VBA version
-> maybe on Windows one should switch to the internal one, too.
Userforms:
- Tahoma font is not available in Mac OS X and when copied from Windows it is almost unreadable
-> Arial has to be used as Userform font
- Bitmaps in Userforms have to be bmp files! If transparent gifs are used, the Userform cannot be
used on Mac
- the units for positions and dimensions for Userforms and its components are Pixels on Mac, but
Points on Windows, resulting in an about 1.3 times smaller Userform on Mac.
Keep this in mind when designing a Userform.
- When closing a UserForm always Unload it ("Unload Me") and not only hide it.
- Only use GUI specific code in the Userform code-module.
- Resizing on Mac is only possible by clicking the appropriate controls (so far)
On Windows: SDK functions are used.
- Userform_Activate is only called once, not every time the dialogbox is shown
-> call it explicitly to initialized the form controls
- the Show-command of Userform has no argument on Mac
-> conditional code (together with Userform_Activate)
Others:
- Active X is not implemented on Mac
-> EventClass Module not usable (no double-Click on shape possible)
- FileSystemObject does not exist
-> use only standard IO function (see Tools)
- Functions Round, Replace, and InStrRev are not implemented for some strange reason
-> Round and InStrRev are avoided, Replace implemented for Mac
(Round could be replaced by CInt)
- Shell-command does not work correctly, like expected from the Finder (the "MacOS Explorer")
-> AppleScript (MacSript VB command) or Windows SDK functions are used
- AddPicture function needs width and height on Mac (not optional and NOT -1)
-> use boundingbox width and height from the postscript file (would be difficult with an external tex2bmp)
|
|
 |