Hey guys, Warning! Do not attempt any of the steps mentioned if you are not compitent enough to recreate the error message and to restore the original functionality. For the last couple of days, I’ve been trying to do some tweaking to the Apex. Although not recommended, it has been working out fine in the previous models of BrailleNote. However, with the Apex, there’s a functionality that when attempted creates an error and then it requires you to dots 4,5,6 recet to reinstall the corrupted items. The tweaking involves assigning dots to characters in the unicode tables. With BrailleNote Classic and mPower, it was absolutely doable. Furthermore, Humanware wanted me to record a podcast on how to do it step by step. The tweak involves adding additional unicode tables to have BrailleNote display braille language of your choice. On the Apex, assigning keys works fine, but assigning dot combinations creates an error message. The error is also created when you assigning a new dot combination to an existing unicode table. Usually, this happens on the second character. So now, my question is to whom do I address this issue. It’s not a how to question but more of a recommendation on fixing the bug. When I called Humanware, they’ve been quite helpful to suggest the 4,5,6 recet. I have an mPower in front of me and all the tweaking and assigning the dots works flawlessly. The error message is: “exception: command: 404 at 3595. access violation reading 0”
Thank you. Dmitriy Lazarev ___ Replies to this message will go directly to the sender. If your reply would be useful to the list, please send a copy to the list as well. To leave the BrailleNote list, send a blank message to [email protected] To view the list archives or change your preferences, visit http://list.humanware.com/mailman/listinfo/braillenote
