Sometimes it happens, that the plugin is not usable, because it continues to display NaN.
In such a situation it also throws at least at the developer console the following message:
Uncaught TypeError: Cannot read property 'getSelectedText' of undefined
at DecHexOctBinView.getSelectedText (dec-hex-oct-bin-view.js:73)
at DecHexOctBinView.parseAsHex (dec-hex-oct-bin-view.js:85)
getSelectedText @ dec-hex-oct-bin-view.js:73
parseAsHex @ dec-hex-oct-bin-view.js:85
Confirmed affected operating systems are both Windows 10 and Manjaro Linux.
Some users are lucky and after closing and reopening the plugin panel, it works again.
But some users not.
Here are the environment versions of one of the unlucky users on Windows 10:
Atom : 1.55.0
Electron: 6.1.12
Chrome : 76.0.3809.146
Node : 12.4.0
The origin of this issue seems to be:
|
return atom.workspace.getActiveTextEditor().getSelectedText(); |
So this might be an issue with
Atom itself?
Unfortunately this issue seems to be hardly reproducible.
Sometimes it happens, that the plugin is not usable, because it continues to display
NaN.In such a situation it also throws at least at the developer console the following message:
Confirmed affected operating systems are both
Windows 10andManjaro Linux.Some users are lucky and after closing and reopening the plugin panel, it works again.
But some users not.
Here are the environment versions of one of the unlucky users on
Windows 10:The origin of this issue seems to be:
dec-hex-oct-bin/lib/dec-hex-oct-bin-view.js
Line 73 in c86f6e2
So this might be an issue with Atom itself?
Unfortunately this issue seems to be hardly reproducible.