Once, at school, last year, we had to present a C# project that, upon clicking a button, took words from a .txt file and showed them in an alphabetical listBox...

Since the file they gave us was so long that we had to wait a minute or so to get the listBox full, I implemented a progressBar which popped up on the button, and upon clicking it, the progressBar advanced for every word it loaded, until, upon finishing, it would have disappear leaving again the button, and the listBox would have been loaded.

Apparently, this choice alone – even if it had next to nothing to do with the exercise – was enough to give me a solid 9 out of 10, because our professors never explained us about progressBars and I used that completely on my own... I tend to do things like this in class, where I explore what my tools could give me.

So long story short, I ended up having the best vote in class for that, and I was so happy and motivated :D

Moral of the story: if you can, always try to learn something new about your tools and your programming language, on your own, because apparently it gives you advantage towards others, at least in school. Or even if you're not in school, it could still be something cool to learn that might be helpful in the future, for your projects or your job's projects.
The more you know, the better!

So.... yeah, making a Scratch clone (with more features) is frustrating and super hard.

Major problems include
- Drag&Drop from listbox to usercontrol - stress level : 3/10
- connect blocks when two blocks are close to each other - stress level : 10/10
- generate live code when there was a change in blocks editor - stress level : 9/10
- write a compiler or some interpreter that converts block code to real c# code - stress level : 10/10
- generate output by calling csc.exe - stress level : 1/10
- make code at least readable - stress level : 7/10

When I was on my first internship, I started developing an Android app, while my friend developed a C# program that read a .txt with info and references from a mail service (in my country it's CTT).

The damn .txt files got really really big, na she had to display all of the data in a listbox (it was a PoC) and when he pressed the item, it had to fill some fields at the left of the listbox.

Needless to say, he didn't learn of multi-threading yet, and I had, so I taught him how to multithread so the app wouldn't lock up while loading the massive .txt file.

The listbox filling made a cool animation (like CMD executing commands from a bat file) and we even implemented a progressbar.

I felt like a badass Dev after that.

Wpf Rant
Seems kinda retarded but it should be trivial to reference a ListBox in a SelectionChanged event doing something like SomeListBox.Items[someIndex] = new TextBox()

in order to replace a simple textblock element with a textbox element that accepts input (replace-in-place), but it's proven to be the most long, aggravating series of unnecessary convoluted bullshit I have encountered so far.

And when I do something like ((ListBox)e.Source).SelectedItem = new TextBox(), nothing break per se but I get no god damn error or feedback, as if it worked, but nothing fucking changed.

I can only assume I'm fucking retarded or like most of the shit coming out of microsoft, WPF is a broken pile of bullshit.

I'd ask on here but every time I ask technical questions I never get any fucking answers. Like a ghost town around here sometimes..

Monday morning brain funk while looking at a support case right now.

Apparently there is a listbox (zkoss) that lets you select users via check box to send emails/alerts whatever.

If you select 3 users it counts the number correctly, but it doesn't iterate through and find the 3 actually selected 😂

Instead it just reads the number selected and iterates through that many times from 0 🤔

Happy Monday 😂😂😂

visual basic dotnet
ComboBox and ListBox both have Items property, and also both are descendants from ListControls
but ListControls have no Items property
do those developers understand object oriented programming correctly?