Learn2Program PB outdated?

[TwoCatsYelling]

@TwoCatsYelling

Please take a look at blueznl's "PureBasic Survival Guide" it's a nice tutorial:

PureBasic Survival Guide

also download the PureBasic Book from purebasic.com, it's a must read:

PureBasic.pdf

lastly, don't forget to use google search to search for content in this forum:

Search PB Forum

Thank you.
Norm.

Excellent resources! Thanks! Got them downloaded/bookmarked.

Searching for info in the forums... that'll be hit or miss for a bit. There's going to be times, for a bit anyway, where I'm not even sure what the right question is lol.

Thanks again!

[Axolotl]

...
Again, that may not have been the intent, but it just seems kind of "braggy".

okay, that's not what I meant. I have great respect for anyone who wants to learn programming. In no way do I want to come across as "boastful" here. Sorry.

[TwoCatsYelling]

...
Again, that may not have been the intent, but it just seems kind of "braggy".

okay, that's not what I meant. I have great respect for anyone who wants to learn programming. In no way do I want to come across as "boastful" here. Sorry.

Okay, cool.
I apologize for the rather harsh response. Hard to know when something is just written and not spoken, and there's no prior interaction with someone.

I've known and worked with some rather "braggy" programmers in my professional life, so maybe my brain "expects" that on some level.

Thanks for clearing that up!

[TwoCatsYelling]

Dipping back to the InitSprite() thing...

Read this part in the book...

The InitSprite command let’s PB know that you want it to use the game
graphics commands known as “sprites.” We’ll be discussing sprite
commands in full detail later in the book, for now though just know that
when performing any commands regarding to full screen games, open
through OpenScreen command, you must be sure that the user
environment is capable of dealing with them, and InitSprite checks this
out for you

Just want to make sure...

Is this basically saying that the program is going to *automatically* InitSprite, so I don't have to? It's just checking to make sure the system running it can use sprites?

That's a really ugly summary, I know... lol

What led me to start this thread was thinking I had to explicitly initialize it myself. But now I think I might have been mis-reading it from the start.

[Demivec]

Dipping back to the InitSprite() thing...

Read this part in the book...

The InitSprite command let’s PB know that you want it to use the game
graphics commands known as “sprites.” We’ll be discussing sprite
commands in full detail later in the book, for now though just know that
when performing any commands regarding to full screen games, open
through OpenScreen command, you must be sure that the user
environment is capable of dealing with them, and InitSprite checks this
out for you

Just want to make sure...

Is this basically saying that the program is going to *automatically* InitSprite, so I don't have to? It's just checking to make sure the system running it can use sprites?

That's a really ugly summary, I know... lol

What led me to start this thread was thinking I had to explicitly initialize it myself. But now I think I might have been mis-reading it from the start.

To restate the first quote in other words:

The InitSprite() command needs to be executed to let PB know that you
want it to use the game graphics commands known as “sprites.” We’ll be discussing
sprite commands in full detail later in the book, for now though just know that
when performing any commands that will be used specifically for drawing and
interacting with screens created with the OpenScreen() command, you must first
be sure that the user environment is capable of dealing with them, and InitSprite()
checks this out for you and is required to be executed to enable the use of any of
the other 'screen graphics' commands. It only has to be executed once in a
program and is usually included early in the program execution.

[TwoCatsYelling]

Dipping back to the InitSprite() thing...

To restate the first quote in other words:

The InitSprite() command needs to be executed to let PB know that you
want it to use the game graphics commands known as “sprites.” We’ll be discussing
sprite commands in full detail later in the book, for now though just know that
when performing any commands that will be used specifically for drawing and
interacting with screens created with the OpenScreen() command, you must first
be sure that the user environment is capable of dealing with them, and InitSprite()
checks this out for you and is required to be executed to enable the use of any of
the other 'screen graphics' commands. It only has to be executed once in a
program and is usually included early in the program execution.

That helps clear it up, thanks!

[BarryG]

Searching for info in the forums... that'll be hit or miss for a bit. There's going to be times, for a bit anyway, where I'm not even sure what the right question is lol.

I totally get this! I started a new job some time ago and a lot of their operational processes are online, and we're expected to "search the database" to find out how to do something. This is ridiculous for a job, and I found it easier just to ask a co-worker. It was a very stressful time for me because everyone was saying I should be fired for not knowing how to do the job, even though I was new!

Searching is only useful if you know what terms to search for.

[TwoCatsYelling]

Searching for info in the forums... that'll be hit or miss for a bit. There's going to be times, for a bit anyway, where I'm not even sure what the right question is lol.

I totally get this! I started a new job some time ago and a lot of their operational processes are online, and we're expected to "search the database" to find out how to do something. This is ridiculous for a job, and I found it easier just to ask a co-worker. It was a very stressful time for me because everyone was saying I should be fired for not knowing how to do the job, even though I was new!

Searching is only useful if you know what terms to search for.

Yep! Difficult to search for answers when you aren't sure what the question is :p.

That job you described... It didn't happen to be a call center, did it? I worked at a call center for a time where your pay was based on a grade, which was scored in large part on the accuracy of the info you gave clients. The company deliberately put info under the wrong categories, or in completely unintuitive locations, so people would be more likely to give wrong info, keeping their grade and, thus, pay lower. When people started catching on to where info was actually located, they'd move it around again. Was an open secret. Everyone knew they were doing it, but the higher-ups denied it, and your job was threatened if you questioned it. Kinda like the rampant nepotism at my current job... but that's another topic.

Pretty messed up. I got out of there quick lol.

[BarryG]

No, not a call center. As the sole bread-winner for my wife and kids I can't afford to rock the boat about it. I'd leave the job if I could but nothing else pays as much or I don't have the qualifications.