#hazzy | Logs for 2019-09-28
Back
[01:00:32] -!- c-log has quit [Ping timeout: 276 seconds]
[01:01:59] -!- c-log has joined #hazzy
[03:30:53] -!- c-log has quit [Ping timeout: 265 seconds]
[03:32:37] -!- c-log has joined #hazzy
[08:11:37] -!- tommylight has joined #hazzy
[09:05:11] -!- tommylight has quit [Ping timeout: 260 seconds]
[09:44:17] <roguish[m]> jthornton: just ordered mosfets and gate drivers to try and repair a couple 7I40s.
[12:07:58] <jthornton> cool
[12:13:19] <hazzy-m> morning
[12:16:20] <hazzy-m> Lcvette: The main reason fo having ProbeBasic seperate is so that it can have its own release sechedual.
[12:16:50] <hazzy-m> Before if you fix a spelling error in ProbeBasic we have to make a whole new QtPyVCP release, and everyone has to update all of QtPyVCP just for that one little thing, which puts a lot of load on me and TurBoss and makes it MORE difficult for the end user to stay up to date
[12:17:58] <hazzy-m> it also causes people who don't use ProbeBasic to have to update QtPyVCP just to get fixes for stuff they aren't even using, which again does not make any sense
[12:19:59] <hazzy-m> Also with PorbeBasic tied to the QtPyVCP release schedual you can't test probe basic with new QtOyVCP feature branches, now it is possible to run the most recent probe basic on the VKB branch, which before would not have been possible without a lot of work rebasing etc.
[12:21:10] <Tom_L> sounds like a plan
[12:21:28] <Tom_L> can i update now? :D
[12:21:42] <hazzy-m> ALso if sombody wants to make their own version of ProbeBasic all they have to do is fork and edit the ProbeBasic repo, and its easy to install and test. Before theyu would have to fork all of QtPyVCP and distribute the whole thing
[12:22:04] <hazzy-m> Tom_L: hey Tom!
[12:22:13] <Tom_L> but you've created a disturbance in the force...
[12:22:18] <hazzy-m> yes, you should be able too
[12:22:21] <Tom_L> hi
[12:22:57] <hazzy-m> yes, but change is not always bad :)
[12:24:05] * hazzy-m lost his coffee cup
[12:27:35] <Tom_L> now that _is_ bad
[12:28:22] * hazzy-m found it outside in a flower bed
[12:35:26] <Tom_L> tryin to stunt their growth?
[13:21:46] <Lcvette> The forking will be difficult for most but I understand your point.
[13:21:52] <Lcvette> Is it fixed?
[13:22:17] <Lcvette> Bebas kai
[13:22:39] <hazzy-m> you need to install QtPyVCP again
[13:22:40] <Lcvette> Find anything wonky or could it have been from when I uninstalled it?
[13:22:55] <hazzy-m> from the dir using `pip install -e .`
[13:23:03] <Lcvette> It's a new version?
[13:23:11] <hazzy-m> and all will be well
[13:23:36] <Lcvette> Did you change anything
[13:24:50] <Lcvette> I'm in chapel hill, had to take my dad in for his igg treatment, heading back to Wilmington now
[13:25:01] <Lcvette> Should be home in hour and a half
[13:25:34] <Lcvette> What directory?
[13:25:41] <Lcvette> Not main terminal?
[13:26:09] <Lcvette> Install it in the pro e basic directory?
[13:26:19] <Lcvette> Do I need to uni stall probe basic first?
[13:27:08] <Tom_L> uninstall and re'install or update?
[13:28:20] <Lcvette> Hazzy
[13:28:21] <Lcvette> ?
[13:30:20] <hazzy-m> uninstall QtPyVCP with `pip uninstall qtpyvcp` and then from your `dev/qtpyvcp` directory run `pip install -e .`
[13:30:35] <hazzy-m> I'm working on embeding the font in ProbeBasic now
[13:30:42] <Lcvette> I don't have a Dev qtpy directory
[13:31:24] <Lcvette> I was just doing the little install
[13:31:54] <hazzy-m> same dir where you used to edit the Probebasic files
[13:33:02] <Tom_L> should i move mine to /dev/qtpyvcp or leave it where it is?
[13:33:53] <hazzy-m> Tom_L: you can leave it where it is
[13:34:11] <hazzy-m> the location does not matter, as long as you know where it is!
[13:34:23] <Tom_L> that's the hard one
[13:35:57] -!- Tom_dev has joined #hazzy
[13:36:06] <Tom_dev> log
[13:36:06] <c-log> Tom_dev: Today's Log http://tom-itx.no-ip.biz:81
[13:36:54] <Lcvette> Hazzy I installed on my machine,
[13:36:57] <Lcvette> No edit on that ine
[13:37:05] <Lcvette> That's the one that was busted last night
[13:37:16] <Lcvette> I didn't touch the dev machine, left it alone
[13:37:49] <hazzy-m> ok, then install with `pip install git+https://github.com/kcjengr/qtpyvcp`
[13:38:10] <Tom_L> ok so after the uninstall, there are still files in the /qtpyvcp directory
[13:38:24] <Lcvette> What directory
[13:39:08] <Tom_L> /home/tom/qtpyvcp
[13:39:19] <hazzy-m> when you install with `pip qtpyvcp` it won't install any files outside of the install location (usually .local/lib/python2.7), so that is why you are missing the font file and possibly the hallib which I bet is causes your problems
[13:39:41] <Lcvette> Ah
[13:39:50] <hazzy-m> Lcvette: it does not matter what directory when using `pip install git+https://github.com/kcjengr/qtpyvcp`
[13:39:55] <Lcvette> Sounds reasonable
[13:40:05] <Lcvette> Ok
[13:40:39] <Lcvette> Should I do a fresh install or uninstall everything and do I install qtpyvcp first then probe basic?
[13:40:44] <hazzy-m> Tom_L: yes, when you install with `pip -e .` it just creates a ling to the folder, so when you uninstall it just deletes the link, not the files
[13:41:24] <Tom_L> oh
[13:42:04] <hazzy-m> you can run pip uninstall for both qtpyvcp and probe_basic if you want to make sure everything is clean, and then install qtpyvco first and then probe_basic
[13:42:27] <Lcvette> Ok
[13:44:42] <Tom_dev> so where does: pip install git+https://github.com/kcjengr/qtpyvcp put the files/
[13:44:46] <Tom_dev> ?
[13:47:51] <hazzy-m> Tom_dev: it downloads the zip file from github to a temp dir, unzips it and runs the equivalent of `pip install .` which installs the compiled python files to .local/lib/python2.7/qtpyvcp
[13:50:52] <Tom_L> so should i be in the probe_basic directory when i install it?
[13:51:27] <hazzy-m> if you install with `pip install -e .` yes
[13:52:16] <hazzy-m> the . just means install from here, so you could also pass the path instead of using the .
[13:52:33] <TurBoss> hello
[13:53:19] <TurBoss> rpi4 just arrived
[13:53:27] <TurBoss> \o/
[13:53:38] <hazzy-m> yo
[13:53:40] <hazzy-m> Hurray!
[13:53:41] <hazzy-m> 4gb?
[13:53:52] <TurBoss> yup
[13:56:54] <TurBoss> oh I can' power it
[13:56:55] <TurBoss> lol
[13:57:14] <hazzy-m> oh no!
[13:57:15] <hazzy-m> usb c
[13:57:39] <TurBoss> yes
[13:57:44] <TurBoss> i don't have it
[13:57:45] <TurBoss> xD
[13:57:57] <TurBoss> and is just 8:00 pm all closed
[13:58:01] <TurBoss> nooooooooooo
[13:58:10] * hazzy-m didn't either lol
[13:58:18] <Tom_L> no corner convenience stores?
[13:58:22] <Tom_L> they have em
[13:58:23] <hazzy-m> :(
[13:58:35] * hazzy-m passes TurBoss a USB C power supply
[13:58:45] * TurBoss is downloading
[13:58:54] <TurBoss> lol
[13:59:16] <hazzy-m> big file ...
[13:59:20] <Tom_L> ok something must be installed right. probe_basic comes up in the editor
[13:59:22] <hazzy-m> lol
[13:59:38] <hazzy-m> sweet!
[14:00:34] <TurBoss> I was taking a look at the offsets table
[14:00:42] <TurBoss> but python only gives the currently active one :|
[14:01:18] <Tom_L> ok so where are the sims at now since i moved the qtpyvcp install?
[14:03:33] <Tom_L> found em i think
[14:04:30] <Tom_L> probe_basic doesn't show up in the vcp chooser though
[14:21:50] <hazzy-m> Tom_L: it should show up in the lower installed VCPs section
[14:25:01] -!- Tom_dev has quit [Quit: Leaving]
[14:25:12] <Tom_L> i think i'm figuring it out
[14:25:25] <Tom_L> just more than one way to install