cb4960 Wrote:If this issue occurs again, can you please open the Browser Console (Ctrl-Alt-J), and check if there are any errors that look like they might be related to Rikaisama? Thanks.

I've tried with the Browser Console and Rikaisama stop working when this error appears:

"TypeError: can't access dead object rikaichan.js:735:0"

I wonder why it gives this error only when I use a EPWING dictionary :/

cophnia61 Wrote:

cb4960 Wrote:

cophnia61 Wrote:When I use an EPWING dictionary, after a while Rikaisama stops working.
The word continues to get highlighted but the blue window doesn't appear anymore, and I must restart the browser.
Sometimes it happens after a while, sometimes it happens after just a couple of checks with rikaisama.
Anyone had the same issue and know how to fix it?
Thank you in advance!

What version of Firefox are you using? What version of Rikaisama are you using? What operating system are you using? What dictionary are you using? Can you provide steps to reproduce the issue?

Thank you cb4960 for your interest!

Firefox 38.0.1 (I've seen just now that there is an upgrade available, I will try it and see if it fixes the issue EDIT: it's the last version)

Rikaisama 22.3

Windows Vista 64 bit

研究者新和英大辞典 第5版 (I will try with another compatible dictionary if I find one, and see if it gives the same issue)

There are no particular steps: I activate Rikaisama with the red-smile icon, then I put the mouse cursor over a word and it gives me a definition; then ad any random moment it stops working, it continues to underline the words where I put the mouse cursor, but it doesn't show the blue popup with the definition. Even if I deactivate and reactivate Rikaisama with the red-smile icon, it still doesn't work. The only solution is to close Firefox and reopen it :/

I've found another way to reproduce symptom but with different precondition (not related to Epwing)

1. hover to any Japanese word and wait until definition popup appear

2. Press U (Super sticky mode) so the definition pop up is 'Frozen'

