Skip to main content
LinSims
Community Expert
Community Expert
January 9, 2019
Question

Cannot open Character Palette or Hex Input

  • January 9, 2019
  • 4 replies
  • 2399 views

The last few weeks I've noticed that I cannot use the character palette. When I click Insert > Character > Character Palette, all that happens is that the Insert entry on the menu bar is deselected. The same thing happens with Hex Input. I checked all the other items on the Insert menu, and they all work. I've tried a number of suggestions provided on the FrameUsers list, including trying to change screen resolution (tricky, I'm already at the highest), moving to using the laptop screen only, variations on the Windows+Shift+arrow keys ... nothing works. I thought briefly it might be a corrupted program because Frame was giving me some odd errors when I closed it, but I've reinstalled with all updates, no longer get the errors on close out, and I'm STILL not seeing either the palette or the hex input.

It isn't a TERRIBLE issue, since I've already created variables for most of the non-standard characters (mostly fractions) that I use and know keyboard shortcuts for most of the rest, but even so, it WAS working, now it isn't, and I don't know why.

Suggestions?

This topic has been closed for replies.

4 replies

LinSims
Community Expert
LinSimsCommunity ExpertAuthor
Community Expert
February 18, 2019

Recently updated to Windows 10 Pro, fully patched.

FrameMaker 2019, Update 2.

The Hex Input and Character Palette are now available, but are closing themselves within about 10-20 seconds after being opened. With the Hex Input (which I never use but was checking for the sake of completeness), this means if I have the Unicode in my clipboard and paste it in, I can get the character I want.

If I want to use the Character Palette, however, and need any font other than Courier, I'm out of luck. The palette will close while I'm still scrolling through the available installed fonts. If I just stick to Courier, it usually still closes before I can find the character I want.

Admittedly, I can generally find what I want using the Windows Character Map, but I find it curious that a program that made its reputation by being a better DTP than anything else out there still uses the antiquated and hard to read Character Palette and now the palette is (for me) pretty much impossible to use.

michaelcarlisle
Inspiring
August 19, 2019

I also am experiencing the problem of the Character Palette closing after 10 seconds that linsims reported.

I am using FrameMaker 13 (FrameMaker 2015) on the Windows 10 Enterprise operating system, 64-bit. Today is Monday. I was able to use the Character Palette the previous Friday.

Any assistance and information on how this problem can be fixed will be greatly appreciated.

michaelcarlisle
Inspiring
August 19, 2019

Rebooting my computer seems to have fixed the problem The Character Palette no longer prematurely closes.

LinSims
Community Expert
LinSimsCommunity ExpertAuthor
Community Expert
January 21, 2019

I'm back to not being able to use the character palette or the hex input. I can't keep redoing the preferences folder every time this happens.

LinSims
Community Expert
LinSimsCommunity ExpertAuthor
Community Expert
January 10, 2019

Solved! I found Matt Sullivan's Tech Comm Tools post on another thread about FM2019 crashing where he suggested renaming the preferences folder to make Frame create a new one. I tried it and it solved not only my Character Palette/Hex Input issue, but a new one that had reared its ugly head, a Windows application error that was popping up when I closed Frame.

Community Manager
January 10, 2019

Hi linsims,

can you give some tech specs? Sounds you are using FrameMaker 2017 or 2019. If 2019 release: 32 or 64 bit?

Also, which Windows version?

LinSims
Community Expert
LinSimsCommunity ExpertAuthor
Community Expert
January 10, 2019

Windows 7, fully patched (they just pushed some stuff out on Tuesday).

FrameMaker 2019, update 2, 64-bit.

What puzzles me is that it WAS working, and now it isn't. Because I don't use it that often, I've no idea when the changeover occurred.