Post by scooterman1 on Dec 14, 2009 12:07:21 GMT -5
I installed the CR8tracer and created the .GFS file. I then installed the Type 2.2 Demo. I open Type 2.2 Demo, Click New, type in the Family Name, and Full Name, and click on O.K. I then go to open the GFS, but it places the circling 'O' (like the Hour Glass in earlier versions of Windows), and never progresses to where you can add the GFS file. It's like the program locks up. Any ideas??? I tried reinstalling and that didn't fix the problem.
Post by Allan Murray on Dec 15, 2009 1:01:04 GMT -5
Because I have not tested the program(s) on Windows 7, I am not yet claiming compatibility (as with Vista also - but I know of several users who are using it on Vista).
Do you get the same result when adding a .GFS that has been created from Type 2.2 rather than CR8tracer? Because another possibility is that CR8tracer is the program that is not compatible - a corrupt GFS could cause 'hanging'.
I would be interested to hear from anyone else who has had problems (or no problems) using the software on Windows 7. Hope to have a compatible and fully tested version in the future.
Post by scooterman1 on Dec 15, 2009 12:08:58 GMT -5
No, I click on File/New, enter Family Name, enter Full Name, click OK, and this is when the program locks up. I have also tried running the program in Compatibility Mode for both Vist AND Windows XP. Nothing works.
I'm running Windows 7 and having a similar problem.
Whenever I try to create a new font, the program locks up and I get a not responding message. When I try to open .ttf files that I created with another program, about half will open and half will freeze the program.
Post by Scott Janssens on Feb 15, 2010 2:56:09 GMT -5
I get the same problems. I notice the app uses 50% of the CPU and seems to continuously allocate RAM in 2 mb chunks until I kill the process. Attaching the Visual Studio (2010) debugger to the process I get this exception at the point the app stops responding:
Unhandled exception at 0x00448721 in Typelight.exe: 0xC000008E: Floating-point division by zero.
Probably not very useful, but here's the call stack:
Typelight.exe!00448721() [Frames below may be incorrect and/or missing, no symbols loaded for Typelight.exe] Typelight.exe!00451a86() gdi32.dll!7681a974() comctl32.dll!7659953d() comctl32.dll!76599543() comctl32.dll!76595598() comctl32.dll!7659cfff() comctl32.dll!7659d00a() comctl32.dll!76587e53() comctl32.dll!76587e60() user32.dll!754f6238() user32.dll!754f68ea() user32.dll!754f6899() user32.dll!75500ab0() user32.dll!75507b0f() user32.dll!754f8112() comctl32.dll!737fb90d() Typelight.exe!0040100c()
Post by Allan Murray on Apr 5, 2010 0:23:17 GMT -5
The problems reported in this thread are not a Windows 7 compatibility issue.
Since this thread was posted I have tested Type light, Type 2.2 and Type 3.0 on Windows 7 without any problems. Type 3.0 also includes some enhancements for Windows 7.
I am interested to hear any other reports, or receive any assistance in isolating the cause (there have only been a few reported cases). This maybe a specific hardware or software compatibility issue (possibly 64 bit? - I have not tested on 64 bit systems).
Post by bruceuncle on Jun 19, 2011 18:49:29 GMT -5
I'm running Win7 64-bit on an I5-750. Type V3.0.011 is installed and generally runs OK.
I say 'generally' as I've had an occasional 'Unhandled exception' along the same lines as the one Scott posted. And every now and then, the glyphs view in the mapping window goes blank and I get a 'not responding'. If I've been quickly doing a lot of glyph manipulation repetitively, this will resolve itself if I just wait (for some threads to 'catch up' maybe?). But it can also be terminal sometimes. As you suggest in the manual - Save Often!
And one that I cannot understand: If I create a new font and import single-character glyphs into it, it warns me that only the first 50 will be saved when I try to save as TTF. And sure enough, it does only save the first 50 - just like the Typelight and Type trial versions. The single-character glyphs originally were created and saved from both the Typelight and trial Type versions. It left me wondering if you 'clobbered' the glyph files produced by those versions to prevent users creating more than 50 glyphs by saving them singly - like I did.
A workaround seems to be to open an existing Windows font (a copy I hasten to add) trash its contents and import into that. But its a lot more effort as the names and metrics all have to be changed and I would be concerned about copyright violations.
The above comments are far from deal-breakers. The software is just what I needed for my purposes (a keyboard and mouse symbol font for specific documentation). A great product overall.
One request: The CR8tracer manual refers to creating glyph files in ASCII sequence to make the mapping in Type a one-hit process. It refers to a page in the Type 2.2 manual. I've scoured the Type 3.0 manual and can find no similar reference. So what's the process?
Post by Allan Murray on Jun 20, 2011 2:35:01 GMT -5
To map several glyphs at once: 1. Make sure that the first glyph is selected in the edit window 2. Click the character in the mapping window that you want to map the first glyph to (it will turn blue) 3. While holding the shift key, click on the last character that you want to map to (the whole range of characters will be highlighted blue). 4. Press the map button. The glyphs will be mapped sequentially from the first character to the last.
The reference seems to have got lost from the Type 3.0 manual. Will fix that on the next update.
Yes, glyph files created on the demo version (even though they may contain more than 50 glyphs) can only be used to export 50 glyph (max) fonts.
Post by bruceuncle on Jun 20, 2011 19:08:25 GMT -5
Many thanks for the prompt reply. And for the instructions on bulk mapping - works a treat.
Now I've got the full version, I abandoned the glyphs I'd created with the demo and used the action script facility to do things a lot faster. That feature really makes this editor a very powerful tool. As the majority of my font's glyphs are keyboard characters, it's been really simple to import the basic keyboard character glyphs, scale them to fit the key outline, then centre them and past the outline over the top - all in one hit over the entire glyph set. Great! (Even if the language syntax does remind me of the olden days - coding in assembler.