<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/lifelines/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/lifelines/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/lifelines/feature-requests/</id><updated>2008-05-17T19:42:19Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Handle DEAT/MARR/DIV Y</title><link href="https://sourceforge.net/p/lifelines/feature-requests/19/" rel="alternate"/><published>2008-05-17T19:42:19Z</published><updated>2008-05-17T19:42:19Z</updated><author><name>elsapo</name><uri>https://sourceforge.net/u/elsapo/</uri></author><id>https://sourceforge.netc10430031b81da309ad67cbff1c9533cb8dfd09a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Patrick Texier requested that info page displays when person has DEAT Y, or MARR Y, or DIV Y&lt;/p&gt;
&lt;p&gt;I just implemented a revision to birth &amp;amp; death display which handles this for death, but marriage is a separate section of code (&amp;amp; currently ignores DIV).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Mention self-test in release process</title><link href="https://sourceforge.net/p/lifelines/feature-requests/18/" rel="alternate"/><published>2007-05-11T19:04:19Z</published><updated>2007-05-11T19:04:19Z</updated><author><name>elsapo</name><uri>https://sourceforge.net/u/elsapo/</uri></author><id>https://sourceforge.net21890b888b2f0b59aefda3596779e2339094f250</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Add note to README.MAINTAINERS.something to check the st\st_all report.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>new report function gettatgs</title><link href="https://sourceforge.net/p/lifelines/feature-requests/17/" rel="alternate"/><published>2007-04-20T00:50:57Z</published><updated>2007-04-20T00:50:57Z</updated><author><name>elsapo</name><uri>https://sourceforge.net/u/elsapo/</uri></author><id>https://sourceforge.netaa4c0edaeab8c14ed653b74e0073ad84c6737857</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;From request &amp;amp; discussions on LINES-L list, Nov 2005 week 4:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://listserv.nodak.edu/cgi-bin/wa.exe?A1=ind0511d&amp;amp;L=lines-l" rel="nofollow"&gt;http://listserv.nodak.edu/cgi-bin/wa.exe?A1=ind0511d&amp;amp;L=lines-l&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;My last proposal was here:&lt;br /&gt;
&lt;a href="http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0511d&amp;amp;L=lines-l&amp;amp;T=0&amp;amp;P=6185" rel="nofollow"&gt;http://listserv.nodak.edu/cgi-bin/wa.exe?A2=ind0511d&amp;amp;L=lines-l&amp;amp;T=0&amp;amp;P=6185&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Implement "--version"</title><link href="https://sourceforge.net/p/lifelines/feature-requests/16/" rel="alternate"/><published>2005-10-01T17:45:26Z</published><updated>2005-10-01T17:45:26Z</updated><author><name>elsapo</name><uri>https://sourceforge.net/u/elsapo/</uri></author><id>https://sourceforge.net49205d3a12d2ad200c555572464dc64f64ba7d2f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implement --version/-v option.&lt;br /&gt;
Its conventional.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Improve "const correctness"</title><link href="https://sourceforge.net/p/lifelines/feature-requests/15/" rel="alternate"/><published>2005-07-11T21:00:23Z</published><updated>2005-07-11T21:00:23Z</updated><author><name>Markus Elfring</name><uri>https://sourceforge.net/u/elfring/</uri></author><id>https://sourceforge.net705ba643ad0f0036f490356fadc39f89f3aaa8e9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Would you like to apply the advices from the article&lt;br /&gt;
"http://en.wikipedia.org/wiki/Const_correctness" to&lt;br /&gt;
your sources?&lt;br /&gt;
I suggest to add the key word "const" to the type&lt;br /&gt;
specifiers for parameters like the following.&lt;br /&gt;
- ttl (function "ask_for_indiseq")&lt;/p&gt;
&lt;p&gt;&lt;a href="http://cvs.sourceforge.net/viewcvs.py/lifelines/lifelines/src/liflines/llinesi.h?rev=1.67&amp;amp;view=markup"&gt;http://cvs.sourceforge.net/viewcvs.py/lifelines/lifelines/src/liflines/llinesi.h?rev=1.67&amp;amp;view=markup&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;- ttl, prmpt, basedir (function "ask_for_db_filename")&lt;/p&gt;
&lt;p&gt;&lt;a href="http://cvs.sourceforge.net/viewcvs.py/lifelines/lifelines/src/liflines/llexec.h?rev=1.2&amp;amp;view=markup"&gt;http://cvs.sourceforge.net/viewcvs.py/lifelines/lifelines/src/liflines/llexec.h?rev=1.2&amp;amp;view=markup&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Shared libraries</title><link href="https://sourceforge.net/p/lifelines/feature-requests/14/" rel="alternate"/><published>2005-07-07T18:26:19Z</published><updated>2005-07-07T18:26:19Z</updated><author><name>James Prevatt</name><uri>https://sourceforge.net/u/jmprev/</uri></author><id>https://sourceforge.net9626eec15c810870f042274574f30e6c3e97fdd4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;One more modification request that would make it easier for an OpenBSD port/packages: use shared versions of libiconv and libintl instead of statically linking them.  Thanks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Install location for man pages</title><link href="https://sourceforge.net/p/lifelines/feature-requests/13/" rel="alternate"/><published>2005-07-07T18:24:47Z</published><updated>2005-07-07T18:24:47Z</updated><author><name>James Prevatt</name><uri>https://sourceforge.net/u/jmprev/</uri></author><id>https://sourceforge.nete6a48a633b4d12326260cccdcc5f7e0eaf492930</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am working on a port to submit into the OpenBSD ports/package tree.  Would it be possible to modify the installation procedure so the the man pages are actually installed to the locations specified by the configure script?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Make !x GEDCOM indentation configurable</title><link href="https://sourceforge.net/p/lifelines/feature-requests/12/" rel="alternate"/><published>2005-06-20T17:19:33Z</published><updated>2005-06-20T17:19:33Z</updated><author><name>elsapo</name><uri>https://sourceforge.net/u/elsapo/</uri></author><id>https://sourceforge.net57693451c111dab533b763f36b0ba75dc596585a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Make !x GEDCOM indentation configurable&lt;/p&gt;
&lt;p&gt;When displaying in a Gedcom-like format (for example, in&lt;br /&gt;
response to !x), LifeLines uses a 6-space indentation&lt;br /&gt;
for each level.  I am writing to request that this&lt;br /&gt;
amount of indentation in a future release be changed so&lt;br /&gt;
that it not be any predetermined amount, but that it&lt;br /&gt;
become instead a configurable quantity (with 6 as a&lt;br /&gt;
reasonable default).&lt;/p&gt;
&lt;p&gt;(Requested by W. E. Brown on LINES-L list)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Provide a way to delete a source record</title><link href="https://sourceforge.net/p/lifelines/feature-requests/11/" rel="alternate"/><published>2005-01-03T05:02:48Z</published><updated>2005-01-03T05:02:48Z</updated><author><name>Peter Fales</name><uri>https://sourceforge.net/u/psfales/</uri></author><id>https://sourceforge.net46133d7df0c58fd28c7953ce01fac26f868bdf42</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;As far as I know there is currently no way to delete a&lt;br /&gt;
source record, right?&lt;br /&gt;
I believe it may even be so stated in the&lt;br /&gt;
documentation.   I think it would be useful to be able&lt;br /&gt;
to do that.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>confirm box before swapping families</title><link href="https://sourceforge.net/p/lifelines/feature-requests/10/" rel="alternate"/><published>2005-01-03T02:30:17Z</published><updated>2005-01-03T02:30:17Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.net6f1ec3198e5807e54dd69d5e96ad413a6a86912c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;RFE on mailing circa August 2004 by Jens Arvidsson:&lt;/p&gt;
&lt;p&gt;When using the "Swap two families" command, the current&lt;br /&gt;
LL behaviour is (provided the person is a spouse in two&lt;br /&gt;
families) to automatically switch the families, no&lt;br /&gt;
questions asked (a message is shown in the message&lt;br /&gt;
panel though). I think that it would be useful to be&lt;br /&gt;
prompted before the switch is done, since it is fairly&lt;br /&gt;
easy to invoke the command by mistake and then miss the&lt;br /&gt;
message (I sometimes do this when I really mean to&lt;br /&gt;
press "!x").&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>