Hi Keisuke -

Thanks for your response.  I have looked at that feature, and I can see how it 
is useful for the first time my app is launched.  In fact, I already built that 
mechanism into my app by setting the DataFilePath key in the XML build file to 
a dummy datafile embedded within the application package.  I think it does the 
same thing as this new “Default Data” mechanism, no?  In any case, I don’t 
understand how it solves the problem once my app has opened a valid datafile, 
has quit, and is relaunched.

I suppose I could blow away the lastDataFile.xml file each time I quit my app, 
causing it to open the default data file upon next launch.  But that does not 
solve my problem, which is that 4D still does not know the user launched my app 
with a specific datafile in mind (by either double clicking on the datafile or 
dragging the datafile on top of my app icon).

Am I still missing something?

- Steve


> On Jun 29, 2017, at 6:00 AM, Keisuke Miyako via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> you really need to use the "Default Data" mechanism
> 
> http://doc.4d.com/4Dv15/4D/15/Default-data-file-in-merged-applications.300-2018649.en.html
> 
>> 2017/06/29 17:28、Steve Slanec via 4D_Tech <4d_tech@lists.4d.com> のメール:
>> What are other people doing to work around this?
> 
> 
> 
> 
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to