On Tue, Jan 01, 2008 at 03:29:15PM -0500, David Reiser wrote: > > On Jan 1, 2008, at 1:38 PM, Mike Alexander wrote: > >> --On December 31, 2007 4:46:27 PM -0800 Andrew Sackville-West >> <[EMAIL PROTECTED]> wrote: >> [snip] >> >>> 3) how to handle the saved reports. specifically, how to get the user >>> to actually go in and fix the things -- do they need to edit the file >>> by hand? can they just resave the report and have it overwrite the old >>> one (ideal solution, but I don't think that works ATM)? can we >>> implement something to one-time-deal translate those reports into YA >>> saved-reports-2.2 file? >> >> If a saved report doesn't have an internal ID could you generate one on >> the fly? >> >> Mike > > I'm pretty sure Hampton wrote code to create an ID on the fly for custom > check formats. I would imagine it could be reused pretty easily.
the engine generates (from somewhere -- handwave) GUID's all the time, there must be a way to just grab one. The actual content of the internal ID of a report is completely meaningless, so long as it's unique, so I would think a GUID would be perfect. A
signature.asc
Description: Digital signature
_______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
