Loading Screen - Printable Version +- Qbasicnews.com (http://qbasicnews.com/newforum) +-- Forum: QbasicNews.Com (http://qbasicnews.com/newforum/forum-3.html) +--- Forum: Challenges (http://qbasicnews.com/newforum/forum-10.html) +--- Thread: Loading Screen (/thread-1439.html) |
Loading Screen - Sterling Christensen - 07-16-2003 Here's my entry. Remove the delay loop if you want to see how fast it can go. Code: DECLARE SUB endLoading () Loading Screen - Ninkazu - 07-16-2003 Whoa, that's pretty cool! Somewhat small too. Crap, now I may not win Loading Screen - oracle - 07-17-2003 I've updated the challenges page at QBNZ. Go have a look. Loading Screen - Ninkazu - 07-17-2003 37.5? Cheh, I was expecting at least a 40... What do you suggest for more color? The reason the program is slow is because it's using a buffer (it can't get ANY faster than just about 40 fps, and even so, you can't notice anything higher than 60) Do you suggest I take out the buffer and let it have flicker? I hope not. Loading Screen - oracle - 07-18-2003 I get 288FPS uncompiled. Which is really wierd... The loading bar sucks. There's no indication of where 100% is. The colours are still dark, and the black background can be changed for more points (every entry so far has used a black background, be original!) Also, where is the delay? I did state in the rules that slow screens would be penalised. However, you get the award for "best variable names" Loading Screen - Ninkazu - 07-18-2003 What do you mean, "Where's the delay?"? I have the percent increased whenever a certain variable equals 10, but no actual delay on the rendering. Also, there IS a way to tell where the bar ends. Notice how it goes from dark to bright to dark? the last dark is 100. Ok? ahahaha. The variable names are just stupid crap for FOR loops, or... are you talking about "blorg"? There's really no way to have a cool background without just making a BSV, but I didn't want external files. Or are you suggesting I have a BRIGHT color scheme with a white background? You should know by now that I'm a dark person. Loading Screen - Sterling Christensen - 07-18-2003 Oracle, if I'm not mistaken, this is where you put the loading routines in his program (see the comments): Code: WHILE percent < 101 It's not like it only goes at that one speed, you can increase percent as fast as you like, you just have to take out the lines that fake the percentage. Loading Screen - Blitz - 07-19-2003 I don't get it, why no libs? Loading Screen - oracle - 07-19-2003 Blitz: I want to see *your* code. Because 1) I'm not very experienced at using libraries and 2) Some people who enter (probably most) don't know how either, which ruins it for them. However, you are free to make something with UGL, although it won't count Nink: The last dark? I know what you mean, but when it's that dark it's hard to tell. What I want is like a box with the line in it so when the line reaches the end of the box that is 100%. I'll retest your program for speed later. Loading Screen - na_th_an - 07-19-2003 Quote:Blitz: I want to see *your* code. Because 1) I'm not very experienced at using libraries and 2) Some people who enter (probably most) don't know how either, which ruins it for them. I never understood that general opinion/belief. Mostly 'cause using libs makes your life easier. Always. Pure QB stuff, appart from being slow, is harder to code and give you more headaches than LIB stuff. For example, any animation with double buffering in PQB is such a hassle and that can be solved with just three lines of LIB calls. If you wanna code a double buffered animation in PQB, you may either: 1.- Use SETVIDEOSEG and QB drawing functions. 2.- Code your own blitters that draw to a buffer (PUT compatible, of course) Both two sollutions are really a big hassle. With most libs, you just create a buffer with a function that returns a handle, then you use that handle and pass it to the drawing functions in the lib, then you use that handle again and pass it to the function that copies the buffer to screen. If you read this: http://faq.qbasicnews.com/?blast=DoubleBufferingConcepts you'll realize what a hassle is doing stuff in PQB. Not 'cause it is PQB, just 'cause if you wanna efficient blitters and fast (?) animation, you need to code stuff from scratch, and such things are already cleanly and "fasterly" coded for you in any LIB. PQB for the challenge of doing it may be cool, but PQB 'cause "LIBs are harder" is a nonsense. In fact, LIBs are there for lazy programmers like me who don't like to reinvent the wheel. If I had to code my blitters and double buffers, I would not code. I'm too lazy |