« first day (2502 days earlier)      last day (678 days later) » 

12:02 AM
RELOAD!
[Minesweeper] New Users: 16, Games Played: 77, Bombs Used: 56, Moves Performed: 11123
 
@MathieuGuindon why did I know that was going to be the answer? :/
I was not following the abstraction you described earlier very well I think.
The point of the interface between the business and data access code is so that business doesnt know about DbContext at all right? So what members are supposed to be exposed on that interface?
 
12:49 AM
Very stoked; made my first GUI program in twinBasic!
3
(mind you, that's GUI the hard way, not the basic way ;-) )
 
dang looks sweet
 
1:48 AM
I am confused reading the twinBasic site whether it does what RD does or not. It mentions VBA but overall seems more focused on VB6 and developing outside of a host application.
 
[rubberduck-vba/Rubberduck] build for commit 507c9e67 on unknown branch: AppVeyor build succeeded
 
2:43 AM
@theVBE-it'srightforme it allows you to make DLL files that can be reference by projects.
 
2:57 AM
@IvenBach so it complements RD?
 
3:29 AM
You can create your own DLL with the classes and functionality you need with twinBasic. Because it is compiled code it runs faster than VBA code which is interpreted.
It serves a different purpose than RD.
 
 
2 hours later…
5:29 AM
@this a little embarrassed I missed this earlier but dad joke game on point
@IvenBach I see now ty.
 
5:59 AM
Actually, VBA code is actually compiled, too. The main problem with VBA is that it is coupled to the host documents, which is annoying if you want to reference something from multiple places.
In addition, I have the feeling that the VBA compiler does not perform too much optimization; the incremental compiles are a bit fast for that.
 
6:20 AM
@M.Doerner What exactly do you mean by "reference something" here? Like use a certain class in multiple projects?
@MathieuGuindon nvm I found this SO answer and I think it made what you were saying clear: stackoverflow.com/questions/21349950/…
was missing the concept of putting an interface on the context class because I was only thinking about how the business layer would still directly "own" the context object
i see how the generic repos are redundant
also dumped the multiple contexts since it seems easier to go with one for now and add more later if actually needed
Doing this helped me actually understand the concept of the factory pattern properly however so I would say it was worth it overall.
 
6:57 AM
oops then i read the answer below
it is never easy :/
 
 
1 hour later…
8:00 AM
@theVBE-it'srightforme That is a thought-provoking answer. Similar to the discussion @this and I were having earlier, it speaks to how extreme one chooses to be in separating persistence and business concerns. Both EF (directly) and the answer given will abstract the mechanics of database interaction, the difference is in how many different models are used...
... If the persistence model (entities, entity sets) you're using is close (enough) to the form that your business layer wishes to use, you can get away with using it directly. If not, then perhaps it's better to follow the answer, so that you have ultimate control over the mapping process.
But that then means that you'll need to maintain two entire models (and the mapping between them), which is not a cheap proposition.
 
 
2 hours later…
10:08 AM
@theVBE-it'srightforme Let me give an example if what I mean. Let's say you have some piece of code that provides some specific kind of data based on user input. Let's further assume you need that same behaviour in multiple Excel applications. It would be ideal to extract that code into one file that can be referenced by all the application.
However, if it is in a VBA project, you are bound to the exact location of the host files containing the code.
Moreover, if you use an Excel file, it will always open together with the referencing Excel file.
If you had a dll instead, you could register it in the registry and acquire the reference from there, also without the need to open the reference (automatically) in any application.
 
 
6 hours later…
3:43 PM
@M.Doerner Compilation that isn't mandated... I frequently find hairballs of obsolete code from copy-pasta'd workbooks.
Turns into an archaeological dive of "Should this be here? Nope."
 
 
3 hours later…
6:41 PM
> I need to implement this for myself. I'm getting semi-consistent crashes when importing everything in a single action. Importing by module types doesn't crash.
 
7:06 PM
> Personally I think I'd use a "all but document modules" filter. Not sure what to best call/describe it in a dropdown though.
 
7:36 PM
> Does "Non-document VB Files (*.bas; *.cls; *.frm)" fit?

Should we have configuration for which is the default filter selected? Perhaps cache the last selected filter for next use?
 
8:05 PM
How can I link to the latest stable release for RD? I don't want to use github.com/rubberduck-vba/Rubberduck/releases/tag/v2.5.1 since that will change for the next release.
 
8:37 PM
the word latest magically becomes the latest version
 
@HackSlash :le-sigh: I forgot to RTFM docs.github.com/en/github/administering-a-repository/…. #4 states it.
 
 
1 hour later…
9:58 PM
Anyone proficient with how to display relative images on GH? I'm trying and can't get it to work.
 
10:42 PM
 
@IvenBach looks like example 586 shows relative image: github.github.com/gfm/#example-586
Can you be more specific about the problem you are having?
Are you doing some sort of "../../imagebehind.jpg" and getting your wires crossed?
 
@HackSlash It supports relative URL locations. I had a PEBCAK moment, in extreme...
It's so bad I'm too ashamed to state what it was.
 
lol, it's okay. You don't have to tell us.
I just got a new error that basically tells me I don't know what I am doing
 

We're all idiots

Aug 22 '19 at 19:34, 15 minutes total – 24 messages, 6 users, 1 star

Bookmarked Aug 22 '19 at 19:52 by Mathieu Guindon

^ It qualifies to add me to that group.
 
10:54 PM
waves hand the error is that there was an error.
 
I have no idea what that means but I errored my syntax somehow
 
@HackSlash basically Property Get Foo() As Double and Property let Foo(NewValue As Single)
 
Public Property Get Status() As String
Public Property Set Status(ByVal newStatus As String)
 
or alternatively, Property Get Foo(Index As Long) As String and Property Let Foo(NewValue As String)
ah, the problem here is that String is not an object.
you can only Let but not Set a string.
 
^ You can't Set it.
 
10:57 PM
What? My property can't be a string?
oh beans
 
:)
What IvenBach sez so much more succinctly.
 
