« first day (2540 days earlier)      last day (640 days later) » 

00:02
RELOAD!
[rubberduck-vba/Rubberduck] 2 opened issues. 8 issue comments.
[Minesweeper] Games Played: 108, Bombs Used: 77, Moves Performed: 13874, New Users: 50
 
2 hours later…
02:05
@HackSlash oh, that makes more sense
Changing jobs, @MathieuGuindon? Exciting!
Also, did I forget to say hi to @Vogel612? How did your time as a mod treat you?
Is this a pure C# job, Mat?
 
11 hours later…
13:08
@Hosch250 looking like it; interviewing with another team (same place as earlier this week, different client) in an hour; it's C# and SQL Server, probably with some Javascript and some front-end work that I'll learn as I go along. Job title ".NET Developer" at last!
Mat! Mat! Mat! Mat! Mat!
</cheerleader>
@MathieuGuindon Nice! What company?
Since this is a public chat I'll keep that undisclosed until it's official =)
but it's a nice, not-sinking, well-known one
13:32
"not-sinking" is a bonus...
14:00
wonders if Mug has landed a job at Microsoft to update the VBIDE ;-)
14:11
@mansellan that presumes MSFT even wants to update VB*. :\
@mansellan wonders if wishes hopes prays Mug has landed a job at Microsoft to update the VBIDE ;-) <--FTFY
lol, it's not MSFT :)
 
1 hour later…
15:26
I would think you have the experience and qualifications: you've gotten an MVP from Microsoft, herd cats ducks on an OSS project, contributed as a mod on CR, and anything else that's not mentioned. You have a bit of public exposure for everything you've done, just have to look in the right spot.
15:43
Right now I don't have the option to add a WPF window. I tried adding one manually and updating the file which caused other files to have errors.
do we actually use WPF winodws?
we don't/can't
that's why our windows are all WinForms dialogs
with an embedded WPF host thing
I was unsure about the popup dialgos like hte settings dialog and add/remove reference dialog but indeed those are WPF usercontrols
My mistake on using window. I'm unable to add any WPF item.
Pick "New Item..."
15:55
I'm used to seeing WPF options.
When I do, nothing WPF related is available.
they're just handy shortcuts that depend on the project type/template
@IvenBach there should be a "user control (WPF)" somewhere
could be you didn't install the Win32/Desktop workload for VS?
Same installation I've been using that had it previously.
I have the same list on work and home computer with the RD solution loaded.
If I open a WPF solution, that does have the WPF related options available.
Hence my confusion.
does look every bit like a project template thing. anyway if it's for RD then WPF is already there - pretty sure you could add a new empty file, give it a .xaml file extension, set its build properties accordingly, and then copy the <UserControl ...> markup (and adjust the contents accordingly) from any other existing control
16:01
I attempted to do that previously. That's when had other errors start coming up for InitializeComponent being duplicated.
I'll try again.
probably because of the designer
you don't deal with jsut one file; you have at least 2 I think
FooBar.xaml and FooBar.xaml.cs
yeah
Have to make sure they are related and one depends on the other.
16:03
that's what the class attribute does in the xaml
:derp: It's staring at me the moment I pasted it.
<UserControl x:Class="Hey.Stupid.You.Didnt.Update.Me.And.Thats.Why.I.Gave.You.An.Error.FooBarView"
:)
I wonder why I keep trying some days...
in order to lrean.
Still feels like I make every possible mistake. Repeatedly.
16:10
Let me try again. In order to laren.
@IvenBach that means you're learning every possible thing!
Experiencing every possible thing. One day it'll become learning.
and that is why you keep trying :)
 
