SDLPoP v1.17 release
SDLPoP v1.17 release
I think there should be a separate thread for releases, so here it is...
And here is the Release Candidate of SDLPoP v1.17. (Windows binaries+source, as usual.)
And here is the Release Candidate of SDLPoP v1.17. (Windows binaries+source, as usual.)
- Attachments
-
- SDLPoP_v1.17RC.zip
- (4.71 MiB) Downloaded 417 times
Re: SDLPoP releases
Why not one thread per release.David wrote:I think there should be a separate thread for releases, so here it is...
Then the last release isn't on page 10 and comments in the thread are related to a particular release.
The last release was more than a year ago, and a dozen extra threads shouldn't be a problem either.
Falcury, replay recording should probably auto-end when the prince enters the princess room.David wrote:And here is the Release Candidate of SDLPoP v1.17. (Windows binaries+source, as usual.)
Also, in doc/Readme.txt it says "* Ctrl-J: joystick mode (implemented by segrax) / gamepad mode (implemented by Norbert)".
These "implemented by" texts can be removed. Similar text is already included elsewhere in the file.
Re: SDLPoP releases
OK, on it!Norbert wrote:Falcury, replay recording should probably auto-end when the prince enters the princess room.
Re: SDLPoP releases
By the way, what is the princess room is something that various mods customize.
It is something both CusPop and apoplexy can modify. Both the level and the room.
I didn't check, but it may be the only thing apoplexy can modify but SDLPoP can not.
It is something both CusPop and apoplexy can modify. Both the level and the room.
I didn't check, but it may be the only thing apoplexy can modify but SDLPoP can not.
Re: SDLPoP releases
In fact, SDLPoP can't modify most special events (yet)... the level 3 checkpoint and skeleton wake-up event, the level 4 mirror appearance (etc.) are other examples.Norbert wrote:By the way, what is the princess room is something that various mods customize.
It is something both CusPop and apoplexy can modify. Both the level and the room.
I didn't check, but it may be the only thing apoplexy can modify but SDLPoP can not.
Well, you could change the hard-coded values in the source code and recompile, of course... But I think you meant being able to modify the behavior without recompiling, right?
Done, among other things:Norbert wrote:Falcury, replay recording should probably auto-end when the prince enters the princess room.
viewtopic.php?f=126&t=3925&p=20578#p20578
Re: SDLPoP releases
Falcury wrote:But I think you meant being able to modify the behavior without recompiling, right?
Re: SDLPoP releases
Renamed the topic from "SDLPoP releases" to "SDLPoP v1.17 release".Norbert wrote: Why not one thread per release.
Then the last release isn't on page 10 and comments in the thread are related to a particular release.
The last release was more than a year ago, and a dozen extra threads shouldn't be a problem either.
Re: SDLPoP v1.17 release
Falcury, if David doesn't get to it this weekend, maybe you could publish RC2?
Re: SDLPoP v1.17 release
I would do it myself, but I'm on GNU/Linux and don't have everything properly set up to compile and link an SDLPoP executable for Windows. I'd have to look into cross-compiling it or configure Dev-C++ or something similar via Wine. Since you are actively developing SDLPoP on a Windows platform, it's probably almost no work for you at all. We could wait for David, but he's only here around Saturday evening/Sunday morning, which is almost a week away from now. Then we'd have RC2 available for testing; testing takes time. Yet another week would pass, and then 1.17 would be released... maybe. There are 121 entries for 1.17 in the changelog, and the previous release was 13 months ago. I don't think 1.17 needs to be flawless. If there's a bug, 1.18(*) can be released the next day with a bug fix. Currently, end users are no longer in the loop (RERO context). At least not the non-developers, unless they happen to have found this thread. SDLPoP 1.16 is one of the packages that's being downloaded the most from popot.org. Probably a big chunk of those downloads are from me/us, but still. What I'm trying to convey is my belief that end users are on social media and general websites, not on this forum or on GitHub. There are billions of potential users out there. I think with more frequent releases, users may be more inclined to check back for news and test/use new features. More releases could mean more 'press', more Tweets, more opportunities to reach people. I also think the more time between releases, the more 'afraid' developers may become to release anything, because missing a bug becomes a much bigger deal. The polishing may never end. How about a monthly release cycle: simply check the changelog and if there were any changes, release a new version. I have always created and included a GNU/Linux executable in the packages, and I don't mind adding them to popot.org once a month. Just some thoughts.Norbert wrote:Falcury, if David doesn't get to it this weekend, maybe you could publish RC2?
(*) Yes, 1.17.1 would make more sense, but I'm trying to make a point.
Re: SDLPoP v1.17 release
OK, here is a new release candidate for version 1.17.Norbert wrote:Falcury, if David doesn't get to it this weekend, maybe you could publish RC2?
The updated changelist:
Spoiler: show
The first one has the gears icon, the other one (with "_alticon" added to the filename) has the alternate icon.
We could handle the remaining pull request by segrax (providing MSVC compatibility for the replay code) after the 1.17 release, I think.
- Attachments
-
- SDLPoP_v1.17RC2.zip
- (4.64 MiB) Downloaded 433 times
-
- SDLPoP_v1.17RC2_alticon.zip
- (4.64 MiB) Downloaded 402 times
Re: SDLPoP v1.17 release
The following doesn't need to be in 1.17, just some suggestions.Falcury wrote:OK, here is a new release candidate for version 1.17.
fread() is currently used without checking the return value.
This is not necessarily a problem, but gcc complains about it.
A workaround is to replace fread calls with a custom function:
Code: Select all
int cfread (void *ptr, size_t size, size_t nmemb, FILE *stream)
{
return (fread (ptr, size * nmemb, 1, stream));
}
chdir() is currently used without checking the return value.
Something like this could be used...
Code: Select all
if (chdir(exe_dir) == -1)
{
fprintf (stderr, "chdir failed: %s\n", strerror(errno));
}
fprintf(stderr, error_message);
Gives a warning that disappears when this is used instead:
fprintf(stderr, "%s", error_message);
I noticed my level 1 replay of David's mod plays without adding the mod.
This surprised me. The savestate includes the whole level, or?
Re: SDLPoP v1.17 release
All right, noted!Norbert wrote:The following doesn't need to be in 1.17, just some suggestions.
Yes, the savestate includes the level. Only the level that is loaded at the start of the replay, though.Norbert wrote:I noticed my level 1 replay of David's mod plays without adding the mod.
This surprised me. The savestate includes the whole level, or?
It would of course be possible to embed more levels for multi-level replays (as needed). Perhaps we should add that to the format at some point.
Or, maybe there should just be some kind of warning, if a custom asset was expected but could not be found.
Re: SDLPoP v1.17 release
So, after merging the new changelog (and replacing "February ??" with the actual date), can I now make a final release?
Might be useful if someone wants to see the solution of a particular level/room.
(Or to skip slow/boring parts... )
So true...Norbert wrote: I also think the more time between releases, the more 'afraid' developers may become to release anything, because missing a bug becomes a much bigger deal. The polishing may never end.
That's interesting!Falcury wrote: While viewing a replay, you can press F to skip forward to the next room, or Shift+F to skip to the next level.
Might be useful if someone wants to see the solution of a particular level/room.
(Or to skip slow/boring parts... )
Did you too notice that SDLPoP version numbers became in-sync with year numbers?Norbert wrote: (*) Yes, 1.17.1 would make more sense, but I'm trying to make a point.
Re: SDLPoP v1.17 release
Yeah, go for it!David wrote:So, after merging the new changelog (and replacing "February ??" with the actual date), can I now make a final release?
Then, if you want to keep using the gears icon, could you close the alternative icon pull request?David wrote:Added the gears icon: https://github.com/NagyD/SDLPoP/commit/ ... 49d4b5450d
I'm not fully sure if this will be the final icon, though...
The decision seems to be 'in limbo'...
Re: SDLPoP v1.17 release
Okay, here it is.Falcury wrote:Yeah, go for it!
- Attachments
-
- SDLPoP_v1.17_release.zip
- (4.72 MiB) Downloaded 478 times