3.(Here's the fun part) instead of pressing 'U' again to turn off Super sticky mode, hover the mouse over to any blank area of the page and click on the blank area. This will make the definition popup disappear.

4. The word continues to get highlighted but the blue window popup doesn't appear anymore.

5. The fix version 1: restart Firefox
The fix version 2: without restarting Firefox, simply disable Rikai-sama, then enable Rikai-sama again , but without moving the mouse. Ensure the "Rikai-sama Enabled" blue pop-up is still there, then press 'U' to turn off super sticky mode

myxoma Wrote:

cophnia61 Wrote:

cb4960 Wrote:What version of Firefox are you using? What version of Rikaisama are you using? What operating system are you using? What dictionary are you using? Can you provide steps to reproduce the issue?

Thank you cb4960 for your interest!

Firefox 38.0.1 (I've seen just now that there is an upgrade available, I will try it and see if it fixes the issue EDIT: it's the last version)

Rikaisama 22.3

Windows Vista 64 bit

研究者新和英大辞典 第5版 (I will try with another compatible dictionary if I find one, and see if it gives the same issue)

There are no particular steps: I activate Rikaisama with the red-smile icon, then I put the mouse cursor over a word and it gives me a definition; then ad any random moment it stops working, it continues to underline the words where I put the mouse cursor, but it doesn't show the blue popup with the definition. Even if I deactivate and reactivate Rikaisama with the red-smile icon, it still doesn't work. The only solution is to close Firefox and reopen it :/

I've found another way to reproduce symptom but with different precondition (not related to Epwing)

1. hover to any Japanese word and wait until definition popup appear

2. Press U (Super sticky mode) so the definition pop up is 'Frozen'

3.(Here's the fun part) instead of pressing 'U' again to turn off Super sticky mode, hover the mouse over to any blank area of the page and click on the blank area. This will make the definition popup disappear.

4. The word continues to get highlighted but the blue window popup doesn't appear anymore.

5. The fix version 1: restart Firefox
The fix version 2: without restarting Firefox, simply disable Rikai-sama, then enable Rikai-sama again , but without moving the mouse. Ensure the "Rikai-sama Enabled" blue pop-up is still there, then press 'O' to enable senseido mode, and press 'U' to turn off super sticky mode. Finally press 'O' again to turn off senseido mode.

Keep in mind that for Super Sticky mode you have to either Ctrl-Click or Alt-Click a word to show the popup. So step 4 demonstrates the expected behavior.

cophnia61, I made a test version that may fix the issue:

Download test 1

Let me know if you still see the issue. If so, please check the Browser Console (Ctrl-Shift-J) like you did before.

myxoma thank you for the time and effort!

cb4960 I've tried it for 15 minutes now and it seems to work! Not only, it seems even faster: now the popup appears immediately while before there was a delay, maybe it is correlated?

Thank you very much to both myxoma and cb4960!

EDIT: It stopped working now! After 20 minutes of usage... I will try again with the browser debugger!

EDIT2: The error is the same:

"TypeError: can't access dead object rikaichan.js:649:0"

Please try this new test version (Rikaisama_v22.4_Test2.xpi) when you get a chance:

Download Test 2

cb4960 Wrote:Please try this new test version (Rikaisama_v22.4_Test2.xpi) when you get a chance:

Download Test 2

I've tried it and it stopped working after some time, but I've tried two times and both times it lasts longer than the official version and it's more responsive (maybe this is correlated with the problem?). But this time the error is different:

"TypeError: topdoc.getElementsByTagName(...)[0] is undefined rikaichan.js:596:3"

I have like the impression it happens most of the time (but not allways) when I do things like when I open a new tab or I switch to another tab, or when I put firefox on background... but I'm not sure about this :/

Here's another one to try:

Download Test 3

cb4960 Wrote:Here's another one to try:

Download Test 3

It works! This time I'm sure! I've tried it for 30 mins, it still gives some errors but it continues to work:

Quote:elem or parentNode is not defined! rikaichan.js:761:0
showPopup() Exception: TypeError: can't access dead object rikaichan.js:771:0
TypeError: can't access dead object rikaichan.js:3617:0

then after 10 mins it gives:

Quote:showPopup() Exception: TypeError: can't access dead object rikaichan.js:771:0

and then another time the same error, after around 10 mins:

Quote:showPopup() Exception: TypeError: can't access dead object rikaichan.js:771:0

I have just uploaded version 22.5 of the Rikaisama Firefox extension.

Download version 22.5 via SourceForge

What's New?

● "Fixed" issue that some users were having that caused the popup to stop appearing after several minutes of EPWING mode use.

cb4960

I have some problem. i use it for a while(a month maybe) and it worked fine, but today when i press R button to import it, nothing happen. the Note Add pop up doesnt appears and the vocab also doesnt add to anki. i try restart my laptop and reinstalled anki add-on but nothing happen. Does anyone know what cause this to happen?

EDIT: found solution. it's because of the damn firefox update V_V just downgrade back to v30.0 and everything is fine

Firefox 41 is now on DevEdition/Beta, so Rikaisama (and Rikaichan's dictionaries) stopped working: http://sourceforge.net/p/rikaisama/bugs/3/

I have just uploaded version 22.6 of the Rikaisama Firefox extension.

Download version 22.6 via SourceForge

What's New?

● Rikaisama is now "signed", meaning that it will now work with Firefox 41+. I've tested on Windows and Linux Mint using Firefox Nightly 42.0a1. In Nightly, there are quite a few "Unsafe CPOW usage" warning in the Browser Console which I have yet to look into.

cb4960

Hi, I have problem getting Rikaisama to import audio to my anki deck. It just shows as ちたい - 痴態.mp3 in the field, and it wouldn't actually play unless I drag the audio from the saved folder. Is this a problem with my saved path?

errido Wrote:Hi, I have problem getting Rikaisama to import audio to my anki deck. It just shows as ちたい - 痴態.mp3 in the field, and it wouldn't actually play unless I drag the audio from the saved folder. Is this a problem with my saved path?

In "Options > Clipboard & Save > Save audio", put the path of your Anki collection's media folder. Also be sure to check "Options > Anki > Save audio when one of the Anki Real-Time Import keys is pressed".

I saved the audio in the anki collection's media folder and I did check the save audio when import key is pressed, but I still have to manually input the [sound:myaudio.mp3] in order for it to work. Sorry if I'm being such a no0b, but is there something else that I missed?

errido Wrote:I saved the audio in the anki collection's media folder and I did check the save audio when import key is pressed, but I still have to manually input the [sound:myaudio.mp3] in order for it to work. Sorry if I'm being such a no0b, but is there something else that I missed?

In the "Options > Clipboard & Save > Save format" textbox, simply replace "$a" with "[sound:$a]".

For example, a complete save format with expression, reading, meaning, and audio might look something like this: "$d$t$r$t$n$t[sound:$a]".

I'm having firefox 41.0a2 permanently freeze after trying to mouse over something with rikaisama enabled. Is this because I have e10s enabled? That's the only thing I changed. I enabled it because firefox has been regularly hitching up for a full second at a time every few seconds with e10s disabled.

wareya Wrote:I'm having firefox 41.0a2 permanently freeze after trying to mouse over something with rikaisama enabled. Is this because I have e10s enabled? That's the only thing I changed. I enabled it because firefox has been regularly hitching up for a full second at a time every few seconds with e10s disabled.

So far I have only tried it on 42.0a1, but for me it seems to work with or without e10s enabled.

The issue resolved itself, just like it came.

I have just uploaded version 22.7 of the Rikaisama Firefox extension.

Download version 22.7 via SourceForge

What's New?

● The Real-Time Import feature is now compatible with Firefox 40+.

Note: A signed version should be released within a week.

cb4960

The signed version of Rikaisama 22.7 is now available.

Hi cb4960,

Is the source code available? The homepage says it's on sourceforge but I cannot find it there. Hope I'm not missing some kind of obvious link on the sourceforge page.

Also, I was wondering if my request from over a year ago was ever implemented: http://forum.koohii.com/showthread.php?p...#pid208716

If so it does not seem to be working.

Thanks again for all your generous efforts to helping us out!

EDIT: Thought I would just edit in my reply since an extra post seems unnecessary.

V Thanks so much! Silly me or not knowing about the .xpi thing.

Flamerokz Wrote:Hi cb4960,

Is the source code available? The homepage says it's on sourceforge but I cannot find it there. Hope I'm not missing some kind of obvious link on the sourceforge page.

Also, I was wondering if my request from over a year ago was ever implemented: http://forum.koohii.com/showthread.php?p...#pid208716

If so it does not seem to be working.

Thanks again for all your generous efforts to helping us out!

The .xpi file is actually just a zip file. So to see the source code, simply unzip it. After unzipping you will also need to unzip chrome/rikiachan.jar.

I never did add that feature, but I'll try to add it in the next version (for real this time).

Some rocky times ahead for Rikaisama (and other Firefox add-ons):

The Future of Developing Firefox Add-ons (blog.mozilla.org)

In particular, the "Deprecation of XUL, XPCOM, and the permissive add-on model" is troublesome.

This DownThemAll blog post describes some of the issues:

http://www.downthemall.net/the-likely-en...wnthemall/

In short, Rikaisama/Rikaichan may be dead in 12-18 months time.

I guess Classic Theme Restorer will become incompatible too. Pfft.

So I'll either use an old version of Firefox, or switch my browser out of spite.