Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Comment: | Don't overwrite fields if only carriage return is entered
In other words, prevent accidentally deleting fields. This has always This small change means that if you just enter return then the old value This is good enough for me. There is one downside: if you really want to |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | origin/tweaks | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
1559d3c95645eb1cb6ab8c55a25d559e |
| User & Date: | atomicules@lavabit.com 2013-03-22 17:02:02.000 |
|
2013-03-23
| ||
| 21:27 |
Extend the "don't overwrite fields if only carriage return is entered" to password field
And also use malloc. What I'd done before wasn't doing what I thought. C I'm in two minds about the benefit of dynamic allocation though. Since | |
|
2013-03-22
| ||
| 17:02 |
Don't overwrite fields if only carriage return is entered
In other words, prevent accidentally deleting fields. This has always This small change means that if you just enter return then the old value This is good enough for me. There is one downside: if you really want to | |
| 17:01 | Merge branch 'modernise' into tweaks2 check-in: 9ed6b07353 user: atomicules@lavabit.com tags: origin/tweaks, trunk | |