Oooh! For once I might make a contribution!
I had the same issue in a healthcare context. These IT systems vary
tremendously between services, are complex and often hard to connect with -
either by design, or by lack of interest in supporting other software.
I found the best way to get a comb
I agree (from limited experience I admit). The hassle referred to usually
includes messages from the OS that many non-tech users will find mysterious,
confusing and generally off-putting. Quite a lot of users don’t really
understand the requirement to log in just to get some bit of software upda
Thank you all for your advice. Jacque, normalizeText() was what I had vaguely
remembered but couldn’t find.
Richmond, I am working on a library that removes emojis from text and replaces
them with imageSource... so that the text can be printed to PDF on mobile. You
are correct about the “going
Sorry if this is documented somewhere but I can’t find it.
On desktop platforms, LC gives us “suspend” which is fired when the app goes
into the background. I seem to be having some problems with iOS, in that when
the screen locks (triggered by user action or a time limit), my app seems to
sto
I’m not sure what you mean with ”suspend” on mobile. You only run one
application at a time. If your app goes out due to a phone call or any other
event it will normally quit your app and send a closeStack message and some
more. If you want to create an application that doesn’t allow the screen
I’m re-sending this because I used the wrong email server.
Bill
William Prothero
http://es.earthednet.org
> On Nov 17, 2020, at 8:46 AM, William Prothero wrote:
>
> David and Graham,
> One approach that occurred to me is this.
> There are 2 components to the work that students would “hand in”
William Prothero wrote:
> It seems the effort to make this app work with learning management
> systems would be huge, something I’m definitely not up for.
It may not be. I've made standards-compliant courseware in the past (a
while ago; the data format was XML ), and it wasn't as bad as I'd
t
Android has always acted like this and now that iOS apps run in the
background like Android does, it behaves the same way. At least our
problems are cross-platform now.
An app will stay in RAM until the user specifically quits or until the OS
needs the memory. When that happens, the OS wipes t
On iOS use mergNotify as below. Works well for me.
on openStack
mergNotify "UIApplicationWillResignActiveNotification"
mergNotify "UIApplicationDidBecomeActiveNotification"
end openStack
on UIApplicationWillResignActiveNotification pUserInfo
// Your code before the app goes to background
--
Richard,
I kinda like the pdf idea. Seems it would give me a way to encapsulate and
format the text and images and perhaps a fairly defined pdf format would make
it straightforward to edit it using Livecode as well.
Best,
Bill
William A. Prothero
https://earthlearningsolutions.org
> On Nov 17,
> The application's core is access to Earth data (that scientists used to
> develop the theory of plate tectonics) and capturing and annotating plots
> that can be incorporated into student writing.
If the 'student writing' is created in some other program then wouldn't it be
sufficient to al
And just a reminder that, under iOS, you’ll have to register to receive a “
UIApplicationWillResignActiveNotification” message, and then write a handler to
respond to that (PS only register once in your stack script — I learned the
hard way). It’s documented under mergNotify in the dictionary (w
For getting it FROM the student, why not just use a livecode stack file. It
could contain everything and be highly editable. For returning it TO the
student you could use a pdf.
--
Scott Morrow
Elementary Software
(Now with 20% less chalk dust!)
web https://elementarysoftware.com/
email
Scott Morrow wrote:
> For getting it FROM the student, why not just use a livecode stack
> file. It could contain everything and be highly editable.
^ this
LiveCode stack files are an underrated document format.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the
14 matches
Mail list logo
