first Cobra example#1: .....

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|711\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> first Cobra example#1: .....
Fri, 29 Dec 2006, 04:04
power mousey	hi all, first Cobra example program uses keyset,pure2d var rnum,rnum1,rnum2:real result1:real Function addrealnumbers(rnum1:real,rnum2:real):real Begin result1=rnum1+rnum2 End Begin rnum=addrealnumbers(2.0,5.0) MessageBox("2.0 plus 5.0 = " + rnum) End --v cheers, power mousey
Fri, 29 Dec 2006, 04:14
Jayenkai	Tweaked.. program uses keyset,pure2d var rnum,rnum1,rnum2:real Function addrealnumbers(rnum1:real,rnum2:real):real Begin result=rnum1+rnum2 End Begin rnum=addrealnumbers(2.0,5.0) MessageBox("2.0 plus 5.0 = " + rnum) End --v You needn't declare "Result", result is an inbuilt variable used for returning values from functions. Whereas before you did Return a+b you now do Result=a+b (although I'm sure Graham could spend 2 minutes adding a Return Macro/Definition/Command, which simply gets changed to "result=" during compilation.) -=-=- ''Load, Next List!''
Fri, 29 Dec 2006, 04:31
power mousey	oh oh!!! oh whoa!!! in my second simple example program uses keyset, pure2d var rnum,rnum1,rnum2:real result1:real Function addreals(rnum1:real, rnum2:real):real Begin result1=rnum1+rnum2 End Begin rnum=addreals(2.0,5.0) If rnum=7.0 MessageBox("equals 7 ") Else MessageBox("doesn't equal 7") Endif --v the if condition fails...when using rnum. I even used a workaround of declaring another variable such as inum:integer and then assigning inum to--> inum=Floor(rnum) and then modifying the If conditional to If inum=7.0 I keep getting a messagebox of 'doesn't equal 7' However, if I used the return value in the conditional...the program works so it would be If result1=7.0 then the messagebox displays 'equals 7' this will work but just using the function will not work. such as If addreals(2.0,5.0)=7.0 I don't think the return valuse is being place in the function. If this was intentional...I think the return value should be. However there is a bug witht he If conditioal not recognizing the main variable which should be returing or placing the return value in the main variable of rnum. As shown in the first example. Definitely another bugger bug.
Fri, 29 Dec 2006, 04:33
power mousey	yes you're right Jay. I fount that out. I was going to mention that. But those otehr bugs came up. You were right about the if conditionals. Definitely, needs fixing. let me try something that just came to my mind.
Fri, 29 Dec 2006, 04:47
power mousey	nope...it didn't work. I think there is some kind of quirky bug in Cobra. Its working in the first program. But in the second program which is the same....for some reason the return value of result1 is not being placed into rnum. Yet, the return value is being held with the true actual value. hmmmmmm.......scratches fur and ears. The return value works but what is the point of using a main variable and assigning it to the function...which the main variable will hold the actual return value...and its not doing it. shesshhh!!!, might as well just use the return value in the function for comparions rather than the main variable. Hopefully it will be repaired and fixed. cheers, power mousey
Fri, 29 Dec 2006, 14:05
power mousey	I have tried the demo patch for Cobra. cough!! cough!! did not fix the problem or issue with the Function. though there are other problems too. example: program uses pure2d, keyset Function addreals(rnum1:real, rnum2:real):real Begin result1=rnum1+rnum2 End var rnum:real Begin rnum=addreals(2.0,5.0) //this should display the message of //'2.0 plus 5.0 = 7.0 //but alas, it does not, but the value is 0 //however, //if I replace the variable of rnum with result1 //in which result1 is the return value..it works!! //it displays '2.0 plus 5.0 = 7.0' //apparently, the return value is not being placed //in the real variable of rnum MessageBox("2.0 plus 5.0 = " +rnum) End --v ackkkkkkk!!!!!, power mousey until it is addressed and even fixed...I will use this as a work around. just use rnum as a dummy variable in calling the actual function and just using the return value...which in this case is result1.
Fri, 29 Dec 2006, 14:37
grahamk	Sorry to be negative, but there are no problems there. Are you even trying the examples, or just typing stuff into this forum ? The example you give above do not even compile (you get an undefined variable at line 9), so there is no way you could have run them Change result1=rnum1+rnum2 to result=rnum1+rnum2 and everything works, and doesn't give a syntax error.
Fri, 29 Dec 2006, 14:51
power mousey	graham, it doesn't matter if you are negative or not. In other words you don't have to apologize. For good or for bad or just for in-between along within the extremes...just talk and share with me. hey myself, I have learned and matured a little along the way. true. yes, it didn't compile so I declared result1 as a real in the var section. I will put this in. let me try this out. I'll be back! cheers, power mousey ---- alright!!! thank you Graham. Its fixed. a beer and a pizza for you. true. program uses pure2d, keyset Function addreals(rnum1:real, rnum2:real):real Begin result=rnum1+rnum2 End var rnum:real Begin rnum=addreals(2.0,5.0) MessageBox("2.0 plus 5.0= " +rnum) End --v all cheers, power mousey ---- Graham, I have another question and comment. It concerns with moving a sprite on the screen. Not rotating it but moving it with a Pong like effect. I created a Pong-like game and with this alien bug as the ball. Yet, it moves jerky like and is blurry. I used all kinds of timing speeds with both the Pause() command and also with a time limiting algorithm using start=Millisecs as a timer. I used various values from 2 all the way up to 150 for the timer value in the conditional. I still see and get the jerky movement of the bug and also it still blurs. Could this be due to the Snakebite debugger being enabled? Could this have an effect witht he performance and with the graphics moving? wondering and curious, power mousey new editey--> let me try a few things out
Fri, 29 Dec 2006, 16:10
power mousey	nope. the ideas didn't work the image loaded as a sprite...and then later on laoded as an image did not eliminate the jery movements at times and also the blurs too. maybe I need new glasses. mousey needs a new pair of specks. cheers, power mousey
Sat, 30 Dec 2006, 05:00
power mousey	sigh!! oh well, sorry but I'm going back to Blitz3d and DBPRO. And awaiting for the XGS 2: the cube shaped home computer later this year. The Diablo has eventually destroyed the Cobra. www.internationalhero.co.uk/d/diablo2.htm cheers, power mousey
Sat, 30 Dec 2006, 18:29
garand	and you were so set on it back at CW.com
Sun, 31 Dec 2006, 00:32
shroom_monk	Well, I guess that's what it is, garand. Cobra was much awaited by all, but then there were delays delays delays. People were probably expecting more from something so long in development. -=-=- A mushroom a day keeps the doctor away... Keep It Simple, Shroom!
Sun, 31 Dec 2006, 01:01
N/A	People were probably expecting more from something so long in development. You've got to remember that the 3d component was developed at the same time, so you're only seeing a part of the whole at the moment. -=-=- A mushroom a day keeps the doctor away... Keep It Simple, Shroom!
Sun, 31 Dec 2006, 16:14
power mousey	@garand, yes, you're right I was for a time. Then....well lets say issues and conflicts with cough! cough! Promises,Promises. And to interject have you heard or listened to the song Promises, Promises by Naked Eyes? Obviously now, they are resolved and forgiven. Cause now I'm uisng and testing Cobra. true? and shroom says it even better than me...in this case. thank you, shroom. serious. but its too bad, cause I like Cobra. But this one thing or issue or glitch with the blurry sprite or image and its jerky movements at times. It just bothers me...like Play Basic did. But in Play Basics' case the demo was great but the full version and upgrades since have not fixed a similar problem. sincerely, power mousey
Mon, 01 Jan 2007, 10:49
magicman	[quote = fluke] You've got to remember that the 3d component was developed at the same time, so you're only seeing a part of the whole at the moment. So when do we get the 3D demo then? -=-=- Stuff... Yeah...