Hi there FooSoft and various testers
for your several years of development and debug work on Yomichan.
I only started using chrome this past couple of days after several years of using firefox and various incarnations of rikaichan/kun/sama over those years. For me I think the single best thing that yomichan does that absolutely hands down, trumps rikaisama is the gating of the scan function by requiring the SHIFT key to be held down as you mouse over the text. The frustration that I would experience with accidental deletion of text due to automated selection by rikaisama was so annoying that I had dedicated a programmable mouse button to make it easy for me to quickly disable rikaisama before I would start typing and just as quickly re-enable it for proof reading and/or browsing.
I prefer the yomichan default approach so much more.
It will come as no surprise that I now have a spare mouse button programmed with the SHIFT key.
Having said that I do still occasionally run into a situation where I've used the shift key to type some punctuation character and perhaps before I release shift some unintended selection has been made. I am experimenting with options for "select matched text", "scan delay" and "scan length" to see if I can reduce the occurrence of these (already dramatically less frequent) accidents.
Is the choice of shift as the hotkey carved in stone or might that someday become a user-specified key?
I do miss ready-access to the Sanseido j-j dictionary definitions but have yet to explore installing EPWING j-j dictionaries for Yomichan.
Google Hangouts and Yomichan
I use yomichan with google hangouts.
I mention this here in case another user has found a better solution than I have. I am running
- Windows 10 Home v1607 (64-bit)
- Google Hangouts 2017.110.418.3 (the so-called desktop app)
- Chrome 56.0.2924.87 (64-bit)
Google Hangouts 2017.110.418.2 (the browser extension)
If you are scratching your head over the version difference between the google hangouts desktop app and the hangouts browser extension then, well, so am I.
They look very much like the same beast to me. The browser extension launches a window separate from the chrome browser. The desktop app launches a windows separate from the chrome browser. If that window has already been launched by the alternate method then it simply grabs focus. The advertised virtue of the so-called desktop app is that you don't need to have a chrome browser instance running however, as you will see from the Task Manager reports below, the chrome.exe process becomes the parent process in both cases!
All is perfectly fine when a google hangout is launched from a gmail
tab within the chrome browser ... even after I pop that chat window out into it's own separate window. So no surprises - Yomichan behaviour is as advertised. I guess you might say that the extension's scope extends to that pop-out window.
I am also trying out the so-called desktop version of google hangouts :
and discovered that yomichan is not active or not enabled within that window.
This is a bit of a surprise because task manager shows this desktop hangout process as one of three sub-processes to the parent "Google Chrome
" process. (C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Inspecting the three windows using AutoIt3 Window Spy (aka AutoHotkey) I learn that each of the three windows
- the desktop hangout window and
- the pop-out window from a gmail tab within the chrome browser and
- the chrome browser window itself
are identified as the same ahk_class "Chrome_WidgetWin_1
I can only imagine that this is because the scope of the Yomichan (as a chrome browser extension) is not embracing this alternative window for using hangouts. If anyone reading this is successfully using google hangouts independent of gmail
and knows how to get yomichan functioning within that chat window then please share. (As I will if and when I solve the problem for myself.)
It is early days for me yet and it is not really a big deal because a satisfactory working solution exists (via a gmail tab) and I may yet find myself completely won over to chrome in the near future.