Where's history for 64-beta?

[Raf]

There is a file with the history of changes. Which version is it for: x32 or x64? Where is the file for x64? Im checking it every 2-3 days

[admin]

Currently History.txt is only for x32, and the x64 history is only available in the forum's beta release thread: viewtopic.php?t=28739 Most of it is identical to the recent x32 history in History.txt.

I'm still thinking about the best way to merge the two.

[Raf]

I can write a parser that will analyze the dates in two files starting from the launch date of the x64 beta (2025-07-07) and combine them into one file in chronological order:

Code: Select all

// Example
v27.10.0003 - 2025-07-15 13:36
    * Configuration | Information | File Info Tips & Hover Box | Show file info tips | 
      Extra fields: v27.00.0805 - 2025-06-25 17:50 added:
        The Opens With line now mentions the version number if available.
      This is now bound to a new tweak:
        InfoTipOpensWithAppendVersion=1
    ! Some minor bug fixes.
v27.90.0003 - 2025-07-12 13:34
    + Background File Operations: If a background job fails due to an XYcopy error, you 
      now can view the error message by right-clicking the failed job in the Background 
      Jobs dialog box and selecting "Details..." from the context menu.
    + Configuration Dialog: Now the bitness is shown in the title bar.
v27.90.0002 - 2025-07-11 13:38
    ! DOS Commands via Address Bar, e.g. "!set", didn't work correctly. Fixed.
    ! SC sync: Error 9 could occur under rare circumstances. Fixed.
v27.10.0001 - 2025-07-11 13:38
    ! SC sync: Error 9 could occur under rare circumstances. Fixed.
v27.90.0001 - 2025-07-10 15:18
    > The version number has been increased to 27.90.0001. Up to 9,998 revisions are 
      possible before the 64-bit version is officially released as v28.00.0000. That 
      should be sufficient.
      The space from v27.10.0000 to v27.80.9999 is reserved for updates, mostly bug fixes, 
      to the 32-bit version.
    ! SC base64encode: Didn't work. Fixed.
    ! TB Fix: VERSION info block 'FileVersion' string was padding the Revision part to 5 
      characters rather than 4 to match VBx.
    * XYcopy: Updated to 2.10.0278.
v27.10.0000 - 2025-07-09 19:00
    = NEW OFFICIAL RELEASE. Main developments since last release:
  +++ This is a BIG maintenance release. Numerous minor fixes and improvements have been 
      made since the last major release.
  +++ This is also the last 32-bit version of XYplorer. The next one will be 64-bit.

.......... XYplorer ver 27.00 .....................................................
v27.00.0906 - 2025-07-07 11:11
    > This is the first version of XYplorer's 64-bit edition (created with twinBASIC) that 
      is published in the beta channel of the user forum, in its own 64-bit beta thread.
    > The old 32-bit edition will not be discontinued entirely, but will receive bug fix 
      releases as necessary.
    + Help | About XYplorer: Now shows the twinBASIC version used to create it.
    * Executable Names: The "TB" suffix was removed from XYplorer.exe and XYcopy.exe.
    * XYcopy: Updated to 2.10.0277.
    Most users don't need to know this, but here are some points about the 64-bit 
    installation to keep you up-to-date:
    > The XY64 installer filename now begins with XYplorer64, for example:
      XYplorer64_27.00_Install.exe
    > The XY64 installer places the application into "C:\Program Files" now, not 
      "C:\Program Files (x86)" anymore.
    > The Help file is now called XYplorer64.chm.
    > To enable a smooth upgrade the 32-bit and 64-bit versions use same default app data 
      folder: C:\Users\<USERNAME>\AppData\Roaming\XYplorer\ (aka %APPDATA%XYplorer\)
    > This means that if you use both the 32-bit and 64-bit versions of the app with the 
      default app data settings, they will share the same app data folder. This is 
      probably not a good idea unless you know what you're doing.
    > This also means that if you uninstall either version, 32-bit or 64-bit, using 
      Uninstall.exe (directly or via Shell "Programs and Features"), that shared app data 
      folder will be nuked.
v27.00.0915 - 2025-07-09 11:04
    * MLS: Internally updated to version 8.196.
      > TRANSLATORS: Please wait until Reference_8.196.lng is uploaded.
        You will be notified if you have subscribed to this thread:
        https://www.xyplorer.com/xyfc/viewtopic.php?f=12&t=9648
    * Updated the help file.
v27.00.0905 - 2025-07-07 10:11
    + New Variable <xybitness>: Returns "32-bit" or "64-bit" depending on the bitness of 
      the main executable (XYplorer.exe).
        echo <xybitness>; //"32-bit" in the VB version, "64-bit" in the TB version        
    * Updated the help file.
v27.00.0901 - 2025-07-06 12:15
    + Tools | Customize Keyboard Shortcuts...: The Jump button now obeys to F3.

Despite the mix, x64 and x32 have different versions, so everyone can quickly find out which version the Changelog was for. And when the x64 version is released, the History will continue only for the x64 version and there will be no mix of bitness. The History will continue. Updates will continue. But the link to the History.txt will remain the same.

[admin]

Great, sounds perfect to me, thanks!

[admin]

I uploaded the complete TB history as TXT file:
https://www.xyplorer.com/download/HistoryTB.txt

Note that I added "(x64)" to the entries where the version number was still below 27.90.

[Raf]

I uploaded the complete TB history as TXT file:
https://www.xyplorer.com/download/HistoryTB.txt

Thank you. Here's merged history starting from

Code: Select all

v27.00.0700 - 2025-06-12 19:00
    = MAINTENANCE RELEASE.
  +++ Minor bug fixes and enhancements.

SortedHistory.txt

(48.49 KiB) Downloaded 182 times

I made the sorting tool public so that it can be used for merging various changelogs: https://github.com/JoyHak/ChangeLogSorter

[admin]

Thanks!

Looks like my "(x64)" additions to HistoryTB.txt are missing?

[Raf]

I've accidentally used old x64 file
Fixed:

SortedHistory2.txt

(57.3 KiB) Downloaded 227 times

[admin]

[Garonne]

I think, as long as we have both additions, we should keep histories separate. History.txt and History64.txt... if we have a History64 at all. For me, the Forum is fine, too.

Once XY64 finally releases, both Histories could (and maybe should) merge. Unless x32 (currently 27.10.0900) reaches x64 version numbers (starting 27.90.0000, which isn't intended if I got that right) there shouldn't be any problem.