Final call for scmdraft
Topic Locked
Topic Locked|
お や す み
|
double click on location brings up properties box, sometimes that causes the location to move?
Press enter to avoid this situation. I'd love some better scrolling options. Now, when I press the arrow keys to scroll and move the cursor, it moves very slowly. If there are a lot of sprites, this also happens, or if there is a grid active. The mouse wheel doesn't work either. I'd very much enjoy a ctrl+wheel to zoom, and possibly a shift + middle click to pan. ![]() ![]() ![]() ![]() ![]() ![]() This is a great wallpaper to use if you want to go into an epileptic fit every time you sit down in front of your laptop, which I guess is a better option than watching Naruto.
|
|
You're not old until the past seems more fun than the future.
|
Yeah, I knew that. Nice to hear that you're starting to get things done.
Whatever you do, make sure you make ScmDraft accept EUDs in the text trigger editor. Because this is currently preventing some maps from being produced as you can't mass create EUD triggers. Next on the list should be all the minor fixes which can be done in a couple of minutes. With all these done you will have added a considerable portion of user-friendlyness. The last priority should be bugs. Get ScmDraft to be as stable and clean as possible. If then is still time left, just go for what looks reasonable and doable. Godspeed. |
|
You're not old until the past seems more fun than the future.
|
Well if you want it quantitized maybe everything that can be done in under half an hour.
Looked through the first page (so there are probably more), this is what I got and what I'd assume fits this category. I might be wrong with one point or another, as I don't know your code.
Maybe I have another bug (crash on certain map). I'm testing right now. And I hope you realize the potential that text based EUDs offer. You have to trust my opinion as an expert mapper on this. Text-EUDs are more important than ANY bugfix (for the mapping community). You must not sacrifice it to for getting ScmDraft bug-free. Although I understand that from your programmer's point of view bugs are priority 1. This post was edited 2 times, last edit by NudeRaider: Apr 12 2009, 11:11 am. |
|
You're not old until the past seems more fun than the future.
|
Well of course deaths too, but that's obvious.
EDIT: Preliminary bugreport: Stacked map revealers (via the stacking option of ScmD) for multiple players seem to cause the crash mentioned above. Removed them and it's stable for like 4 hours now. Testing with a fresh map to confirm. Stand by... This post was edited 1 time, last edit by NudeRaider: Apr 12 2009, 3:01 pm. |
|
お や す み
|
I mentioned earlier about how starforge handles triggers, via a config file, which you can switch between numbers/text. Deaths is really the only important one, as it's commonplace. The leaderboard for kills can be used to display most addresses after the kill table.
![]() ![]() ![]() ![]() ![]() ![]() This is a great wallpaper to use if you want to go into an epileptic fit every time you sit down in front of your laptop, which I guess is a better option than watching Naruto.
|
|
Wouldn't just one of them be enough then, if it can read all memory? (for the EUDs)
Preliminary bugreport: Stacked map revealers (via the stacking option of ScmD) for multiple players seem to cause the crash mentioned above. Removed them and it's stable for like 4 hours now. Testing with a fresh map to confirm. Stand by... <- A fix which isn't public prevents a very seldom crash with scanner sweeps. DO you have any? EDIT: - Sometimes when I validate in textual editor and save all the unnamed trings move up a number (switch 06 -> switch 07) <- Are you using the latest version? (IE the one only linked in the latest news on my site) - When editing properties of a group of units you can select which of those you want to be affected. Make this selection carry over to the selection (red circles) in the editor (Unit Layer) <- this has been possible for many years. This post was edited 3 times, last edit by NudeRaider: Apr 12 2009, 6:59 pm. Reason given: merged posts ![]() ![]() ![]() ![]() ![]() ![]() |
|
You're not old until the past seems more fun than the future.
|
No, I'm afraid not. Let me show you:
Here's a small group of units selected: ![]() Now I open the unit properties dialog: ![]() And deselect the units: ![]() But as you can see they are still selected (red/yellow circles around the units). And they are still after closing the properties dialog. However this has no priority, as you can delete them from the dialog, which is enough in most cases. About my bug report... I'm not sure if the map revealers are the cause. My tests are inconsistent right now. I'll post more if I can say something definite. The map *had* scanner sweeps. We tested that earlier, remember? But in the current version of this map there are no scanner sweeps anymore and I'm afraid I have deleted your bugfix version you sent me back then. |