« first day (2218 days earlier)      last day (41 days later) » 

12:01 AM
RELOAD!
[Zomis/Games] 1 commit. 356 additions. 46 deletions.
[Minesweeper] Games Played: 108, Bombs Used: 71, Moves Performed: 13074, New Users: 12
 
 
13 hours later…
1:01 PM
[rubberduck-vba/Rubberduck] MDoerner pushed 17 commits to next (only showing some of them below)
[rubberduck-vba/Rubberduck] IvenBach pushed commit 664c7d99 to next: Correct default public interface extraction
[rubberduck-vba/Rubberduck] IvenBach pushed commit 79540a49 to next: Merge remote-tracking branch 'upstream/next' into Issue5346_Extract_interface_creates_private_classes
[rubberduck-vba/Rubberduck] IvenBach pushed commit cd9f7565 to next: Merge remote-tracking branch 'upstream/next' into Issue5346_Extract_interface_creates_private_classes
[rubberduck-vba/Rubberduck] IvenBach pushed commit d0a341a4 to next: Update instancing selection to use combobox
[rubberduck-vba/Rubberduck] IvenBach pushed commit b927e4ab to next: Merge remote-tracking branch 'upstream/next' into Issue5346_Extract_interface_creates_private_classes
[rubberduck-vba/Rubberduck] IvenBach pushed commit 5904fa1a to next: Clarify instancing wording notice
Remove unused converters

Their declaration in XAML in made redundant by the ResourecDictionary.
[rubberduck-vba/Rubberduck] IvenBach pushed commit 864167e9 to next: Remove unused code
[rubberduck-vba/Rubberduck] web-flow pushed commit 97ed7d30 to next: Merge branch 'next' into Issue5346_Extract_interface_creates_private_classes
Merge pull request #5357 from IvenBach/Issue5346_Extract_interface_creates_private_classes

Issue5346 extract interface creates private classes
 
1:19 PM
Anyone have any interesting use cases or techniques for triggering VBA when a user double-clicks a cell/row?

"...you could do different things on a double click or right click with ctrl held down."
4
A: Control double click event for row header

KekuSemauThe DoubleClick Event does not fire when the headers are doubleclicked. I don't think there is any trivial way around this - you have to live with the events as they are provided. I think there are still enough room to implement more functionality. To give you some more ideas, you could do dif...

 
@User1973 what are you trying to do?
DoubleClick event is the way to go.
that is if you're clicking a cell.
... but I assume that's not what you want to do.
 
@BigBen I actually haven't tried much yet. I came across this technique recently, and I can't help but think it will be really handy for something. I just don't know what, yet.

It might be handy to make a spreadsheet where a user can double-click a parent record in a table in Sheet A, which would open Sheet B and highlight a child record in a table there.
 
@User1973 If you're clicking in a table, then just use the Double Click event. What you propose sounds very doable.
 
[rubberduck-vba/Rubberduck] build for commit 669c4d86 on next: AppVeyor build succeeded
 
 
1 hour later…
2:29 PM
@BigBen Cool. Thanks.
 
2:59 PM
@User1973 VBA+OOP Battleship uses the Worksheet_DoubleClick event to confirm a ship or attack position. Seen it?
ah, it's actually Worksheet_BeforeDoubleClick github.com/rubberduck-vba/Battleship/blob/master/src/…
 
@MathieuGuindon I really have to download that lol
 
@MathieuGuindon Holy smokes. No, I had not seen that!
 
3:38 PM
[rubberduck-vba/Rubberduck] build for commit 9fcad5a0 on unknown branch: AppVeyor build succeeded
 
4:01 PM
[rubberduck-vba/Rubberduck] build for commit 4b01a60d on unknown branch: AppVeyor build succeeded
 
4:21 PM
@MathieuGuindon long time no answer.
 
[rubberduck-vba/Rubberduck] build for commit f536ffad on unknown branch: AppVeyor build succeeded
 
@BigBen =)
 
COVID and work screws with answering questions.
 
4:37 PM
and coding OSS, and writing blog articles, and writing a book, and... ...at this rate I'll be a 3-term MVP :)
4
 
[rubberduck-vba/Rubberduck] build for commit d68a0ddd on unknown branch: AppVeyor build succeeded
 
5:08 PM
[rubberduck-vba/Rubberduck] build for commit 66d00b0e on unknown branch: AppVeyor build succeeded
 
5:19 PM
You were right with the Excel process. I have 78 ghost instances of it LOL — t3chb0t 17 secs ago
lol
 
5:51 PM
Yikes!
 
@MathieuGuindon - there's a new answer posted. It's quite cute.
 
IDK, has a feel of "clever code"
 
haha
I did say it was cute. Cute is close to clever.
 
 
4 hours later…
9:44 PM
> The installer is currently prompting our users to accept the terms of a license that has nothing to do with end users beyond "well you can download the source code too if you want".

Rubberduck doesn't have an *End User License Agreement* to agree to. IANAL but I doubt we *need* one? Let's remove that installer step.

Or better... come up with a witty *legalese-looking* parody of a EULA to present instead?
 
10:08 PM
> # End-User License Agreement ("Agreement")

Last updated: July 02, 2020

I know you're not going to read this End-User License Agreement carefully before clicking the "I Agree" button, downloading or using Rubberduck.

# Acknowledgment

By clicking the "I Agree" button, downloading or using the Application, You are agreeing that humans should not be bound by EULAs that take longer than 30 seconds to read. If You do not agree to the terms of this Agreement, do not click on the "I Agree"
 
@Duga This one caught me off guard entirely.
 
@Duga lol, something like that - although, removing the step and hiding the Easter-egg fake EULA in the STDOUT output of the installer executable when it's executing via command-line with the -duck switch provided, could be fun too
@IvenBach same :)
 
> I suggest changing Company --> Rubberduck (hereafter referred to as 'The Duck'). That way when reading:
- The Duck grants You ...
- The Duck reserves the right...
- ... liability of The Duck and any of ...

The 3rd person makes all the difference.
> I suggest changing Company --> Rubberduck (hereafter referred to as 'The Duck'). That way when reading:
- The Duck grants You ...
- The Duck reserves the right...
- ... liability of The Duck and any of ...

Doesn't matter what the first 2 people do. The 3rd person is always better.
 
10:23 PM
@Duga Presenting the GPL and having it agreed has one merit though: you have to acknowledge that there is no warrenty whatsoever.
That statement should definitely stay.
 
absolutely :)
> EULA: If it works, it works. If it doesn't work, pull requests are welcome. Enjoy!
 
 
1 hour later…
11:57 PM
> GPL **is** an EULA, though. It was literally created to enforce protections of the rights of **end users**. It's an end-user focused license that the installing user agrees to. :tada: it's an EULA :)

Just because most companies are attempting to enforce restrictions on the end user through their EULAs, that doesn't make a permissive license "not an EULA".
 

« first day (2218 days earlier)      last day (41 days later) »