R
Richard Kucia
I've been reading up a little bit on the MS logo requirements for mobile
applications. If I understand them correctly, the use of a "File" menu was
previously forbidden, but is now acceptable. My app uses a "File" menu for
the usual desktop functionality.
My user can open one or more existing project files within the app, and can
also create one or more new projects. Upon File | Exit, the app prompts the
user to save each "dirty" or unsaved project -- typical desktop processing.
What I'm confused about is how to meet the logo requirement when power goes
off or Windows Mobile elects to cannibalize the executing program. I can't
simply save the "dirty" projects because the user's intention might be to
abandon changes. And I can't guess what filenames the user intended for the
new projects. Anyone have any pointers on the proper logo-compatible design?
Thanks.
Richard Kucia
applications. If I understand them correctly, the use of a "File" menu was
previously forbidden, but is now acceptable. My app uses a "File" menu for
the usual desktop functionality.
My user can open one or more existing project files within the app, and can
also create one or more new projects. Upon File | Exit, the app prompts the
user to save each "dirty" or unsaved project -- typical desktop processing.
What I'm confused about is how to meet the logo requirement when power goes
off or Windows Mobile elects to cannibalize the executing program. I can't
simply save the "dirty" projects because the user's intention might be to
abandon changes. And I can't guess what filenames the user intended for the
new projects. Anyone have any pointers on the proper logo-compatible design?
Thanks.
Richard Kucia