<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Multiple Settings Profiles</title>
		<link>http://aprsisce.wikidot.com/forum/t-618915/multiple-settings-profiles</link>
		<description>Posts in the discussion thread &quot;Multiple Settings Profiles&quot;</description>
				<copyright></copyright>
		<lastBuildDate>Sun, 09 Aug 2026 10:24:43 +0000</lastBuildDate>
		
					<item>
				<guid>http://aprsisce.wikidot.com/forum/t-618915#post-1851443</guid>
				<title>Re: Multiple Settings Profiles</title>
				<link>http://aprsisce.wikidot.com/forum/t-618915/multiple-settings-profiles#post-1851443</link>
				<description></description>
				<pubDate>Fri, 13 Sep 2013 19:14:12 +0000</pubDate>
				<wikidot:authorName>APRS IS CE</wikidot:authorName>				<wikidot:authorUserId>440686</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>You can do this today by simply running APRSIS32 from a different directory. Since the XML configuration file is stored in the default directory when the .EXE is run, each directory ends up with it's own configuration. You can even copy the APRSIS32.XML file from one directory to a new one and then make changes from there.</p> <p>I have multiple configurations available, some of which are concurrently active (with unique -SSIDs), and run them all from a single copy of APRSIS32.EXE with multiple short-cuts each specifying a different default directory for execution.</p> <p>Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://aprsisce.wikidot.com/forum/t-618915#post-1695438</guid>
				<title>Multiple Settings Profiles</title>
				<link>http://aprsisce.wikidot.com/forum/t-618915/multiple-settings-profiles#post-1695438</link>
				<description></description>
				<pubDate>Sat, 26 Jan 2013 04:55:50 +0000</pubDate>
				<wikidot:authorName>APRS-Jeff</wikidot:authorName>				<wikidot:authorUserId>1530772</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Lynn,</p> <p>I was contemplating changing several of my settings the other day (for mobile ops from a sailboat), and I realized several things that I might manually want to change (SSID, map tile set, APRS icon, path, etc.) on a recurring basis. I then thought about the paradigm that the Kenwood Radios (D700, D710) utilize with their Programmable Memories (PMs)</p> <p>My idea would be for APRSISCE/32 to employ the concept of &quot;profiles&quot;. Using this concept, the operator could set, save, and recall groups of settings. These &quot;profiles&quot; could be named for easy recall, and be implemented by merely managing xml configuration file(s) with a little bit of program logic. In fact, I'm doing this now on my WinMo device with a scripting language. I call a script from a shortcut which renames/copies a certain copies of the setup xml files, and then calls the program. But, it would be more elegant if the program handled profile management internally.</p> <p>Anyway, I thought I would pass this along as a suggestion if you deem it worthy for your next upgrade.</p> <p>73,<br /> Jeff<br /> N5TEV</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>