-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shows 'NaN' everytime and throws TypeError: Cannot read property 'getSelectedText' of undefined #81
Comments
Looks like it happens when the active pane is not a text editor. The fix would probably be to return |
I have seen a screenshot and it looks like the active pane was a text editor.
Insteresting, might be a good idea to add that. |
It looks like the issue happens when the dec-hex-oct-bin view is in the center workspace instead of in a dock. When a button is clicked the dec-hex-oct-bin view is activated making the TextEditor no longer the active pane item. To fix this we have to find a way to get the selected text from the "last active" TextEditor instead of the "current active" TextEditor. |
At first i feel better with it, if the user has confirmed this.
I think it might be a more reliable solution, if we preventing the plugin pane from became a part of the center view by using the |
That sounds like an easier solution 👍 |
And we should add a check in |
Oh yes. |
And if none found but clicked it shows a friendly message. |
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 10
andManjaro 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.
The text was updated successfully, but these errors were encountered: