|
Dev - Also, on form submission, use GD to resize the image as a new thumbnail file
|
Dev - In the submission form, you can now upload a banner image
collision_check_segments
 This time, it's basic. In a chance where you need to check if segments collide, as in triangulating polygons with concave parts, you'll have to find if a segment intersects another one. By using simple algebra, I managed to create what I believe is a bug-free code. It is possible for me to find the X and Y values, but then there would be the problem of what would happen if there was no collision. Don't be suprised about how simple this is. It does what it was programmed to do. To clear the lines, press space. It's very basic, and anyone could have made it, but I haven't seen any example like this. So I took an initiative. No need for credit. EDIT: if the line is the same, it returns false. I did that for marbs, but you can easily change that. Target platforms: 
Dev - Warning Dev - After editing rating, make rating display change Dev - When editing, update "edited" column Dev - Restore deleted comments Dev - Display deleted comments if mod (hidden, then with dropdown) Dev - After deletion or during edit, make rating dropdown appear again Dev - Stricter rating rules. Prevent user from rating again Dev - Pages Dev - Reporting
Kenon submitted an example :o
another* example
You broked my combo. :l
I'm pretty sure your code could be simplified further, but good effort anyways.
Yeah, I don't need most of the variables I created aside from to assemble the slope variable and the y-intercept variable, which is used to solve the x location of collision. It just makes it much easier to assemble.
Thanks for making this, I havent found any bugs with it...yet ;)
Simple, effective, original. That's an acronym for SEO. Well, that didn't make sense, but this score does. 9/10.
pretty simple example. basic algebra :P
still, it works. 7/10 
Simple, yes. Effective, halfway. Original, no.
Ok. My explanations: Simple: Yes, all you have to do is use the script. Effective: Halfway. It returns whether the lines collide, but does not tell where, unlike most other such examples. Original: No, Many people (myself included) have made such things.   FAIL
@AlertGames: "basic algebra :P" I acknowledged that
@Gamer3d: I can easily make it where it return the x and y coordinate. Just I was debating on whether to return it via one script to a string, or to make two scripts that return x or y. And I haven't seen something like this in a while. I know it's not original, as marbs just needed something to implement into his game. It workes. @Cat: WTF. Strange. I hope you didn't alter it. Or wait... did I fix that? I really don't know how that could happen. Quote I hope you didn't alter it. Nope. And I redownloaded it and tried it again, and the result was the same.
Just make the first one straight vertical and make the second one intersect it, and you will get that.
@Kenon - I've made this exact same thing before - there are a lot of things that give false positives - parallel lines also give that they do not collide. ^_^
I made a GM7 extension that includes this and more...
If you want to try it, it's here: http://gmbase.cubedwater.com/image_links/cache/ex_124.png
Nice one, jackass, you posted the link to a graphic.
xD!!!!!!!!!!111
lol. This is pretty nice
9/10 
Nice, I like it, I may be able to get some use out of this :) 8/10
|
Recent Activity
|
64Digits attacked by new meteor shower DDoS attack. Over 1000 meteor attacks/sec
