![]() ![]() You may head to the download page and re-install 0.2.2 to apply the fix. Vista users who met problems with previous version should upgrade - users who do not have any problem may wait until the next release. Installer files have been updated to this release tagged 0.2.2a. 1 2009-06 Tagaini Jisho 0.2.2 update for Windows usersĪn update to 0.2.2 has been released, that fixes an important issue that may make Tagaini unusable if installed under Program Files on Windows Vista. This was a mistake not to post more often - although Tagaini now have a community of regular users (according to the hits I get from the new version checker), the mailing-list is pretty inactive and there is still no external contribution.Īnyway, for the people following this website, here is a little update about the upcoming 0. This is the first time a news item is posted that is not a release announcement. If you are interested in trying the future next release and don’t mind encountering a couple of rough edges, please download this release, give it a try, and give some feedback either as a comment here or on the mailing list! 3 Development news, Mac OS Snow Leopard problems, and call for help Some shaping still needs to be done, but the purpose of this release is to get some feedback and confirmations that everything works as expected. The features set includes everything that was planned for 0.2.4. Despite of the “beta” label, it should be safe to use by regular users. 7 0.2.396 beta version releasedĪ beta version of the upcoming 0.2.4 has been released for Linux and Windows (Mac binaries coming soon). The score calculation algorithm has also been reworked - the previous one was totally flawed and only based on the number of attempts/number of success ratio. As a result, this version is available and working on Windows, Mac and Linux again. ![]() So, it’s time for another beta release! Not many changes in this one (although the kanjis popup outline has been reworked because Qt 4.6 made it too buggy), but rather cleaning and improvement of the building and release process in order to make it more comfortable. obsolete words), hiragana/katakana agnostic search, training on a given results set, improvements in the kanji strokes rendering and navigation, support for SKIP code search, an improved score calculation algorithm, a Dutch translation of the GUI, and much more. Amongst them are full wildcard search support, automatic filtering of some entries according to their properties (e.g. This release has been baked for months in order to provide much more polished preferences and tons of new features. I then used Comodo to whitelist these in the firewall so they'd always be approved for accessing the internet.The long-due 0.2.4 release of Tagaini Jisho is finally available. ![]() C:\Windows\ImmersiveControlPanel\:\Program Files\WindowsApps\Microsoft.StorePurchaseApp_12109.1001.10.0_圆4_8wekyb3d8bbwe\StoreExperienceHost.As the version numbers were different, the folder names were also different. #1 Grant the current user the permissions to access the WindowsApps folder It is important that these tasks are completed in the correct order, otherwise you'll have to do it again. When trying to whitelist or allow the above files in my firewall, I was given an error that I wasn't allowed to access the folder as I didn't have the right permissions. So then I tried to grant myself the correct permissions. Just right click the folder WindowsApps then click properties then open the security tab. I then used the settings tab to try to give myself the relevant permissions needed to access this folder. Something strange appeared in the security tab. It should instead show a list with several checkboxes in rows and columns underneath another list from another box. So obviously my current principle (or user-space in linux terminology) is unable to read this folder.Īfter clicking the "advanced" button, I then got this window to appear. It said that I (or my current principle) don't have read permissions for this folder. I then clicked the view button but made sure that the "users" principal was selected beforehand. I then saw an error that the access control entry was corrupt. I deleted it and created a new one with the correct permissions. The correct permissions should look like the image below. ![]()
0 Comments
Leave a Reply. |