see? This is the kind of derp
 
@HackSlash I'd also suggest changing newStatus to value or something generic.
 
FWIW, took me a while to see it.
 
Thanks @this
@IvenBach What is wrong with my descriptive name?
 
10:59 PM
Nothing wrong with it.
 
I know this is from another era but VBIDE really could do to use a separate error message for each possibilities.
The current error message is quite... meaty.
 
It is a long list of possible problems
But it's better than "SYNTAX ERROR"
 
and it does say why but not until 4th part (invalid final Set parameter)
LOL, I suppose so
 
The fact the property name is Status and it's a Let property means you're assigning a "value" to it.
 
I am assigning a value, yes. That value is the new status.
 
11:01 PM
"I am Error" is a quote from the NES game Zelda II: The Adventure of Link. The quote is spoken by a villager, apparently named Error, in the town of Ruto. In the original Japanese version of the game, the line is Ore no na wa Erā da... (オレノナハ エラー ダ...), which translates to "My name is Error...". The unlikely character name is widely believed to have been a programmer's in-joke, since the game also features a similar looking character named Bagu (バグ), meaning software bug. In computing, a bug is a flaw in the programming code. Error and Bug are thus assumed to form a comical, in-universe parallel...
 
@IvenBach apparently there was a bug with Bagu's name.
#TIL
back to the property thing - it's curious that VBA won't let you Set a string but you can Let and Set an object both.
 
That is odd considering you absolutely need the Set keyword to set an object.
 
Can you Let an object?
 
Yes, you must Set within the body but defining Let is perfectly legal.
 
^ Ah. That's it. I had plenty of WTF moments on that one.
 
11:15 PM
FWIW, this is legal:
Public Property Get Foo() As Excel.Worksheet
End Property

Public Property Let Foo(NewValue As Variant)
End Property

Public Property Set Foo(NewValue As Excel.Worksheet)
End Property
Change Variant to String, and you get the error about inconsistent properties.
But this is legal, too:
Public Property Get Foo() As Excel.Worksheet
End Property

Public Property Let Foo(NewValue As Excel.Worksheet)
End Property

Public Property Set Foo(NewValue As Excel.Range)
End Property
Heck, you can even do this:
Public Property Get Foo() As Excel.Worksheet
End Property

Public Property Let Foo(NewValue As Variant)
End Property

Public Property Set Foo(NewValue As Excel.Range)
End Property
but Let must not be Excel.Range!
This is fine.
 
11:46 PM
[rubberduck-vba/Rubberduck]: 1313 stars vs. [decalage2/oletools]: 1501 stars
 
@this is devious. ;)
 

« first day (2502 days earlier)      last day (678 days later) »