Page 1 of 1

Listary build number change (not an update)

Posted: Fri Aug 06, 2010 10:24 am
by webfork
Ours: 2.00 (Build 190) http://www.portablefreeware.com/index.php?id=1680
Theirs: 2.00 (Build 169) http://www.listary.com/download.html

The last update was June 20, so I'm guessing that's just a typo. Unfortunately, updating the main entry (to avoid confusion) put it back on the front page, even though its not really a software update.

Re: Listary build number change (not an update)

Posted: Fri Aug 06, 2010 10:37 am
by joby_toss
Changelog:
  • · New: Edit text anywhere with your favorite text editor
    · New: Hot key support for commands
    · New: Hot key support for favorites
    · New: Show icons for desktop
    · New: Show icons for jump lists in Windows 7
    · New: New commands
    · New: Add Free Commander support
    · Improved: Icon position
    · Improved: Window position while searching jump lists
    · Improved: Tool tip flicker
    · Fixed: GDI resource leak in certain circumstances
    · Fixed: Crash when click on the last empty item
    · Fixed: Halt if press Win + Q in a list
    · Fixed: A typo in Options
    · Fixed: Some items in "Add Command" menu are grey in Pro version
    · Fixed: Crash IE8 when close tabs with DEP on
I now have a very good reason to use it, as FC is my main files browser!
Thank you!

Re: Listary build number change (not an update)

Posted: Fri Aug 06, 2010 6:52 pm
by I am Baas
Read the thread after updating the DB entry... :o

Should we post new builds to this forum instead?

Re: Listary build number change (not an update)

Posted: Sat Aug 07, 2010 12:06 am
by guinness
I was confused to where you were getting the build number, but now I see the website doesn't correspond to the version in the ZIP file.
It a tricky question because the developer should ideally update their main site as well, so maybe Listary should be updated if the build number is different to the DB entry.

Re: Listary build number change (not an update)

Posted: Sat Aug 07, 2010 6:36 am
by webfork
guinness wrote:It a tricky question because the developer should ideally update their main site as well, so maybe Listary should be updated if the build number is different to the DB entry.
Ohhhhh... wow that's annoying.

In this case I'd go with the smaller number on our end just so that users won't try to upgrade to a lower version.

Listary

Posted: Thu Mar 28, 2013 9:06 pm
by I am Baas

Re: Listary

Posted: Fri Mar 29, 2013 10:33 am
by Checker
Thanks ... and updated :wink: