nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
Code Issues Projects Releases Wiki Activity
pre-0.83
putty-source/windows/pageant.rc

96 lines
3.3 KiB
Plaintext
Raw Permalink Normal View History

Pull out the common compiler-specific workarounds and so on from individual resource files into windows/rcstuff.h. [originally from svn r5405]
2005-02-26 17:43:47 +00:00
/*
* Windows resources for Pageant.
*/
Alexey Savelyev's mkfiles.pl patch to support lcc-win32. This has caused a small amount of extra inconvenience at the tops of .rc files, but it's been positive overall since lcc has managed to point out some pedantic errors (typically static/extern mismatches between function prototypes and definitions) which everything else missed. [originally from svn r3744]
2004-01-20 20:35:27 +00:00
Pull out the common compiler-specific workarounds and so on from individual resource files into windows/rcstuff.h. [originally from svn r5405]
2005-02-26 17:43:47 +00:00
#include "rcstuff.h"
Add weird XML manifest resources, to enable WinXP skins to work within PuTTY's dialog boxen. [originally from svn r1530]
2002-01-08 09:32:50 +00:00
`win-versioninfo': all builds of all Windows binaries now contain a VERSIONINFO resource. The versioning scheme is described in windows/version.rc2. Some .rc files are now #included in others. In order to keep MSVC project files working, these have been renamed to .rc2; there may exist a better solution. (This checkin also includes the documentation tweak missing from r6367.) Testing performed: - MinGW (cross-compiler): works - VC nmake: works (tested with VC6) - VC project files: builds with VERSIONINFO resource (no VER variable though) - Borland: an old version of this patch was tested with it and more or less worked, except that some of the VERSIONINFO strings were apparently not terminated properly. Not attempted to work around this. - LCC: not tested. Some fixes are in there from the last time we tried this, but then the build ultimately failed and I haven't tried this since that was fixed. - Dev-C++: untested. (Haven't done anything special.) - Unix Gtk/autoconf Makefiles work as before. [originally from svn r6374] [r6367 == f86ad059db0c5225b29da5f8a138d7dce4322f22] [this svn revision also touched putty-wishlist]
2005-10-04 14:13:28 +00:00
#define APPNAME "Pageant"
#define APPDESC "PuTTY SSH authentication agent"
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
#include "pageant-rc.h"
Rename most of the platform source files. This gets rid of all those annoying 'win', 'ux' and 'gtk' prefixes which made filenames annoying to type and to tab-complete. Also, as with my other recent renaming sprees, I've taken the opportunity to expand and clarify some of the names so that they're not such cryptic abbreviations.
2021-04-23 05:19:05 +00:00
#include "help.rc2"
Stop looking for putty.chm alongside the binary. With this change, we stop expecting to find putty.chm alongside the executable file. That was a security hazard comparable to DLL hijacking, because of the risk that a malicious CHM file could be dropped into the same directory as putty.exe (e.g. if someone ran PuTTY from their browser's download dir).. Instead, the standalone putty.exe (and other binaries needing help) embed the proper CHM file within themselves, as a Windows resource, and if called on to display the help then they write the file out to a temporary location. This has the advantage that if you download and run the standalone putty.exe then you actually _get_ help, which previously didn't happen! The versions of the binaries in the installer don't each contain a copy of the help file; that would be extravagant. Instead, the installer itself writes a registry entry pointing at the proper help file, and the executables will look there. Another effect of this commit is that I've withdrawn support for the older .HLP format completely. It's now entirely outdated, and supporting it through this security fix would have been a huge pain.
2019-01-26 20:26:09 +00:00
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
IDI_MAINICON ICON "pageant.ico"
IDI_TRAYICON ICON "pageants.ico"
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
IDD_LOAD_PASSPHRASE DIALOG DISCARDABLE 0, 0, 140, 60
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
Polish up passphrase prompts for key decryption. Now Windows Pageant has two clearly distinct dialog boxes for requesting a key passphrase: one to use synchronously when the user has just used the 'Add Key' GUI action, and one to use asynchronously in response to an agent client's attempt to use a key that was loaded encrypted. Also fixed the wording in the asynchronous box: there were two copies of the 'enter passphrase' instruction, one from the dialog definition in pageant.rc file and one from the cross-platform pageant.c. Now pageant.c doesn't format a whole user-facing message any more: it leaves that to the platform front end to do it the way it wants. I've also added a call to SetForegroundWindow, to try to get the passphrase prompt into the foreground. In my experience this doesn't actually get it the keyboard focus, which I think is deliberate on Windows's part and there's nothing I can do about it. But at least the user should _see_ that the prompt is there, so they can focus it themself.
2021-04-02 09:49:18 +00:00
CAPTION "Pageant: Loading Encrypted Key"
From Greg Prosser: Apparently using "MS Shell Dlg" instead of "MS Sans Serif" in resource files interoperates better with WinXP (enabling font smoothing and improving display of password boxes). I've verified that it's harmless on Win95. [originally from svn r2329]
2002-12-15 12:44:21 +00:00
FONT 8, "MS Shell Dlg"
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
BEGIN
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
CTEXT "Enter passphrase to load key", IDC_PASSPHRASE_STATIC1, 10, 6, 120, 8
CTEXT "", IDC_PASSPHRASE_FINGERPRINT, 10, 16, 120, 8
EDITTEXT IDC_PASSPHRASE_EDITBOX, 10, 26, 120, 12,
ES_PASSWORD | ES_AUTOHSCROLL
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
DEFPUSHBUTTON "O&K", IDOK, 20, 42, 40, 14
PUSHBUTTON "&Cancel", IDCANCEL, 80, 42, 40, 14
END
winpgnt: say 'click to focus' in async passphrase prompt. I continue to believe that there's nothing I can (or should) do about the fact that on Windows, Pageant's async passphrase prompt dialog box doesn't automatically get the input focus when it pops up in response to a request received via invisible IPC. However, one thing I can do is add some text to the box that _warns_ people about it, so that at least there's some kind of suggestion that you should get into the habit of clicking on the passphrase prompt before typing your passphrase into it. (I would be less concerned about all of this if it weren't for the fact that focus is surprisingly non-obvious on Windows 10, at least on the machine I have here. When the window doesn't have focus, the title bar has the same background colour, and only the text is fainter. And perhaps more confusingly, the cursor in the edit box still flashes! That fooled _me_ a few times to begin with.)
2021-04-22 18:47:13 +00:00
IDD_ONDEMAND_PASSPHRASE DIALOG DISCARDABLE 0, 0, 250, 78
Polish up passphrase prompts for key decryption. Now Windows Pageant has two clearly distinct dialog boxes for requesting a key passphrase: one to use synchronously when the user has just used the 'Add Key' GUI action, and one to use asynchronously in response to an agent client's attempt to use a key that was loaded encrypted. Also fixed the wording in the asynchronous box: there were two copies of the 'enter passphrase' instruction, one from the dialog definition in pageant.rc file and one from the cross-platform pageant.c. Now pageant.c doesn't format a whole user-facing message any more: it leaves that to the platform front end to do it the way it wants. I've also added a call to SetForegroundWindow, to try to get the passphrase prompt into the foreground. In my experience this doesn't actually get it the keyboard focus, which I think is deliberate on Windows's part and there's nothing I can do about it. But at least the user should _see_ that the prompt is there, so they can focus it themself.
2021-04-02 09:49:18 +00:00
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "Pageant: Decrypting Stored Key"
FONT 8, "MS Shell Dlg"
BEGIN
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
CTEXT "A client of Pageant wants to use the following encrypted key:",
IDC_PASSPHRASE_STATIC1, 10, 6, 230, 8
CTEXT "", IDC_PASSPHRASE_FINGERPRINT, 10, 16, 230, 8
winpgnt: say 'click to focus' in async passphrase prompt. I continue to believe that there's nothing I can (or should) do about the fact that on Windows, Pageant's async passphrase prompt dialog box doesn't automatically get the input focus when it pops up in response to a request received via invisible IPC. However, one thing I can do is add some text to the box that _warns_ people about it, so that at least there's some kind of suggestion that you should get into the habit of clicking on the passphrase prompt before typing your passphrase into it. (I would be less concerned about all of this if it weren't for the fact that focus is surprisingly non-obvious on Windows 10, at least on the machine I have here. When the window doesn't have focus, the title bar has the same background colour, and only the text is fainter. And perhaps more confusingly, the cursor in the edit box still flashes! That fooled _me_ a few times to begin with.)
2021-04-22 18:47:13 +00:00
CTEXT "If you intended this, click in this box to make sure it has",
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
IDC_PASSPHRASE_STATIC2, 10, 26, 230, 8
winpgnt: say 'click to focus' in async passphrase prompt. I continue to believe that there's nothing I can (or should) do about the fact that on Windows, Pageant's async passphrase prompt dialog box doesn't automatically get the input focus when it pops up in response to a request received via invisible IPC. However, one thing I can do is add some text to the box that _warns_ people about it, so that at least there's some kind of suggestion that you should get into the habit of clicking on the passphrase prompt before typing your passphrase into it. (I would be less concerned about all of this if it weren't for the fact that focus is surprisingly non-obvious on Windows 10, at least on the machine I have here. When the window doesn't have focus, the title bar has the same background colour, and only the text is fainter. And perhaps more confusingly, the cursor in the edit box still flashes! That fooled _me_ a few times to begin with.)
2021-04-22 18:47:13 +00:00
CTEXT "input focus, then enter the passphrase to decrypt the key.",
IDC_PASSPHRASE_STATIC3, 10, 34, 230, 8
EDITTEXT IDC_PASSPHRASE_EDITBOX, 10, 44, 230, 12,
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
ES_PASSWORD | ES_AUTOHSCROLL
winpgnt: add a help button to async passphrase prompt. Suggested by Jacob: if this dialog box is going to pop up _unexpectedly_ - perhaps when people have momentarily forgotten they're even running Pageant, or at least forgotten they added a key encrypted,, or maybe haven't found out yet that their IT installed it - then it could usefully come with a help button that pops up further explanation of what the dialog box means, and from which you can find your way to the rest of the help.
2021-04-22 18:58:53 +00:00
DEFPUSHBUTTON "O&K", IDOK, 45, 60, 40, 14
PUSHBUTTON "&Cancel", IDCANCEL, 105, 60, 40, 14
PUSHBUTTON "&Help", IDHELP, 165, 60, 50, 14
Polish up passphrase prompts for key decryption. Now Windows Pageant has two clearly distinct dialog boxes for requesting a key passphrase: one to use synchronously when the user has just used the 'Add Key' GUI action, and one to use asynchronously in response to an agent client's attempt to use a key that was loaded encrypted. Also fixed the wording in the asynchronous box: there were two copies of the 'enter passphrase' instruction, one from the dialog definition in pageant.rc file and one from the cross-platform pageant.c. Now pageant.c doesn't format a whole user-facing message any more: it leaves that to the platform front end to do it the way it wants. I've also added a call to SetForegroundWindow, to try to get the passphrase prompt into the foreground. In my experience this doesn't actually get it the keyboard focus, which I think is deliberate on Windows's part and there's nothing I can do about it. But at least the user should _see_ that the prompt is there, so they can focus it themself.
2021-04-02 09:49:18 +00:00
END
winpgnt: add GUI button to re-encrypt an SSH-2 key.
2021-04-04 08:42:00 +00:00
IDD_KEYLIST DIALOG DISCARDABLE 0, 0, 450, 236
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "Pageant Key List"
From Greg Prosser: Apparently using "MS Shell Dlg" instead of "MS Sans Serif" in resource files interoperates better with WinXP (enabling font smoothing and improving display of password boxes). I've verified that it's harmless on Win95. [originally from svn r2329]
2002-12-15 12:44:21 +00:00
FONT 8, "MS Shell Dlg"
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
BEGIN
windows/pageant.rc: add missing symbolic constant. The main list box in the Pageant key list window was identified by a numeric control id, even though pageant-rc.h has a nice meaningful macro name for it (and pageant.c uses that).
2022-08-01 16:32:40 +00:00
LISTBOX IDC_KEYLIST_LISTBOX, 10, 10, 420, 155,
Windows Pageant: use an owner-drawn list box for the key list. The main key list control in the Pageant window was previously an ordinary LBS_HASSTRINGS list box, with tab characters aligning the various parts of the key information into different columns. This was fragile because any mistake in the font metrics could have overflowed a tab stop and forced the text to move on to the next one. Now I've switched the list box into LBS_OWNERDRAWFIXED mode, which means that in place of a string for each list item I store a struct of my choice, and I have to draw the list-box entries myself by responding to WM_DRAWITEM. So now I'm drawing each component of the key information as a separate call to ExtTextOut (plus one TabbedTextOut to put the '(encrypted)' suffix on the end), which means that the tab stops are now guaranteed to appear where I tell them to. No functional change, for the moment: this is pure refactoring. As closely as I can tell, the appearance of the list box is pixel-for-pixel what it was before this commit. But it opens the door for two further improvements (neither one done in this commit): I can dynamically choose the tab stop locations based on querying the text metrics of the strings that will actually need to fit in the columns, and also, whatever reorganisation I need to do to make certificates fit sensibly in this list box can now be done without worrying about breaking anything terribly fragile.
2022-08-01 16:45:55 +00:00
LBS_EXTENDEDSEL | LBS_OWNERDRAWFIXED | WS_VSCROLL | WS_TABSTOP
winpgnt: add GUI button to re-encrypt an SSH-2 key.
2021-04-04 08:42:00 +00:00
PUSHBUTTON "&Add Key", IDC_KEYLIST_ADDKEY, 10, 187, 60, 14
PUSHBUTTON "Add Key (&encrypted)", IDC_KEYLIST_ADDKEY_ENC, 75, 187, 80, 14
PUSHBUTTON "Re-e&ncrypt", IDC_KEYLIST_REENCRYPT, 315, 187, 60, 14
PUSHBUTTON "&Remove", IDC_KEYLIST_REMOVE, 380, 187, 60, 14
PUSHBUTTON "&Help", IDC_KEYLIST_HELP, 10, 212, 50, 14
DEFPUSHBUTTON "&Close", IDOK, 390, 212, 50, 14
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
LTEXT "&Fingerprint type:", IDC_KEYLIST_FPTYPE_STATIC, 10, 172, 60, 8
Certificate-aware handling of key fingerprints. OpenSSH, when called on to give the fingerprint of a certified public key, will in many circumstances generate the hash of the public blob of the _underlying_ key, rather than the hash of the full certificate. I think the hash of the certificate is also potentially useful (if nothing else, it provides a way to tell apart multiple certificates on the same key). But I can also see that it's useful to be able to recognise a key as the same one 'really' (since all certificates on the same key share a private key, so they're unavoidably related). So I've dealt with this by introducing an extra pair of fingerprint types, giving the cross product of {MD5, SHA-256} x {base key only, full certificate}. You can manually select which one you want to see in some circumstances (notably PuTTYgen), and in others (such as diagnostics) both fingerprints will be emitted side by side via the new functions ssh2_double_fingerprint[_blob]. The default, following OpenSSH, is to just fingerprint the base key.
2022-08-05 17:08:59 +00:00
COMBOBOX IDC_KEYLIST_FPTYPE, 70, 170, 100, 12, CBS_DROPDOWNLIST
Added Pageant, a first-attempt PuTTY authentication agent [originally from svn r589]
2000-09-14 15:02:50 +00:00
END
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
/* Accelerators used: cl */
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
IDD_ABOUT DIALOG DISCARDABLE 140, 40, 270, 136
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "About Pageant"
From Greg Prosser: Apparently using "MS Shell Dlg" instead of "MS Sans Serif" in resource files interoperates better with WinXP (enabling font smoothing and improving display of password boxes). I've verified that it's harmless on Win95. [originally from svn r2329]
2002-12-15 12:44:21 +00:00
FONT 8, "MS Shell Dlg"
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
BEGIN
Grow PuTTYgen and Pageant About boxes. To match a2b040ee09 for PuTTY/PuTTYtel.
2019-03-18 20:32:06 +00:00
DEFPUSHBUTTON "&Close", IDOK, 216, 118, 48, 14
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
PUSHBUTTON "View &Licence", IDC_ABOUT_LICENCE, 6, 118, 70, 14
PUSHBUTTON "Visit &Web Site", IDC_ABOUT_WEBSITE, 140, 118, 70, 14
EDITTEXT IDC_ABOUT_TEXTBOX, 10, 6, 250, 110,
ES_READONLY | ES_MULTILINE | ES_CENTER, WS_EX_STATICEDGE
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
END
/* No accelerators used */
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
IDD_LICENCE DIALOG DISCARDABLE 50, 50, 326, 239
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
Fix the licence again. (Despite the copyright holders being more numerous, it still only said _I_ would not be liable rather than _everybody_ not being liable; also the resource file versions weren't up to date.) [originally from svn r1272]
2001-09-18 18:40:00 +00:00
CAPTION "PuTTY Licence"
From Greg Prosser: Apparently using "MS Shell Dlg" instead of "MS Sans Serif" in resource files interoperates better with WinXP (enabling font smoothing and improving display of password boxes). I've verified that it's harmless on Win95. [originally from svn r2329]
2002-12-15 12:44:21 +00:00
FONT 8, "MS Shell Dlg"
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
BEGIN
Grow the Windows Licence dialog. It was cutting off the last line or so, on some fairly standard Win7/Win10 installations.
2019-03-18 20:32:55 +00:00
DEFPUSHBUTTON "OK", IDOK, 148, 219, 44, 14
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
pageant.rc: make a header file of dialog/control ids. I'm tired of remembering all those fiddly magic numbers and copying them back and forth between the .rc file and the source code. I'm even more tired of having to remember that in the long string of numbers after a dialog item definition, the first one of them _isn't_ one of the position and size coordinates. I've given them all symbolic names, like they should have had all along. I think I originally didn't bother because this was such a small GUI compared to the much larger one in PuTTY proper. But it's growing!
2021-04-04 08:27:47 +00:00
EDITTEXT IDC_LICENCE_TEXTBOX, 10, 10, 306, 200,
ES_READONLY | ES_MULTILINE | ES_LEFT, WS_EX_STATICEDGE
Add the About and Licence boxes to Pageant [originally from svn r648]
2000-09-29 08:43:06 +00:00
END
Add weird XML manifest resources, to enable WinXP skins to work within PuTTY's dialog boxen. [originally from svn r1530]
2002-01-08 09:32:50 +00:00
`win-versioninfo': all builds of all Windows binaries now contain a VERSIONINFO resource. The versioning scheme is described in windows/version.rc2. Some .rc files are now #included in others. In order to keep MSVC project files working, these have been renamed to .rc2; there may exist a better solution. (This checkin also includes the documentation tweak missing from r6367.) Testing performed: - MinGW (cross-compiler): works - VC nmake: works (tested with VC6) - VC project files: builds with VERSIONINFO resource (no VER variable though) - Borland: an old version of this patch was tested with it and more or less worked, except that some of the VERSIONINFO strings were apparently not terminated properly. Not attempted to work around this. - LCC: not tested. Some fixes are in there from the last time we tried this, but then the build ultimately failed and I haven't tried this since that was fixed. - Dev-C++: untested. (Haven't done anything special.) - Unix Gtk/autoconf Makefiles work as before. [originally from svn r6374] [r6367 == f86ad059db0c5225b29da5f8a138d7dce4322f22] [this svn revision also touched putty-wishlist]
2005-10-04 14:13:28 +00:00
#include "version.rc2"
Add NO_MANIFESTS option to Windows build, as the manifests apparently cause trouble for 64-bit Windows builds. Also flag the build flags that only apply to Windows. [originally from svn r5820]
2005-05-21 14:35:21 +00:00
#ifndef NO_MANIFESTS
Add weird XML manifest resources, to enable WinXP skins to work within PuTTY's dialog boxen. [originally from svn r1530]
2002-01-08 09:32:50 +00:00
1 RT_MANIFEST "pageant.mft"
Add NO_MANIFESTS option to Windows build, as the manifests apparently cause trouble for 64-bit Windows builds. Also flag the build flags that only apply to Windows. [originally from svn r5820]
2005-05-21 14:35:21 +00:00
#endif /* NO_MANIFESTS */
Reference in New Issue Copy Permalink