-
I'm not removing release that has been available for a long time. People will anyway load it from dozens of other services. And we get even more bugs that we don't have latest release available.
2009-12-17 18:01:06 UTC in WinMerge
-
As I said I know the problem perfectly well after been thinking about it for years.
The problem is in Windows API not in our code and there is no solution we can do without changing behavior of WinMerge. And we don't want that behavior change. The path check is very useful and lots of users want it. If user doesn't want that checking one can disable it.
Argue as much as you wish I'm not...
2009-12-17 17:57:03 UTC in WinMerge
-
I understand the problem perfectly well. I've tried several approaches to solve it.
Why do you think we have the option to disable checking paths?.
2009-12-16 22:31:13 UTC in WinMerge
-
Sure, just rebuilding magically fixes things.
What I need to do is to setup the proper Wix environment and fix release script to build MSI installer.
2009-12-16 22:27:58 UTC in WinMerge
-
> user first has to select the path left, right before it will be
> checked as valid.
Why? One very nice feature is that WinMerge tells when you have *typed* correct path. Why check path which has been selected before as it is most likely valid path already.
2009-12-16 20:26:29 UTC in WinMerge
-
Yeah, there are some such weird artifacts.
Problem is simply mapping lots of lines to small amount of pixels.
2009-12-16 20:16:33 UTC in WinMerge
-
> Installing the Microsoft Visual C++ 2008 SP1 Redistributable
> Package corrects this error.
*That* would be weird solution. There is nothing in WinMerge requiring VS2008 runtimes. You can check that with Dependency Walker. Or if there really is then something went very wrong when building that release...
Problem is side by side assemblies and the solution is to use MSI installer to...
2009-12-16 20:13:39 UTC in WinMerge
-
The problem is side by side assemblies:
http://msdn.microsoft.com/en-us/library/aa376307(VS.85).aspx
as was already analyzed elsewhere (forums, other reports, I can't remember).
The fix is to use MSI installer instead of InnoSetup. And we have that MSI setup already in source control. But setting up environment and adding it to the release script takes a time and I didn't have that time for...
2009-12-16 20:08:22 UTC in WinMerge
-
WTF is this submitter? One more way to submit anonymous items and work around our limitation to not allow anonymous items?
We really don't need any anonymous items hence I'm just closing this. If people don't bother to even spend time registering but demand developers to put time to something then it certainly is not worth developers time.
Closing as rejected.
2009-11-29 17:46:32 UTC in WinMerge
-
WinMerge setups only one filetype handler and that is for .winmerge files which are WinMerge "project" files. Perhaps you have accidentally sometimes selected to open HTML file with WinMerge and selected that "use this program to always open these files" (or whatever the option name was)? I have no idea how else WinMerge could be involved in normal shellexec.
2009-11-29 17:34:43 UTC in WinMerge
