> Version 2.4.1.5105 OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office 2016 x86 Host Version: 16.0.9126.2282 Host Executable: EXCEL.EXE
The horizontal scrollbar that has been recently added has a few issues.
Initially clicking on an item nudges the horizontal scroll a little so that the icons and start of the text are then hidden from view.
After using the scrollbar and collapsing a grouping, expanding it again makes the scrollbar default to the fa
> We already are using the SDK style. The limiting factor is the ability to use WPF & WinForms, which .NET Core enabled support for in version 3 and is not backported to Visual Studio 2017. We were able to transition to SDK format earlier because we used Sunburst SDK which had support (sort of) for WPF & WinForms without requiring us to go to 2019. To use .NET Core 3 and thus get support for WPF/WinForms, it must be on Visual Studio 2019.
Private Sub web_LoadAutoProxy(web_Request As WebRequest)
#If Win32 Or Win64 Then
On Error GoTo web_ErrorHandling
Dim web_Parts As Dictionary
Dim web_Domain As String
Dim web_ProxyServer As String
Dim web_ProxyBypassList As String
Set web_Parts = WebHelpers.GetUrlParts(Me.GetFullUrl(web_Request))
web_Domain = VBA.IIf(web_Parts("Protocol") <> "", web_Parts("Protocol") & "://", "") & _
web_Parts("Host") & ":" & web_Parts("Port")
' Cache auto-proxy by domain
I'm happy that I was so confused. For a while, it was an every time occurence, so I knew exactly what to do. Since y'all managed to put the stake through the heart of the ghost so long ago, I was baffled...
Access had crashed, so I'd imagine that's where the ghost came from - it attempting to restart itself, me attempting to prevent it from doing so. It wasn't pretty...
It does seem that much of the state of modern commercial software development is "Oh, look, our competitor has an annoying new feature, let's copy it!"
I'd imagine that it's phoning home with the crash report, too, but with no public acknowledgement. I'm sure we all agreed to it buried somewhere 10 miles deep in all the EULA pile
What is a TempSccObj[1|2] object in the Access forms collection? I now have 2 of them and a search for ms access tempsccobj gives me links to Access in general and a search for TempSccObj gives me recepies for kombucha
guess that coulda been the issue - not a clean import. I do recall an error several imports ago. Reimported, all was good, didn't notice if it added a form
Somehow, I managed to miss migrating some reporting for this new process to prod. Once I'm sure I've got that working well, the next step is to migrate my git repository to the OASYS file structure/names and use a real tool, not my home-brewed half-arsed attempt.
@this That's why y'all dubbed me head of QA, right? :D
If only I was as good at finding the issues in my own code before releasing to the public
> I already have a branch that i have not yet pushed building using the extra SDK and it can build 2019 just fine. I need to test it on 2017, however and handle some other mysterious warnings [ref](https://github.com/onovotny/MSBuildSdkExtras/issues/193#issuecomment-544973179).
Using extra SDK might be sufficient to allow us to support both 2017 and 2019, but that needs to be tested.
The only thing is that the alternatives aren't official support so....
That's why we need to make a decision whether we want to cut off 2017
The extra SDK seems to work. Since it's basically just extension of Microsoft's SDK, it might be all that we need but I have to see if I can build it off the 2017 first.
hrm... I've reorganized my Access project git repo based on the files exported by OASIS-SVN instead of my own Import/Export routines. Everything went fine until I tried to merge.
Use a merge tool. Here is one example:
git mergetool --tool emerge
commands:
a- choose change in A
b- choose change in B
n- next change
p- previous change
q- finish merge
info on emerge
In the future I would only merge into master. have a Master and Develop branch, then branch off of dev...
The way files are actually stored inside the Git repository is not relevant to how they are treated when displayed. So the git diff program, when asked to compare two files, first obtains both complete files from the repository and then runs a difference algorithm against them.
Normally, git dif...
OK, it says "current branch: master" and gives me an option to "Use remote version" or "Use local version". I presume "local" = master branch and "remote" = branch I'm merging from?
i assume in your original system, you had a .frm that contains both layout and code
but with OASIS, it splits into 2 files
normally, layout comes first before the code, so in the original .frm the first few lines will look identical to the new .layout, so probably git notices it and thinks, it's a rename operation
but then again, it's very tricky thing to catch since OS doesn't exactly tell you, "oh, hey, that file was originally named X but the luser changed his mind and named it Y"
weird, using git GUI, it doesn't matter whether I select "Use Remote Version" or "Use Local Version" it says:
Force resolution to the other branch?
Note that the diff shows only conflicting changes.
DataMove.layout will be overwritten.
This operation can be undone only by restarting the merge.
Still. as a rule, i avoid the use of pronouns in such verbiage.
English just doesn't work with more than one. Maybe two, if you use different genders but it breaks down quite easily.
He told him that he had to go and he would stay while he was away. He will organize the things in the meanwhile he is working. He will see him again very presently.
yeesh... finally got the Win10 update to start installing itself. 2 hour update time - unable to use the machine while it reboots 487 bajillion times - nice way to end a WFH day...
not a bad thing, really. It's a 2-hour vacay. The boss did hers first thing in the morning yesterday. Just glared at me when I walked into her office - was astounded that it was going to take so long*! Another person was basically napping at her desk while it did its thing...
And, since we're moving all the way to build 1803, we get to do it again in 13 months... :/
* never mind that there wereWARNINGS that it would run 2 hours...
> **Rubberduck version information** Version 2.4.1.21624 OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64 Host Product: Microsoft Office 2013 x86 Host Version: 15.0.5023.1000 Host Executable: EXCEL.EXE
**Description** The images are slightly different sizes setting off my OCD. Spacing for text between UserForm and Standard module and Class Module shows the different sizing.
**To Reproduce** Steps to reproduce the behavior: 1. Right click within Code Explorer > Add
@this I've seen that before.... VS2019 has a habit of "suggesting" that code analysis might be nice (in one of those yellow banners) and "helpfully" adding that property if you click Yes. So I suspect it may sneak back in...
Dear VS2019. For the seventeenth time of asking, no. I would not like to disable Resharper Ultimate 2019 to improve performance. Could you please quit asking now? Kthxbye.
> An issue was raised after the previous scrollbar for the Code Inspection window was added in by me. I've done a fix for it now (going to make a new pull request which will close the issue, #5237) and I'm going to update this pull request with the fix as well. Sorry about that!
gasps Mat is in favor of 2019? checks if sky has fallen
In that case I might just forget about using extra sdk and just use the plain SDK with built-in UseWPF & UseWinForm properties. That should work and is 100% supported instead of jerry-rigged
fwiw, with a big work project, I tried switching to net472 in the new SDK, and it didn't work. So I was worried that it had a bug, but I just tried with a new WF/WPF project and it seems fine, so it's probably something else in the codebase.
@M.Doerner What prompted me was my failures to reproduce Freeflow's crashing with build 5071. It was not something simple as referencing an errant library.
> I've made the fix now. In regards to the first problem you mentioned, I noticed that if you expand an item and click the icon, the scrollbar won't move and you can still see the icon and start of the text. However, if you click the text, the scrollbar moves. This is because the icon is in a column of its own (Type) and therefore separate from the text (Issue). By default it will center in on a column. I'm not sure if there's a way to override this default behaviour, but I can look into it.
Reading Remarks for InputBox triggers my inner @this. Specifically "For example, for an input box that can accept both text and numbers, set Type to 1 + 2." should be 1 or 2.
Achievement Unlocked: You've awoken my inner pedant.
Use a merge tool. Here is one example:
git mergetool --tool emerge
commands:
a- choose change in A
b- choose change in B
n- next change
p- previous change
q- finish merge
info on emerge
In the future I would only merge into master. have a Master and Develop branch, then branch off of dev...
VBA Rubberducking
VBA Rubberducking