Finally decide to install 1.5 today on my Windows 11 HP laptop, and:
Ridiculously long install time, like 3 - 5 min
Once installed, the probe section encroached on the jogging section, where I couldnāt see or select āpreciseāā¦ I āfixedā this by clicking the restore down icon (maximize when single box). It still was 98% maximized, but the scale was corrected and I could access the full probe section
MAJOR issue, and probably a repeat of others: when I tapped the jog buttons, it randomly kept on going. First instance was Z, going down of course, with my brand new whiteside 60 deg V-bit. I know, it was stupid of me to use that bit when I was setting up a new version, but Iāve been very fortunate to finally have GSndr pretty solid for a whileā¦ After calming down, I resumed, only to have the Y axis do the same thing. Only way to stop either one was hitting the stop button on GSndr or the EPO.
Out of frustration, I reverted back to 1.2.2, and it has a new problem: When I tried to probe for Z, everything went as expected until I actually hit the probe button, Gsndr said it initiated the action, but nothing happens. I remember reading some āreverting backā tips, Iāll do some research and hopefully figure that out.
I guess Iām irritated at myself, because I hesitated updating because, as I said, I was pretty solid with previous install of 1.2.2. ā¦ oh, well, should have listened to myself, but didnāt want to be the only one that does!
Well, you are def not the only one that bunkered down at version 1.2.
I run jt on my pc at the mill and if I upgrade it will be because I need to cause the pc crashed and needs a new windows install, or surface mapping is a feature in newer software. If my 1.2 is still working at the machine, I will swap the pc out for a spare (older model) pc and test drive the new gsender on that.
If it works, donāt update is a mantra I ambraced and do not let go of lightly.
That however does not help you much, but maybe in future endavours into updating a working gesender. It seems there are maps to look into and files to delete, but since I donāt updat, I have never go that route.
Hereās to find older versions, but it does not go deeper into the secret deinstallation process.
As far as files from a new version having problems when reverting to an older version here is what Iām aware of.
In your home folder there should be a .sender_rc file. Its probably hidden if you donāt have show hidden files checked in file explorers options. There is also a folder named gSender in AppData somewhere. I donāt have a Windows machine anymore so Iām not positive but I think itās in C:\Users\your_name\AppData\local but it could be in one of the other sub-directories of AppData or just in C:\AppData.
Iām not sure if you can export settings from a new version and then import them into an old version. In any case itāll only be gSenderās settings, not firmware settings that you have to redo.
We all should, but I never remember to, export settings, macros etc before updating just in case we decide to go back.
All good points, gentlemen, I appreciate you taking the time. I did revert to 1.2.2, replaced the .sender_rc file with an known good one from another PC and all was well today.
āMy home is this bunker, it fits al my needs. I will not need updayes with nothing to gain. Iāll always stay loyal, to this age and day. Because a onetwoĆ«r, will not know delay.ā
@DaWoodster sorry to hear your experience and about your bit. FYI to future you or anyone else reading this thread:
That install time is typical for gSender (issue of the app packager we use where we canāt really optimize it anymore)
Weāre still aiming to make tweaks to ensure that it fits the best across all screen sizes, but in some cases people will still experience this. The current best fix is to adjust your Windows or other OS zoom amount and that will get gSender fitting right on the screen (as you mentioned Ken). Hereās a link for more info Setup and Customizations - gControl
For the issue with tapping the jog buttons and getting a longer movement, we realized that in an effort to make gSender feel more snappy by reducing the delay between incremental and continuous jogging, we now have some people experiencing continuous jogs when they accidentally click to jog for too long. To fix this, weāll have a new setting called āContinuous jog delayā where you can customize the amount of time between short clicks and long clicks to your own preference and avoid having the machine move when you donāt expect it to. This setting will be in the new version 1.5.2 releasing tomorrow
