-
Notifications
You must be signed in to change notification settings - Fork 54
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
SessionInfo #86
Comments
Which Electron version are you using? If Electron 7+, it would be nice to share, how you got it to work. Because seems, that a ton of people (including me), couldn't get it to run with Electron 7. |
At this moment I'm stuck with 6.1.10. Will try another version today. Edit: I'm new to React and Electron but I think I made it work with Electron 8.2.3. Tell me how can I help you Martin. What you need to know. But please, don't forget about my issue if you got any tips. :) |
Actually there is still an open issue regarding Electron 7+ compatibility. For now this issue was not closed and I couldn't get it to run. Prebuilt failed with Electron involved IIRC. But: I would give it a shot, when you can confirm, it's working with Electron 8.2.3. Would be awesome if you can check and if you did something special to get it runnig, describe, what to change. Then the other issue could be resolved for a ton of other users. Thanks so much so far! :) |
Let's start with those steps and see if it helps:
|
Thank you! Will give it a try asap |
Hope it helps. If not let me know so we can look further. |
Fixed my issue btw. :) |
@heimdallexus I still get this error: Rebuild throws now error, but also does not change anything. |
Hey Martin, |
Well. Did not worked for me. Tried to follow some tutorials online, but can't get node-gyp to work. Do I have to install something on Windows to get this to work except for node-gyp itself (which is pre-installed with electron if I'm not wrong). Do I have to be in the module directory (node-irsdk) or in the apps root directory? Thanks for your help! |
Anytime Martin. I'm trying to remember the correct steps. I'll try to find some time later today. Anyway ... let me answer your questions. Q: Do I have to install something on Windows to get this to work except for node-gyp itself (which is pre-installed with electron if I'm not wrong). Q: Do I have to be in the module directory (node-irsdk) or in the apps root directory? |
Thanks. I'll also investigate further today in the evening. Thanks a lot! |
package.json
Couple of options after that to build the node file:
Both worked for me |
I did the following:
Not sure where the problem lies. |
Also tried updating node-abi, but that didn't weird either. |
Can I take a look at your package.json and package-lock.json contents? |
OK this get's too long of an answer due to the code. I zipped it. |
So we can move faster, and leave this board alone, reach me through my email. |
It would be nice if you could answer here again with the (hopefully soon found) solution! |
Sure thing. Will update as soon as we find the reason for it since mine is working ok. :) |
Martin, if you want to we can continue over here. No problem. Run: |
Sent you already an email. For me both is ok. node: v12.16.3 |
Just updated everything prior to continue working on this. |
Short update for @sabifa ... I installed a stripped down version by @heimdallexus, but the problem persists and seems to be related to the system config. Not sure what it needs, to get this up and running, but probably a complete rewrite of a new C++ implementation with no dependencies on old versions of node/electron is faster than hunting down a solution to this repo. Maybe just my frustration is writing those lines, but the fact, that this repo is not working with more recent electron versions renders it useless mostly. |
OK. So finally we traced back the error.
Should work and rebuild just fine now and result in the bare minimum of node-irsdk throwing no error at least for starting electron and listening for iRacing. Have to do further testing though, but it seems at least start now without errors. Additional steps I did:
That's it. Hope it helps @sabifa and very big thanks to @heimdallexus once again. He hinted me to the error with the bindings.gyp so that I could hunt it down within 10 minutes in the end. :) |
@sabifa if you want to take a look at my code I can send you the link, just let me know. My email is up there somewhere. |
Same from my side. Can send you a stripped down version as well. |
Wow! Thanks a lot guys, it worked on the first attempt! 🚀 One thing that bugs me is that we have to edit the files inside node_modules, so next time you reinstall the packages it will discard the changes. The best thing would be that @apihlaja applies these changes to the code or that you could set up a PR so he can merge the changes. Maybe a PR would make sense anyways so other see what to do to make it work with newer Electron versions? Unfortunately, looking at the recent issues it seems like he does not have any time working on the project for quite a while now. Another thought: Can't we just move the node-irsdk folder from node_modules into my src folder so it keeps the modified files? |
Another thought: Can't we just move the node-irsdk folder from node_modules into my src folder so it keeps the modified files? Sure. Or you can do as I've been doing. I keep my node-isrdk directory outside and, when I need to reinstall, I just copy it back to node_modules. Anyway the best option is to merge those changes. I don't know Antti so if anybody is up to see if he can take a look or share this project with someone who can that would be nice. Also update irsdk_defines.h to the latest version. |
could someone post the required diff to get electron 8 working? |
Take a look at this comment 🙂 |
apihlaja#86 Based on findings of @heimdallexus and @martinguder. Make sure to rebuild your project.
A question really. I've been writing some code using node-irsdk and electron for the past two weeks.
One thing I have been struggling is that I always manage to lose the first SessionInfo data after hooking the listerner to my browserwindow. Any tip on that?
The text was updated successfully, but these errors were encountered: