Keyman and Filemaker Pro

Hi all. I’m a software developer using Filemaker database program on Windows 10. I’m working with a Canadian First Nation helping to build a language database. I’ve downloaded Keyman, and it works fine with Microsoft word, but I can’t enable the keyboard shortcuts in Filemaker. Does anyone have experience with this?

Hi @Iainpennington, welcome to the community!

I have just re-tested Keyman with Filemaker Pro and found it mostly works on my system. However, it seems that Filemaker itself has some limitations with some writing systems. For example I have found that with Khmer, Filemaker does not accept input of subconsonants (and this does not relate to Keyman – the same issue arises with Windows system keyboards).

Can you provide some more details on:

  • Which writing system you are working with - Latin script, syllabics, etc?
  • Which Keyman keyboard you are using?
  • Which version of Filemaker Pro you are using?
  • Are there specific key combinations that don’t work, or is it a general issue?

Hi Marc. Thanks for your reply.

Client is using FMP 16, Server 16, Windows 10.

I’ve tried both Aboriginal Sans and Aboriginal Serif

Here’s the Debug log:

kmshjell-cef.log

[1209/102223.740:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/102223.764:ERROR:CEFManager(1)] Sending message ProcessMessage_ResizeByContent, 632, 452
[1209/102443.493:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/102443.533:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/103507.238:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/103526.490:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/103526.523:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1209/103533.313:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085335.050:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085335.077:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085449.791:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[1214/085449.806:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\GPUCache to C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\old_GPUCache_000
[1214/085449.817:ERROR:disk_cache.cc(169)] Unable to create cache
[1214/085449.829:ERROR:shader_disk_cache.cc(600)] Shader Cache Creation failed: -2
[1214/085449.853:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[1214/085449.867:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\Cache to C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\old_Cache_000
[1214/085449.877:ERROR:disk_cache.cc(169)] Unable to create cache
[1214/085450.900:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085501.833:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085501.863:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085533.976:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[1214/085533.995:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\GPUCache to C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\old_GPUCache_000
[1214/085534.008:ERROR:disk_cache.cc(169)] Unable to create cache
[1214/085534.027:ERROR:shader_disk_cache.cc(600)] Shader Cache Creation failed: -2
[1214/085534.230:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[1214/085534.244:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\Cache to C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\old_Cache_000
[1214/085534.259:ERROR:disk_cache.cc(169)] Unable to create cache
[1214/085534.275:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085534.475:ERROR:CEFManager(1)] message received ProcessMessage_ResizeByContent
[1214/085534.501:ERROR:CEFManager(1)] Sending message ProcessMessage_ResizeByContent, 450, 300
[1214/085537.758:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[1214/085537.780:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\GPUCache to C:\Users\iain\AppData\Roaming\Keyman\Keyman Engine\CEF\cache\old_GPUCache_000
[1214/085537.799:ERROR:disk_cache.cc(169)] Unable to create cache
[1214/085537.813:ERROR:shader_disk_cache.cc(600)] Shader Cache Creation failed: -2

Thanks for the additional detail. Can you also provide details on the following – then we can test here? (Aboriginal Sans and Aboriginal Serif are fonts, not keyboards)

Sorry it’s not a direct answer but I’m wondering if you know about FieldWorks and have tried to use it for building a language database or whether you’re trying to do something very different. Just want to avoid unnecessary reinvention of the wheel.

Hi Mark. I’m not sure if i understand questions, but here goes:

Writing system: I’m guessing Latin Script - it’s variants on serif and sans serif font set I think.
Keyboard: when I pull up Keyman System Information, i’m seeing in the registry: kv_nisgaa

I have budget to pay for support. Is there a chance we can connect online?

If it helps, i’ve pulled the Keyman System Information and attached but this forum won’t let me upload.

Thanks

Additional reply: when i type, for example, K witth a colon, it works fine here: ḵ

when I do this in ms word, it also works fine.

When i’m in a filemaker text field, it get an error tone, and nothing else happens. I see the K, but no semi-colon

Hi Rowbory. Thanks for suggestion. My constraint is the need to use the nisgaa font, found here: Nisg̱a'a Keyboard Help

Can that font be used with Fieldworks?

and yet one more thing, here’s the font’s i’m using

https://help.keyman.com/keyboard/fv_nisgaa/9.1.1/fv_nisgaa

Any font can be used with Fieldworks. You can set this up in the Styles menu.

This suggests a limitation in Filemaker. Given the keyboard is working fine elsewhere, it might be best to try working with the Filemaker support team to find out why it isn’t accepting input of ḵ.

got it. that was my next step. A question: are you the coder, or one of the coders? If there’s a way to co-ordinate with Claris (Filemaker’s parent), if they show such an interest?

I’m the team lead for the Keyman project. So yes, I would be the appropriate contact if they wanted to dialog. Send me a direct message on this forum if that comes up and we’ll make it happen.

I suggest you’re right about the filemaker limitation. I’ll be talking to filemaker as well about this.

And maybe there’s a bit of additional coding you folks can do to enable filemaker compatibility? Seems to me this could be advantageous to you - in my experience there’s a lot of First Nation’s use of filemaker in Canada.

Is that an option at your end?

Well, more work for us is not really advantageous, given we are essentially volunteers and Keyman is provided free of charge. :wink:

But in any case, there’s not much we can do from our end at this point except to support the Filemaker developers in their investigations as to the problem, as they need.

lol. I understand. lets see what filemaker does… thanks. will keep you posted.