<?xml version="1.0" encoding="UTF-8"?>
	<rss version="2.0"
		xmlns:content="http://purl.org/rss/1.0/modules/content/"
		xmlns:wfw="http://wellformedweb.org/CommentAPI/"
		xmlns:dc="http://purl.org/dc/elements/1.1/"
		xmlns:atom="http://www.w3.org/2005/Atom"

			>

	<channel>
		<title>Cycling 74  &#187;  Topic: frustrated with thispatcher&#039;s filesaving support</title>
		<atom:link href="http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/feed</link>
		<description></description>
		<pubDate>Tue, 18 Jun 2013 17:14:10 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/#post-44469</guid>
					<title><![CDATA[frustrated with thispatcher&#039;s filesaving support]]></title>
					<link>http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/#post-44469</link>
					<pubDate>Sat, 20 Jun 2009 19:45:10 +0000</pubDate>
					<dc:creator>pseudostereo</dc:creator>

					<description>
						<![CDATA[
						<p><begin rant></begin></p>
<p>As far as I can tell&#8230;</p>
<p>For saving files, thispatcher accepts a &#8216;write&#8217; message or a &#8216;writeas&#8217; message (by the way &#8216;writeas&#8217; is currently completely undocumented, in either thispatcher&#8217;s help file or its reference page).</p>
<p>Neither &#8216;write&#8217; nor &#8216;writeas&#8217; accepts any arguments: &#8216;writeas&#8217; brings up a dialog, and &#8216;write&#8217; overwrites the file (unless it has never been saved, in which case it brings up a dialog as well)</p>
<p>Therefore, there is currently no way to set up any kind of auto-incrementing autosave mechanism using thispatcher.</p>
<p>It&#8217;s easy enough to throw together a little autosave abstraction, but only if you want to either a) use &#8216;write&#8217; and overwrite your current file every time or b) use &#8216;writeas&#8217;, and deal with a entering a new name in a file requester each time.</p>
<p>Entering a new file name each time defeats the whole purpose of autosaving.</p>
<p>And overwriting your current file means that the following scenario can happen:</p>
<p>You&#8217;ve been slaving away for hours, diligently autosaving the same file over and over. At some point, you&#8217;ve done something stupid and your patch causes a stack overflow. Max crashes. You&#8217;ve now lost the working version of your patch, because you&#8217;ve autosaved the version with the stack overflow.</p>
<p>Now you can&#8217;t open your patch at all, unless you hold down shift-command to defeat loadbang (a crucial keyboard command which should be documented somewhere besides the loadbang reference page). So you get to spend hours doing detective work, going through your patch, disconnecting things, attempting to load it again without shift-command, crashing Max again, etc etc</p>
<p>(Did this just happen to me? How did you guess?)</p>
<p>And searching the forums just shows that users have been asking about better filesaving support from thispatcher for literally years.</p>
<p>Maybe I&#8217;m missing something, in which case I hope someone will enlighten me.</p>
<p>Otherwise &#8211; dear friends at Cycling, can&#8217;t you do something about this? </p>
<p>This seems really&#8230; basic.</p>
<p><end rant></end></p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/#post-159928</guid>
					<title><![CDATA[Re: frustrated with thispatcher&#039;s filesaving support]]></title>
					<link>http://cycling74.com/forums/topic/frustrated-with-thispatchers-filesaving-support/#post-159928</link>
					<pubDate>Sun, 21 Jun 2009 02:45:37 +0000</pubDate>
					<dc:creator>Matthew Aidekman</dc:creator>

					<description>
						<![CDATA[
						<p>A) how have I been using max for 18 zillion years and never seen that there was a write function.  That saves me 9 billion years of work and I don&#8217;t even need hyperbole to express how happy I am!<br />
B) I don&#8217;t even see writeas documented anywhere</p>
<p>What an amazing feature.  So as long as you can embed everything you need, you can save and recall it all as a single file!!!</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

