<?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/camelbones/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/camelbones/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/camelbones/feature-requests/</id><updated>2007-03-04T00:08:24Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>ShuX feature request</title><link href="https://sourceforge.net/p/camelbones/feature-requests/4/" rel="alternate"/><published>2007-03-04T00:08:24Z</published><updated>2007-03-04T00:08:24Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net54d6e96a198479f7cac0d026a16a722754475d6f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Can you make ShuX read the old MacPerl pods? The come up garbled, presumably due to line-ending issues at least in beta 5.&lt;/p&gt;
&lt;p&gt;Uli Wienands&lt;/p&gt;
&lt;p&gt;wienands@gmail.com&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Choice of Font size</title><link href="https://sourceforge.net/p/camelbones/feature-requests/3/" rel="alternate"/><published>2006-02-16T23:26:41Z</published><updated>2006-02-16T23:26:41Z</updated><author><name>Celeste Suliin Burris</name><uri>https://sourceforge.net/u/csburris/</uri></author><id>https://sourceforge.net335bef73ce034116df147424d730105b654a32b9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For those of us with Hi-Res Screens, some of the docs are unreadable. A &lt;br /&gt;
simple choice of font size in preferences would be fine.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Tutorials</title><link href="https://sourceforge.net/p/camelbones/feature-requests/2/" rel="alternate"/><published>2005-09-24T04:41:20Z</published><updated>2005-09-24T04:41:20Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net428e5fa829ac7de4bc7b5453a523c39448180069</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Your menu's tutorial make too big a leap when it comes time to &lt;br /&gt;
connect the menu items to the 'first responder'.&lt;/p&gt;
&lt;p&gt;Too many steps are skipped, not clear how to get menue to connect &lt;br /&gt;
and what needs to be created to do it. A simple list of the steps &lt;br /&gt;
would help. &lt;/p&gt;
&lt;p&gt;I got lost here:&lt;/p&gt;
&lt;p&gt;Making the connection&lt;/p&gt;
&lt;p&gt;Connecting to First Responder.&lt;br /&gt;
click to enlarge&lt;br /&gt;
First you'll need to create the actions to which you'll connect your &lt;br /&gt;
menu items. This is nearly identical to the actions you created in the &lt;br /&gt;
earlier "Responding to Events" tutorial, so I'll leave out most of the &lt;br /&gt;
detail. The major difference is, where you added those actions to the &lt;br /&gt;
"File's Owner", you need to add these actions to the "First &lt;br /&gt;
Responder" instead.&lt;/p&gt;
&lt;p&gt;Connecting them is virtually the same, as well. Expand the menu &lt;br /&gt;
holding the menu item you wish to connect, so that it's visible. Then, &lt;br /&gt;
control-drag the connection from the menu item to the "First &lt;br /&gt;
Responder" icon, and double-click the action you wish to connect it &lt;br /&gt;
to in Interface Builder's "Info" panel.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>create announce mailling list</title><link href="https://sourceforge.net/p/camelbones/feature-requests/1/" rel="alternate"/><published>2002-03-28T18:44:58Z</published><updated>2002-03-28T18:44:58Z</updated><author><name>matthew wickline</name><uri>https://sourceforge.net/u/wickline/</uri></author><id>https://sourceforge.neta73722bd6f5e4df7c21c724faa7b342814754984</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;please create an annoucnments mailing list so we can&lt;br /&gt;
find out about&lt;br /&gt;
1) new versions released&lt;br /&gt;
2) major changes to website (ie: new docs and such)&lt;/p&gt;
&lt;p&gt;this looks Cool! :)&lt;/p&gt;
&lt;p&gt;-matt&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>