What does it matter that people temporarily couldn't use mouse_x/y for 5 minutes?

When I said useless I meant trivial, and it's not going to break compiling. I expected the mouse update to be added back into the linux platform straight away.

#6 then don't break shit, it is not that fucking hard

Do you know what the optimum strategy is for me to take in order to ensure not break anything? It's for me to not commit anything else. And that's precisely the angle that you guys like to push for when you complain about a largely irrelevant and minor regression like this.

[literally]

1) I couldn't just leave it slow on other platforms, I was moving things around from universe to try and get the speed increase. It would have been more effort than it's worth for me to change everything around to make the functionality of the mouse position work.
2) It took literally 2 seconds to add that functionality back into the other systems
3) mouse_x/y is useless
4) I would have normally made an issue report and have done on other occasion with something like this, I just forgot on this instance. I made a note in the commit message at least and mentioned it on the IRC.
5) The big difference being here that lot's of people actually use Ubuntu. Whereas we're still trying to get the engine to a point where a proper user-base want to use it. Like I said only at that point should we properly care about things such as this
6) I'm not talking about this crap again :p

I personally think that automated regression testing will help these issues a lot.

We could all use a standard test file when going to test if ENIGMA still compiles after changes so it could serve multi-purpose to concurrently report if any regression has occurred.

Forthevin is best at large functional changes/implementation and resolving those annoying little bugs that inevitably wind up occurring and are tricky to squash. I think we need him to have a look over the issues page again, those reports are stacking up

Robert is best at implementing new systems and expanding available features.

I am best at finding those annoying bugs that always crop up everywhere, odd jobs and knowing wtf is going on with everything ENIGMA related.

ExDeus is best at odd graphical systems.

Cheeseboy is best at config set-up, knowing about sound shit and annoying people into doing things.

Josh is best at taking 2 years to write a parser.

Darkace is best at being generally useless.

Ism and TGMG died in a car crash and were later found out to be having an affair.

I will add that I think it's a good idea for any developer to try and look and take note of all the commits that are made. This will reduce the need for fork testing as mistakes can be picked up in this way almost as efficiently and quickly. I do this a lot and find that knowing what commits were made and when comes in handy all the time in dealing with random things that crop up. So am I the only one that currently really does this?

And this whole blame game thing that people like to do with regards to the repo isn't healthy for progress at all. I consider the benefit of progress to massively outweigh the negatives of the odd mistake or regression that might occur. It's hardly like many people are yet using ENIGMA to develop games properly, the progress of the engine is by far the most important thing still at this point. In the future, if more people are developing with it then we will probably want to set-up a more stable repo base by using a common update branch which is properly tested before merging into main. But we're not near that point in the development yet in my opinion, it's more costly to halt the progress with branching and over testing by other developers.

Polygonz, if there is no edit button, THERE IS NO ABILITY TO DISABLE DRAG AND DROP. 

You are crazy, it's called double click the event still.

This is why I said the edit button is pretty useless and the add/replace buttons should be put back : p

Double clicking works fine for me...

That's because nobody bothers with debug code, that's a job anybody could do at any time.

I did tell Robert, I also put a note in the commit message; I should have made an issue report for it as well though. The problem is I can't run and test on other platforms so I can't add in that code when something is changed like that. So I don't really have any other option but to commit it as it is, it's hardly going to cause that much an issue; I certainly consider it preferably to simply stifling progress.

It's your fault, polyfuck. You're drawing a background in screen_redraw without making sure it exists--ie, is not -1.

That debug code tells me all I fucking need to know to figure that out. -5 is global.

The background draw code has been there forever.. I presume before I even came to ENIGMA. This is your worst 'blame me' wrongness yet.

Wow that's great debug code Josh

Maybe the message shouldn't say "you have not saved your recent changes", it could just ask "do you want to save" for now.