« first day (1685 days earlier)      last day (1495 days later) » 

11:00 PM
was SC, but the export feature was invoked by SC
so, there's a chance it's still there
 
I'm currently testing this
2
 
#RecursiveTesting
 
Would be more appropriate on StackOverflow.
 
@Duga @this #2343 seems related
 
already on it
 
@Duga right?
 
Don't know. I tried to add the button then I.... lost it.
 
11:05 PM
?
 
in the 2nd gif, you can see Thunderframe customizing the toolbars by adding the Dockable button.
I dragged it to my toolbar and.... poof
can't get it back
 
it's gone.
 
so, not fixed then
 
that's not RD
that's VBE's button
so I can't test it properly
 
11:08 PM
ttqw
 
> > Exactly what would get removed? To do what?

All the VBA constructs that are obsolete, confusing or not useful. Maybe #3486 or #3308 could be such examples? I see a benefit of not having to write inspections for all such constructs because they will just not compile. RD would document what constructs were removed and why. And if the programmer *really* needs to use a removed construct, they can switch back to VBA.

> I originally read the suggestion as to write a transpiler

Yes, I was
 
hmm RD's import doesn't overwrite.
i think it'd be nice if it supported overwriting, instead of adding a xxx1
 
@this oh its a network copy of a database. i built a system to version access apps and download a copy to their computer
it totally solves the issue.... except when the users dont use the powershell script shortcut i put on their computers
 
Alright, time to merge next.
 
ah oof.
 
11:15 PM
yeah
 
we had a similar situation - the fix was to add a startup code to check the path. If it's a network path, quit immediately
 
i built this app like almost 3 years ago
that i can use to track all of our access applications
and what database tables they use
it ended up morphing into our application tracking
so we do changelogs for apps in it
and with that came the whole powershell script that looks up to see what the last revision you ran was and compares it to the most recent changelog entry
 
> Ok, I think I see what you mean -- it sounds more like you want something equivalent to JavaScript's `'use strict';`? Force all obsolete constructs to be compile-time errors?

Consider that one goal of Rubberduck is to enable developers to take a legacy hand-me-down codebase with all wrong stuff and crappy constructs and be able to maintain it... especially without breaking it. Enabling a strict mode would not help in the initial stage but as the cleanup progressing, I can see enabling stric
 
then when its done, if it was running a different version then the most recent change, it downloads a new copy of the app to the computer, and then logs it in the table storing what versions of applications the computers have
it also logs when that update happened plus every time the script runs, it updates the last ran field, so i know if people are actually using the shortcut
its a neat solution for our setup
the best part is, i dont have to interupt users of the application when i need to update the application since it checks every time it runs
now that does put a damper on things when they leave it up for several months, and we have updated it a bunch
 
OK, sanity check. Do I need to squash commits after rebasing my inspection branch, or will the PR merge do that?
 
11:22 PM
when I made a similar mistake, merging did the trick
 
i can guarantee you that it will do things that i am not familiar with.
 
hooray, we no longer have 7th page of bugs. :-p #ArbitaryMeasurement
2
 
OK, that was the missing piece. The merge pulled in InvalidateStaleInspectionResults, and it needs a cast now.
 
@Comintern we can squash-and-merge, but we'd rather not do that
wow tonight's day-end summary will be interesting
 
11:25 PM
Nah, I think we're good.
 
huh. that's new.
 
@this wth?
 
> I think that's an interesting idea... but well out of scope =)
 
IKR? I'm trying to find out who is giving me that. I was closing Excel and Access, Access crashed while closing and is already dead.
 
@Duga not closing to keep discussion going, but IMO that's well beyond RD's scope
like, waay beyond
 
11:31 PM
hmm, belongs to desktop
welp, i have no idea.
 
Crap.
> Updates were rejected because the tip of your current branch is behind its remote counterpart.
I don't think I want to pull in this situation though. Do I need to git push --force?
 
I think that's what I did
you're talking about your fork as the origin, right?
 
No, wait. I think I do want to pull.
 
pull from rd's next, yes. From your fork, never.
 
Yes. From the standpoint of local/inspections
I'm already based even with RD's next.
 
I think I just need the history from the commits that were pushed before the rebase.
 
@Comintern neither
@Comintern depends... want to completely ignore what's on remote and kill it with fire? that's what force-push is for
if that message appears, the branches are "divergent"
if you want changes from both branches, you'll need to merge or rebase
 
I'm trying to remember how many commits there were and whether I care about preserving them.
 
git pull --rebase is a thing
git log --oneline --decorate --graph --all
 
OK, this seems to be where it's messed up.
| * | | | | | | dc9039cb0 Increase performance of GetAnnotatedLine
| * | | | | | | 84cf953b3 Scope annotations to next non-whitespace line
| | | | | | | | * c9cd8a77e (origin/inspections) Stop churning results on filter and group, freshen up toolbar.
| | | | | | | |/
| | | | | | |/|
| | | | | | * | d84f3e76a Use static images and converters.
| | | | | | |/
| | | | | | * 5cf64236a Apply CE refactoring to CodeMetrics window.
| | | | | | * 4ad676e0f Fix test setup.
| | | | | | * 0a22f2508 Code Explorer performance rewrite.
 
looks like a candidate for pull --rebase if HEAD points to the far right line
 
Yeah, I think pull should be fine.
 
just pulling will make git go a bit cross-eyed, tho
because possible merge conflicts
 
11:54 PM
> comintern added some commits 21 hours ago
Well if I'd known that...
 
something isn't right. it's still showing 100 files?
shouldn't it drop to much smaller number?
 
IIR it should auto-squash the already merged commits.
 
that's what I expected.
 
I don't think it does that until it's actually merged though.
 
but if you look in commits, it still has your CE commits
IME, it's immediate but... ?
 
11:56 PM
Right, but it won't merge them again.
If you want, I can close and re-open the PR.
 
let it build first. I might be wrong about autosquashing happening immediately.
Unrelated: to get to 10% open issues bugs we only have to close ~29 more issues bugs. :)
 

« first day (1685 days earlier)      last day (1495 days later) »