[C# Tip] Illegal Cross-Thread Operations

BuzzerBee · 2015-06-02 13:17:22

Nothing wrong with Thread.Sleep as long as it's properly threaded. Usually.

I myself am a fan of Microsoft's async stuff (e.g. await Task.Delay)

realmaster42

madiik · 2015-06-02 13:26:58

BuzzerBee wrote:

I myself am a fan of Microsoft's async stuff (e.g. await Task.Delay)

YESSS
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

Tomahawk · 2015-06-02 16:08:56

OMG, until the program crashes, do what's easiest ~ i.e. the one liners. If it's not crashing, there's absolutely no point changing the code.

People who wanna invoke and delegate and use background workers can do that and keep it to themselves, and not try to force it on others.

Leave off claiming that you need complex code to write a simple bot, just because it "might" crash and "might" be harmful in some incredibly improbable scenarios.

realmaster42

BuzzerBee · 2015-06-03 04:47:21

"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.

Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.

Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.

Xfrogman43

realmaster42 · 2015-06-03 08:15:11

BuzzerBee wrote:

"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.
Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.
Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.

If you want to code everything the hardest way, you are in serious troubles my friend.

Xfrogman43 · 2015-06-03 08:23:34

marcoantonimsantos wrote:

BuzzerBee wrote:
"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.
Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.
Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.
If you want to code everything the hardest way, you are in serious troubles my friend.

No, that's called learning how to do stuff differently instead of having to google everything.

BuzzerBee · 2015-06-03 08:28:29

I don't want to program the hard way. And I don't.
Invoking is easy.

I just want to program something that won't spontaneously crash.
I just want to program without taking dangerous shortcuts.

lrussell · 2015-06-03 08:33:22

When writing software, you should always try to be clean and efficient. You should also anticipate potential faults and correct for them. It's not about making it difficult, it's about making it sane.

DarkDragon4900, ewoke, realmaster42, BuzzerBee

DarkDragon4900 · 2015-06-03 09:05:59

The way you take in coding your apps defines your level of experience in programming.
Though they might work the same way, there is a difference between a professional's code and a rookie's.

den3107 · 2015-06-03 11:05:49

BuzzerBee wrote:

"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.
Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.
Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.

When in a company it's about the balance between quantity and how long you work on it (how much you cost).
Right now you don't really have to worry about it, but when working you don't have to fix every single bug. Just the ones that the customer might experience.

2015-06-03 11:16:25

den3107 wrote:

BuzzerBee wrote:
"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.
Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.
Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.
When in a company it's about the balance between quantity and how long you work on it (how much you cost).
Right now you don't really have to worry about it, but when working you don't have to fix every single bug. Just the ones that the customer might experience.

Btw there are many ppl who work in a company, so the person who does checkForIllegalCrossThreadCalls = false; does not have to care. There will be another team to fix these bugs.

den3107 · 2015-06-03 14:11:39

alkazam1448 wrote:

▼someqoutes
den3107 wrote:
BuzzerBee wrote:
"Do what's easiest" okay so when a professional company wants you to code something for them are you going to take shortcuts? Programming isn't supposed to be "easy" it's supposed to be a challenge.
Programming is supposed to dare you to try something new and push you to make the best, most responsive program you can.
Sure, if you're just making a simple program for yourself, so whatever. But personally I like to thinking of programming as a fun, dynamic puzzle with code that can always be improved.
When in a company it's about the balance between quantity and how long you work on it (how much you cost).
Right now you don't really have to worry about it, but when working you don't have to fix every single bug. Just the ones that the customer might experience.
Btw there are many ppl who work in a company, so the person who does checkForIllegalCrossThreadCalls = false; does not have to care. There will be another team to fix these bugs.

And that's where you'll get fired.
YOU make the program, YOU fix the bugs, YOU are the ones that will be looked at when there is a bug found, YOU will be put to blame and YOU ARE TO BLAME.

CJMaeder, BuzzerBee

DarkDragon4900 · 2015-06-03 14:25:51

Shh.
Quiet.
Use whatever pleases you.
Was it checkforillegalcrossthreadcalls or invoking.
Kthxbai.

BuzzerBee · 2015-06-03 19:24:16

DarkDragon4900 wrote:

Shh.
Quiet.
Use whatever pleases you.
Was it checkforillegalcrossthreadcalls or invoking.
Kthxbai.

No

Xfrogman43

realmaster42 · 2015-06-03 20:35:35

BuzzerBee wrote:

DarkDragon4900 wrote:
Shh.
Quiet.
Use whatever pleases you.
Was it checkforillegalcrossthreadcalls or invoking.
Kthxbai.
No

stop forcing newbies to use invoke, seriously...
PLUS, don't force ppl like I or DarkDragon that already know how to code good to use your methods, everyone does what they WANT and know.

Xfrogman43 · 2015-06-03 21:01:37

He is not forcing anybody to do anything, he is saying it is a good idea. You do not have to do anything anybody tells you to do, so just do whatever you want.

lrussell · 2015-06-03 22:00:34

marcoantonimsantos wrote:

BuzzerBee wrote:
DarkDragon4900 wrote:
Shh.
Quiet.
Use whatever pleases you.
Was it checkforillegalcrossthreadcalls or invoking.
Kthxbai.
No
stop forcing newbies to use invoke, seriously...
PLUS, don't force ppl like I or DarkDragon that already know how to code good to use your methods, everyone does what they WANT and know.

Your way is more of a lazy workaround than actually trying to understand why it's a problem and correcting it.

Tomahawk · 2015-06-03 22:17:59

Let's just /thread, and let zubberzee code his bot like it's the next Windows OS. Nobody gives a damn; if it works, it works.

Stawp. Pls.

realmaster42, Xfrogman43

lrussell · 2015-06-03 23:05:51

Tomahawk wrote:

Let's just /thread, and let zubberzee code his bot like it's the next Windows OS. Nobody gives a damn; if it works, it works.
Stawp. Pls.

That's like saying this is a good way to convert a string to an integer just because it works.

public static int? ToInt(string value)
        {
            for (int i = 0; i < int.MaxValue; i++)
            {
                if (value == i.ToString())
                {
                    return i;
                }
            }

            return null;
        }

DarkDragon4900

TiKen · 2015-06-03 23:18:02

Lets end this thread on this quote from my dead relative cousin:

Dead far relative cousin wrote:

I never died playing Russian roulette, why should I stop now? Kthxbai plzgo. Yolo swag.

Rest in peace. I'm sad, but deep inside I know it's better for humanity.

kurtv13, ewoke

Tomahawk · 2015-06-03 23:22:18

lrussell wrote:

Tomahawk wrote:
Let's just /thread, and let zubberzee code his bot like it's the next Windows OS. Nobody gives a damn; if it works, it works.
Stawp. Pls.
That's like saying this is a good way to convert a string to an integer just because it works.
public static int? ToInt(string value)
        {
            for (int i = 0; i < int.MaxValue; i++)
            {
                if (value == i.ToString())
                {
                    return i;
                }
            }

            return null;
        }

You're arguing on the wrong website. Find Stack Overflow or a Youtube comment war.

realmaster42

DarkDragon4900 · 2015-06-03 23:23:23

Lmfao.

BuzzerBee · 2015-06-04 00:12:03

It's not something arguable... The Boolean for illegal cross-thread calls was only kept in later versions of .NET Framework for backwards compatibility...

The only thing you are arguing is your right to take dangerous shortcuts, which is a right you do possess. So keep doing you and let me know when your app crashes

realmaster42 · 2015-06-04 08:13:27

BuzzerBee wrote:

It's not something arguable... The Boolean for illegal cross-thread calls was only kept in later versions of .NET Framework for backwards compatibility...
The only thing you are arguing is your right to take dangerous shortcuts, which is a right you do possess. So keep doing you and let me know when your app crashes

/thread

for (int i=0;i<99999999*9999999;i++)
{
/thread
System.Threading.Thread.Sleep(1)
}

Tomahawk · 2015-06-04 16:09:10

BuzzerBee wrote:

It's not something arguable... The Boolean for illegal cross-thread calls was only kept in later versions of .NET Framework for backwards compatibility...
The only thing you are arguing is your right to take dangerous shortcuts, which is a right you do possess. So keep doing you and let me know when your app crashes

I'll let you know then when it never crashes. Dangerous shortcut my ****.

realmaster42

Official Everybody Edits Forums

#26 2015-06-02 13:17:22

Re: [C# Tip] Illegal Cross-Thread Operations

#27 2015-06-02 13:26:58

Re: [C# Tip] Illegal Cross-Thread Operations

#28 2015-06-02 16:08:56, last edited by Tomahawk (2015-06-02 16:14:11)

Re: [C# Tip] Illegal Cross-Thread Operations

#29 2015-06-03 04:47:21, last edited by BuzzerBee (2015-06-03 04:48:03)

Re: [C# Tip] Illegal Cross-Thread Operations

#30 2015-06-03 08:15:11

Re: [C# Tip] Illegal Cross-Thread Operations

#31 2015-06-03 08:23:34

Re: [C# Tip] Illegal Cross-Thread Operations

#32 2015-06-03 08:28:29

Re: [C# Tip] Illegal Cross-Thread Operations

#33 2015-06-03 08:33:22

Re: [C# Tip] Illegal Cross-Thread Operations

#34 2015-06-03 09:05:59, last edited by DarkDragon4900 (2015-06-03 09:07:32)

Re: [C# Tip] Illegal Cross-Thread Operations

#35 2015-06-03 11:05:49

Re: [C# Tip] Illegal Cross-Thread Operations

#36 2015-06-03 11:16:25

Re: [C# Tip] Illegal Cross-Thread Operations

#37 2015-06-03 14:11:39

Re: [C# Tip] Illegal Cross-Thread Operations

#38 2015-06-03 14:25:51

Re: [C# Tip] Illegal Cross-Thread Operations

#39 2015-06-03 19:24:16

Re: [C# Tip] Illegal Cross-Thread Operations

#40 2015-06-03 20:35:35

Re: [C# Tip] Illegal Cross-Thread Operations

#41 2015-06-03 21:01:37, last edited by Xfrogman43 (2015-06-03 21:02:00)

Re: [C# Tip] Illegal Cross-Thread Operations

#42 2015-06-03 22:00:34

Re: [C# Tip] Illegal Cross-Thread Operations

#43 2015-06-03 22:17:59, last edited by Tomahawk (2015-06-03 22:19:23)

Re: [C# Tip] Illegal Cross-Thread Operations

#44 2015-06-03 23:05:51, last edited by lrussell (2015-06-03 23:06:07)

Re: [C# Tip] Illegal Cross-Thread Operations

#45 2015-06-03 23:18:02

Re: [C# Tip] Illegal Cross-Thread Operations

#46 2015-06-03 23:22:18

Re: [C# Tip] Illegal Cross-Thread Operations

#47 2015-06-03 23:23:23

Re: [C# Tip] Illegal Cross-Thread Operations

#48 2015-06-04 00:12:03

Re: [C# Tip] Illegal Cross-Thread Operations

#49 2015-06-04 08:13:27, last edited by realmaster42 (2015-06-04 08:14:03)

Re: [C# Tip] Illegal Cross-Thread Operations

#50 2015-06-04 16:09:10, last edited by Tomahawk (2015-06-04 16:09:51)

Re: [C# Tip] Illegal Cross-Thread Operations

Board footer