+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Click button "check for update" on a nighty build release.
> What is the expected output? What do you see instead?
ThisA dialog box appears : "No news version available" !
> What version of the product are you using? On what operating system?
All nighty Build of JPEXS. Win7x64
> Please provide any additional information below. Attach the file you have problem with
if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
I think this is normal because the nighty build version number is generated with a
Yes, this is normal. The server can't determine which random version number is bigger
unless it stores all nightly versions. But i think it is unnecessary.
Why do you need this feature? Nightly builds are only for testing.
Actually, the server has stored information about all uploaded nightly builds so it may be
When you run a nightly build now, update check should work for all newer official releases
(=no nightly builds).
Maybe we can also implement a checkbox to check for nightly builds too.
But it won't surely display any changeslog as it is stored only in Mercurial repository.
Is this really neccessary?
I think nightly update check could be useful. And another thing is to make real auto
updater - it shouldn't lead to download page but download new version in background, close
FFDec and auto extract in directory from it was launched.
I am not really fan of the autoupdater idea. I was thinking about it earlier, but dropped
I know it could be usefull and quick for users, but... ehm... I don't like idea that users
won't visit my webpages anymore. Some users will download the program elsewhere and won't
ever notice how original webpages look like. I would also like to put something more on
the webpages... for example polls or announcements. I cannot do this without users
visiting the webpages.
I know it is annoying to visit webpages and install it everytime, but please consider it
as small tax for having the software totally free. Please understand us. Thanks.
Ok, maybe then make a nightly update channel (for nightly's only) with auto updater and
stable update channel with old (current) updater because nightly's comes very often and
yes it's a little annoying to visit download page several times a day?