Since there is no minor version change and only build changes and there are absolutely no published changes for this build other than the obvious giveaway date change installation authorisation. It leads me to believe that this will not fix any bugs if anyones found any and reported them and is solely a build incrememnt depicting a new giveaway build was created to be wrapped in setup.exe/gcd protective wrapper. Accordingly I see no reason to install 1.61.60 over 1.61.56 and probably not over any other giveaway 1.61.* build as the What's New page has not even changed since 1.60! The page does acknowledge version 1.61 download but mentions nothing about anything new or fixed within it. My deduction from all this is no actual development is being done in the 1.61 minor version branch and that ALL significant development is being done in the 2.00.81.0 and above Alpha builds which kinda makes sense but would be nice to be made clear during the giveaways so participants know if a giveaway is NEW or just refreshed new build for the different giveaway date. I do recomend the program for those that have a need for a more acomplished multi-programming language editor, it has served me well and I only resort to using other niche programers editors for specific file types or operations that no one has ever quite mastereed e.g. running hippoedit always without elevated rights but certain file ediitng like hosts file that needs to be written with elevated rights I use a little multi-tabbed editor configured to only ever launch as an administrator which does not parse or launch HTML in any way to try and render it so will not present any security risk from specially crafted html or scripts they my contain.

There is one "bug"/omission with giveaway builds. They are ONLY 32bit builds so IF you install them on a 64bit system mostly they will work adequatly but one feature WILL NOT WORK and that is the shell extension for Open WIth HippoEdit context menu entry as Windows shell cannot launch a 32bit shell extension DLL from a 64bit shell.

The solution for us is a little bit convuluted but doable for anyone compitent with 7zip and windows explorer in that you install this protected 32bit giveaway build on your 64bit machine as normal and then download the 64bit installer from HippoEDIT website download page. DO NOT INSTALL IT. Open the installer in 7zip as an archive and extract the 64bit file ShellReg.dll and replace the 32bit ShellReg.dll in the installed (x86) folder installation of this. This will allow the shell extension "Open With HippoEDIT" to show up and function as expected on a 32bit giveway build installed on a 64bit edition of windows. Alex the developer could easily make the installer install the 32bit ShellReg.dll on 32bit windows platforms and the 64bit ShellReg.dll when installing on a 64bit windows platform. One would hope that IF he does this in the future he'll let us know to save us having to do the work for him;-)

TK  –  3 years ago  –  Você achou esse comentário útil? sim | não (+18)

Traduzir

I have an old version installed 1.61.55, in case I want to update to new offered ver 1.61.60, should I uninstall the old one and then install the current?

Rafiq  –  3 years ago  –  Você achou esse comentário útil? sim | não (+7)

Traduzir

Rafiq, All indications are that 1.61.60 build is the same functional code as 1.61.55 and the build just reflects a new giveaway licensing build refreshed for this particular giveaway date. So it is unlikely to be worth your time installing the new giveaway build over the currently released build number which is 1.61.53 let alone any intermediate special giveaway licencing builds. If you simply must have the latest build regardless then you can safely install it over the previous builds :)

Rafiq, All indications are that 1.61.60 build is the same functional code as 1.61.55 and the build just reflects a new giveaway licensing build refreshed for this particular giveaway date. So it is unlikely to be worth your time installing the new giveaway build over the currently released build number which is 1.61.53 let alone any intermediate special giveaway licencing builds. If you simply must have the latest build regardless then you can safely install it over the previous builds :)
Save | Cancel

TK  –  3 years ago  –  Você achou esse comentário útil? sim | não (+11)

Traduzir

My experience with this version was not great. I tried loading a 240M XML file. It loaded it. Scrolling through it was fairly decent when compared with Notepad++ and Code Writer (a previous GiveAwayOfTheDay offer), but it crashes while scrolling. I am on an I7 16MB SSD computer. So, I know my computer has plenty of resources to handle it.

indyman777  –  3 years ago  –  Você achou esse comentário útil? sim | não (+3)

Traduzir

Hi indyman777, I will be happy to check the issue, if I can recreate it on my side. I also answered your crash report. Normally HippoEDIT shall handle such files easily, but may happen that comes to some extreme cases (like single-line file, wrapped, or with collapsed nodes) which are not well tested and may lead to issues. For the single-line file of size 240M you will need, around 240*2+20% of continuous memory, which is not always available for 32bit processes. With 64bit it is mostly always fine. But in the end, the only way to find a reason - debug or see the detailed dump.

Hi indyman777, I will be happy to check the issue, if I can recreate it on my side. I also answered your crash report. Normally HippoEDIT shall handle such files easily, but may happen that comes to some extreme cases (like single-line file, wrapped, or with collapsed nodes) which are not well tested and may lead to issues. For the single-line file of size 240M you will need, around 240*2+20% of continuous memory, which is not always available for 32bit processes. With 64bit it is mostly always fine. But in the end, the only way to find a reason - debug or see the detailed dump.
Save | Cancel

Alex from HippoEDIT  –  3 years ago  –  Você achou esse comentário útil? sim | não (+7)

Traduzir

indyman777, interesting, did it ONLY happen on that one 240Mbyte XML file the once or was it repeatable and it always crashed at the same approximate point in the file and it made no difference if the machine was freshly rebooted or not?
As windows is NOT bullet proof and has many limited resources that can be depleted and cause a crash even if you have dozens of CPU cores and gigabytes of RAM to spare.
Could you provide a non-confidential file that reproduces the problem so the developer could reproduce the bug and track down the cause or at least test it against the code base for 2.00 that he's more engrossed in so he does not carry over any parsing bugs or resource leaks from the 1.61 codebase to the new 2.00 codebase? Or go to the products forum and test out the current 2.00 alpha build to see if it exhibits the same instability with the same file https://forum.hippoedit.com/alpha-version-test-(major)/hippoedit-2-00/

indyman777, interesting, did it ONLY happen on that one 240Mbyte XML file the once or was it repeatable and it always crashed at the same approximate point in the file and it made no difference if the machine was freshly rebooted or not? As windows is NOT bullet proof and has many limited resources that can be depleted and cause a crash even if you have dozens of CPU cores and gigabytes of RAM to spare. Could you provide a non-confidential file that reproduces the problem so the developer could reproduce the bug and track down the cause or at least test it against the code base for 2.00 that he's more engrossed in so he does not carry over any parsing bugs or resource leaks from the 1.61 codebase to the new 2.00 codebase? Or go to the products forum and test out the current 2.00 alpha build to see if it exhibits the same instability with the same file https://forum.hippoedit.com/alpha-version-test-(major)/hippoedit-2-00/
Save | Cancel

TK  –  3 years ago  –  Você achou esse comentário útil? sim | não (+7)

Traduzir