Down key bug in IDE for 10.203

[Crivens]

Note that I realised in a CPU intensive routine that using 3DES in the middle of it is probably a bit of a mistake even though it's pretty fine on most things, so I've replaced the 3DES bit by a screen grab (createscreen with screen 1) of what was going on with the 3DES (doesn't move at that stage anyhow) and paste this instead of using 3DES. Doesn't make a difference to the bug although I thought I'd mention it to exclude the 3DES, plus it gets a few more FPS I would imagine.

Cheers

[Crivens]

Rats. Trying to make a sample project using just the drawing routine and oh happy days it works just fine. Seriously annoying. Right back to see what the hell is going on...

Cheers

[Crivens]

I give up. Must be a lot of stuff I do in the main routine. Strange problem that I would have thought would not come up (createscreen in a function), but sod it can't be bothered mucking around seeing what is going on. I'm thinking it might be alphamode related (I do a lot of mucking around with it) but I dunno. Will ignore for now methinks as I made a work around that suits me just fine.

Cheers

[MrTAToad]

Its always annoying when a routine only causes problems with complicated code

[Crivens]

Yeah. Really can't see why it would do it though. Best guess is something is messing with the alphamode (I do a lot in my game but not at all in my example code), even though I cannot set it to something useful when I draw it. Perhaps need to set it properly when use createscreen? Strange thing is if I then savesprite it loads it in fine with black instead of transparent pixels when I show the highscore chart.

Nevermind, the workaround is fine. When grabbing the 3D screen as a sprite to speed up the background drawing then I just make sure to include the black rectangle before I finish grabbing the screen. So when I draw the background it includes the black rectangle anyway. I'm thinking then that the problem is with transparent pixels in a createscreen as it does not overwrite this with data from the original screen which was there (maybe even though I clearscreen it etc) when the createscreen was made originally.

Still over the years I've had a load of these unexplained ones and I've always done a workaround. Good enough.

Now to get on and finish the damn thing for the app store! No, ang on, mate coming around for drinks. To the app store after lots of beer (ahem and a few more days of ironing out bugs and inserting things like help screens and credits...)!!!

Cheers

[kanonet]

Another Bug in V10.205:
If I compile for Linux the first time, distribution folder gets created with project.linux file inside it. But the file name only contains small letters instead of caps+small letters, like its intended.
If I compile for Linux the second time, it does not replace the project.linux file in the distribution folder, instead it creates a Project.linux file in the app folder. This time it keeps the name like intended.
3rd, 4th... etc. compile just replaces the Project.linux file in app folder, ignoring the distribute folder.

Btw I dont like the idea of the distribution folder (especially for the big platforms), I was just fine with the old way of compiling for Linux, but I understand, why other find that useful.

[MrTAToad]

When compiling for linux for the first time, I had :

, not found (try using -rpath or -rpath-link)

I dont get your strangeness with the filename changing though - it's always lower-case here.