1 hour later…
17:26
@IvenBach For the next time Future-Iven has to build a xaml page manually. Don't forget on the file FooBar.xaml to set the Build Action property to Page - stackoverflow.com/a/8170509/7420518.
ummmm... two issues with the new Peek function:
It kinda stays on top of everything....
that's the idea, yes
and it resizes itself in width. If you've got something that's longer than what fits in the vertical box size, it'll jump in width based on... something... as I scroll
Stays on top of the web browser?
@IvenBach starred for future Iven to find #usingthestarfeatureasitwasintended
the dynamic resizing is known and indeed annoying, making it fixed-width would solve it
3rd issue: there should be an icon there
@MathieuGuindon an icon where?
17:31
top left
whelp, it does, in fact, seem to be missing...
you miss a code review, you miss a lot
what's the purpose of having it stay on top of everything, including web browser, email client, everything?
it's a WPF Popup, its intended purpose is for combobox dropdowns.
this is a complete hack
Is any software not a complete hack?
gotcha
17:34
looks like there's a way to tie it to an owner window, ...but here the owner is a UserControl
3
A: WPF Popup ZOrder

timothymcgrathI've tried to solve this issue as well, and have found no good solution. This seems to be the way it is supposed to work, and you can't override that. The only solution I've come up with is to just use a regular layout panel and raise it's Z-Index, so it is the top-level control (this sort of...

basically the intended use is to pop it up, drag it around, do your thing, and close it when you're done
FWIW it shows up on top of VS when you debug it, too
The present owner is a VB*CodePane?
no, the owner is the CodeExplorerControl
sad how it seems nobody else is [ab]using WPF the way RD does lol
yeah, there's a dearth of information on using WPF in non-WPF applications
there's lot of informations but only as long as you're using a WPF project
most of it works for what we do though
just, the odd little thing like setting a Window owner to some component, we can't do :)
or enforcing a consistent stylesheet for everything
17:47
hey easy just edit your app.xaml ...oh
^
I kind of wished it would have worked the same way then it would be less confusing even though we normally use a WPF element host rather than directly hosting an Windows.Application
18:07
I'll leave it to you to decide which and when to fix 'em
there's no way to For Each ... Next through an ADODB.RecordSet is there.
:(
18:53
@FreeMan how do you iterate when you don't know how many there are?
It's a bit like asking the farmer how many eggs his chickens has laid this morning before he has collected the eggs.
@FreeMan the default property of a Recordset is its indexed Fields property, so nope =)
19:49
@mansellan of course I was.
hehe.this vs @this
so tempted to rename my profile to "that" just to troll the channel ;-)
woah, woah, woah, we're lovers, not fighters. You all can have a peace of me instead.
;-)
rofl
uh, so was... pauses... my GH comment reasonable?
Sure. :)
20:05
@mansellan why wouldn't it be? "can lead to boilerplate" is a massive understatement, but other than that...
@MathieuGuindon heh yeah, I was worried about the "kinda OOP" comment... Thing is, VBx is polymorphic. It's just... inconvenient.
And TBF, that's because COM.
sure, but now we're looking at a brand new compiler and language - that COM can't consume an abstract class has never been a showstopper for COM-visible .NET objects...
Yep, not disagreeing. But I've also been watching the VBF comments, and they're somewhat... change-wary.
at the COM level, everything's interface as to avoid depending on language features.
20:09
tB supporting inheritance has absolutely zero impact on back-compatibility
it's like tB supporting RD annotations
@mansellan Sorry, but I disagree. if all tB did was just do what VB6 did, then there's not much appeal for new adoption.
Again, not disagreeing.
Just hope to take VB6 die-hards along for the ride.
I guess the point is that it'll grow with or without their consent. There's a bigger community to be had.
20:11
That's fair
VB6, with modern syntax, could be a competitor to C++, Python, Rust... They're all in the same native space.
> We seem to see twinBasic.NET
ffs
yeah I had to not bite
Oh wait, didn't mean to say Python, that's a different castle!
> How does TwinBasic intend to handle or introduce the concept of multi-threading to VB6?
people don't seem to just grasp the most basic thing about tB: it's not adding anything to VB6. VB6 isn't going anywhere.
^^^
But they want VB7, which MS denied them. So they pin their hopes and dreams...
@MathieuGuindon yeah, I think that's totally the wrong approach.
20:15
VB6 is dead, long live VB!
Oh, btw, did you look at Mercury? It sounds like it's to VB.NET what tB is to VB6
VB6 had multi threading... STA, MTA... still have the PTSD...
I mean no I didn't look-look, but it's pretty much VB.NET continuing forward
@mansellan lol!
In fact, I missed the announcement that VB.NET was being dropped by MS
20:16
It's not, at least officially
wasn't there something to that effect at last MSBuild?
Which frankly was a non-surprise (beside taking so long to finally admit the simple truth that it has been a 2nd class citizen)
thought I saw something
It's just on a slower dev track
I wasn't there.
20:16
me neither
They posted that they have invested in MSForms in the CLR just recently
They just won't support it for Razor/Blazor, which is heavily C#only
Clarify -- MSForms? The COM 2.0 version?
not WinForms?
Sorry, WinForms
Ok that makes more sense. :)
Lol too many product names!
20:18
Ironic as it may be, WinForms and WPF both are here to stay.
I have this pet thought experiment of what a killer UI framework would look like. All I know is none of those.
Yeah, VB.Net apparently supports both. But I don't think they wanna support VB.Net WPF.
I predict WPF will be renamed MPF soon-ish
"Microsoft Presentation Foundation" goes right up there with "Microsoft 365"
Take your pick... there's WinUI, Project Reunion... God knows how they relate to WinForms, WPF, UWP...
Kinda glad I didn't get involved with UWP, it's gonna die soon.
and thee's Xamarin
sometimes it feel like MSFT is just churning out every variants possible to do UI crappily
^ That's gonna be WinUI
Or was in Reunion lol
20:21
sigh
and someone need to tell the marketing dept to cool it with renaming.
Honesttly, how can they have a "project reunion", when there's another UI framework under active development?
way to miss the point.
Copy of Copy of Copy of UltimateUserInterfaceFramework-Final_Final-Final_v2.csproj
Maybe Build will shed some light next week.
in the end, there can be only one. everything will be a <canvas> before we know it.
Heh...we're mulling putting a Blazor island in our WPF app. Mostly to get towards web. Screw Win desktop, web is more stable (!)
20:26
coming soon to a desktop computer near you: Internet Explorer OS
or Google Chrome OS. Or Firefox Linux
no no no IE is officially dead now!
well, next year anyway lol
No, not IE. IE OS.
@MathieuGuindon nonono! It's a "mode" of Edge. You're enterprise is safe, Promise swear!
@mansellan they did say it's on Chromium so....
"You have ActiveX components your business relies upon? Here, we have a browser for you. And hopefully, your users will feel no need to go anywhere else. Ever."
Sooo... here's a GPO you can set to make sure they never ever install FF / Chrome.
Too cynical?
20:33
Anyone have some time to assist? I hard coded the values needed when adding a new component. I'm want to use a view instead but can't figure out the expected process to do so. I think I need to create a Presenter which requires a dialogFactory and I'm unable to find an example to lean for that.
You're making a dialog, right?
Yes.
take the settings dialog as an example
although, "about" is probably much simpler, but a lot of its data is actually hard-coded in the .xaml so it's kind of a bad example
20:39
I was trying to use the MoveMultipleFoldersView as an example but that hasn't panned out.
then walk through the code to see how that all ties together.
@MathieuGuindon Congrats on the new job!
@IvenBach What kind of dialog do you want to add?
hmm i'm wondering if it's even a good example. There's lot of specific stuff that might be not relevant.
One that allows a ComponentName and Folder to be specified when adding a new component via CodeExplorer>Add.
The MoveMultipleFoldersView is based on a refactoring, AFAIR. For those, we have an entire abstract setup.
20:45
This is one reason why I always shied away from forms of any kind. I couldn't grok the concept. It had been easier to stick it in an Excel cell and pull it from there.
The main complication here is that we load WPF controls inside WinForms dialogs. That really does not make it easier to understand.
Basically we load an MVVM style component into an MVP style dialog.
I mostly understand each one separately. Combined, I'm SOL and struggling mightily.
I don't think you should be worrying too much about WinForm - ti should be generalized; worry about hte WPF
^
@M.Doerner thanks!
I think it makes more sense to treat it as a refactoring action. So you should approach it as a new refactoring action.
20:50
That influenced my choice to use MoveMultipleFolders as my example.
@this oh crap I hope at least half of this is still valid lol
Heh, should I mention that you can put a WinForms element inside WPF? Oh, wait... too late.
MS UI is a mess
I'll read that after traipsing through the SettingsCommand button as it executes.
@IvenBach No forget that.
I think a refactoring action makes for a better example
Forget what? I haven't ready anything...
20:53
@MathieuGuindon I browed quickly and it seems to be still current.... I hope.
It takes me a long while to internalize what I read.
@IvenBach settings form would not be a good example for you to follow
A better aligned suggestion would be a refactoring dialog?
because there's lot of stuff that are specific to the settings form that would be distracting. Any refactoring dialog --- I would probably start with rename dialog would be a better example.
aye, it's got many dependencies and services attached... multiple views, ...definitely the most complex dialog in RD
20:54
^
and given what you need to do, you need services that the setting dialog doesn't have but refactoring dialog will have.
@IvenBach bear in mind: WinForns is basically close to how Windows natively renders things. WPF is an intruder - "gimme an area and I'll do the rest".
I've always had the Excel grid to use as my UI. Forms of any kind is all new.
The ghost (!) of Joel Spolsky continues to haunt all UI framework
yyooooouuuuu arrrrreeeeeee reeeeeinnnnveeeennnnntttttttiiiinggggg Excel
BTW, the MoveMultipleFoldersDialog is basically a copy of the rename dialog.
The suiss army nife of teh all things.
20:58
> At the end of the day, every requirement can be reduced to "Let me do this in Excel"
^^ That mentality carried me too far along.
If it's not gridded I can't understand it...
and everyone who opens Access for the first time hypervenilates. where's my limitless columns and rows?!?
@IvenBach Excel is not a UI. It's a spreadsheet.
@M.Doerner would you suggest [Rubberduck/Rubberduck.Core/UI/Refactorings
](https://github.com/rubberduck-vba/Rubberduck/tree/next/Rubberduck.Core/UI/Refactorings/Rename) and [Rubberduck/Rubberduck.Core/UI/Refactorings/MoveToFolder](https://github.com/rubberduck-vba/Rubberduck/tree/next/Rubberduck.Core/UI/Refactorings/MoveToFolder)?
21:02
Both are basically identical apart from the models used.
:deep-breath: Time to try again.
I'll eventually get this. I just want to understand how to do it properly once I finish.
I think it would be easiest if you create a RefactoringAction for what you want to do with an appropriate model and then set things up like for rename.
@mansellan and user writes in, "I love your product! But could you add ability for me to move columns around and copy'n'paste rows? "
@this bt;dt.
@mansellan Oh no... It's definitely a UI. Everyone else is just definitely doing it wrong.
21:05
@IvenBach bt; dt.
honestly, both.
So for the XAML portion just do everything as is normal with MVVM. When it comes time to display the usercontrol that is when MVP takes over?
Excel has a grid layout, formulas, and Alt-F11. It's crazy addictive, and I should know - it was my intro.
I just had the good fortune to outgrow it quickly.
@IvenBach well yes but I wouldn't say "take over" --- Winform & MVP is how we display the dialog which will have only a WPF host element control
the Winform dialog itself is dumb and does nothing interesting besides providing a container to house the WPF contents.
22:10
Does anyone know of a spy++ equivalent that can work with context menus?
22:23
Just installed the last RD version.
What did you do???
It's bloody fast! After like 2 years it's immensely more usable now than ever! Loving this.
5
After my last cry few weeks ago (when I even posted gifs that it's unusable when clicking faster than 1 click per 5 seconds), I think something has changed for sure.
:-) You made my day.
 
1 hour later…
23:46
[rubberduck-vba/Rubberduck]: 1340 stars vs. [decalage2/oletools]: 1550 stars

« first day (2540 days earlier)      last day (640 days later) »