> an alternative workaround that might be quicker would be using `Windows + [Arrow Keys]` with the window having focus to make it show up as desktop-splitting and bringing the window top onto the screen.
You could also try adjusting your display settings such that the top edge of monitor 2 aligns with the top edge of monitor 1. I assume that Windows internally renders to a bounding box around the combined resolution of both monitors, resulting in the window being "pushed out the top" of monit
Version 2.5.0.5359
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office x64
Host Version: 16.0.12430.20264
Host Executable: EXCEL.EXE
> Do you have another machine to open it on? Judging from the logs, it looks like there's an issue preventing you from loading the Microsoft.CSharp assembly; whether due to a security policy or actually missing the required file.
> At a glance it looked like a severe oversight on our part and I went and swiftly deleted the pre-release, but then that specific build runs fine here and on other machines... could something be broken on your particular machine's .NET setup?
is `foo` or `bar` considered the factory, in the below? trying to go through some starting material on getting more versed in OOP and am getting a little lost
sub foo()
with new bar(true)
'do something
end with
end sub
sub bar(val as boolean) as object
if val then
set objBar = createobject("firstObjBar")
else
set objBar = createobject("secondObjBar")
end if
end sub
i think foo is a constructor while bar is the factory?
"a factory can be a subroutine that returns an object" seems to fit the above, as bar is object
> @bclothier I don't have another machine I can work on for it, but @retailcoder I'll definitely look into the .Net setup. My company HAS made some changes in the past few months.
@MathieuGuindon i think that's exactly what i was doing
i was only getting to literals in trying to understand, since this feels very dry and it's my first time really digging into the concepts (i spent a lot of time working on "classes" and am just now getting to this topic)
I could be wrong, but I think _Initialize and _Terminate are just callbacks like any other "base class" events - invoked from the actual logic that constructs/destroys the object instance
Maybe "more often than not" rather than "sometimes", though.
@Vogel612 that implies that the reader is aware of the same convention. I don't have control over the conventions that the reader expects me to follow. A number of people read 2 commas as an interjection.
@this "To provide it with a name, we can save the class which will prompt VBIDE to ask you to provide it a name." -- I'm guessing that's Access-specific?
some old timers once told me that in Office 97, the modules were saved separately but that changed in 2000. VBIDE was made with "module is a file" originally and used to have a separate command for compiling all the modules.
TBH, I think purple more of a 2000/2002/2003 when gradients was a big thing at Microsoft. In 97 & before it was a yellow key
Hmm, maybe not.
I don't remember that. But then again, I was too busy picking my nose at that time soooo....
Homer: What about bacon?
Lisa: No.
Homer: Ham?
Lisa: No.
Homer: <expasperated>Pork chops?!</expasperated>
Lisa: <irritated>Dad... Those all come from the same animal.</irritated>
Homer: :laughs: Yeah right Lisa. A *wonderful magical animal*.
@this you're going to think I'm a grammer (argh gosh typing this hurt more than I want to admit) nazi or something, but I believe "we've hid" should be either "we hid" or "we've hidden"
VBA Rubberducking
VBA Rubberducking