Search  
 

Please login to post into the forums. Remember - keep your posts friendly. 

Note: Identic Pty Ltd reserves the right to remove any material it considers inappropriate or offensive. Please report any undesirable posts or behaviour to support@lucidcentral.org.

If you have any direct support requests such as reactivation requests please use the help desk.

  
 

Login

    
 
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...Sharing a tip for fixing keys that no longer runSharing a tip for fixing keys that no longer run
Previous
 
Next
New Post
2/22/2017 9:06 AM
 
I've come across two cases where we have struggled to get online Lucid 3 keys to run using the recent builders.

The fix for both was simple once known - to ensure that there were no spaces in the top-level files names.

So for example, chose "Save as" and replace "Plant key.lk4" with "Plant_key.lk4" (underscore or with a hyphen or no space) and ensure that this follows through to the top level files in the deployed version (Plant_key.html and Plant_key.jnlp - so there are no spaces in the file names, which is good practice anyway, but now essential to have them running).

Hope that this tip is helpful to others!
 
Previous
 
Next
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...Sharing a tip for fixing keys that no longer runSharing a tip for fixing keys that no longer run


  
Copyright 2017. All rights reserved. Identic Pty
Terms Of Use  Privacy Statement