Search found 47 matches
- Thu May 09, 2024 1:14 am
- Forum: Getting Started with LiveCode - Complete Beginners
- Topic: Unusual Refresh Problems with Mac standalone
- Replies: 21
- Views: 2355
Re: Unusual Refresh Problems with Mac standalone
Klaus? Strange comment? I wasn't sure if the original poster's bug was actually this one since he/she didn't specify the area not being drawn correctly. Anyway, the bug I am talking about is still present in 9.6.12 rc1. I haven't checked LC10, I am looking forward to a stable version of that but it ...
- Tue May 07, 2024 1:35 am
- Forum: Getting Started with LiveCode - Complete Beginners
- Topic: Unusual Refresh Problems with Mac standalone
- Replies: 21
- Views: 2355
Re: Unusual Refresh Problems with Mac standalone
Forgot to add: you also won't see the bug if all cards in your stack look exactly the same in the bottom 25-pixel height area - same background colour and no (or the same, with the same hilited values ) controls. This is probably the main reason most people will not be affected by the bug.
- Tue May 07, 2024 12:56 am
- Forum: Getting Started with LiveCode - Complete Beginners
- Topic: Unusual Refresh Problems with Mac standalone
- Replies: 21
- Views: 2355
Re: Unusual Refresh Problems with Mac standalone
The bug I referred to is Bug 22027 https://quality.livecode.com/show_bug.cgi?id=22027 reported in 2020 and still here in 9.6.11. The bug report has a simple stack which demonstrates the effect. You won't notice the bug if whenever you move between cards you have any code which causes the whole card ...
- Sun May 05, 2024 11:35 am
- Forum: Getting Started with LiveCode - Complete Beginners
- Topic: Unusual Refresh Problems with Mac standalone
- Replies: 21
- Views: 2355
Re: Unusual Refresh Problems with Mac standalone
The part of the screen which does not draw ... is this just the bottom 25 pixels (menubar height) at the bottom of the window? If so that is a bug which has been around for a long time and is very annoying. It is on the QC list. As noted the fix is to apply any sort of lock unlock screen combination...
- Sat Sep 22, 2018 5:20 am
- Forum: iOS Deployment
- Topic: unknown C++ exception error
- Replies: 3
- Views: 3896
Re: unknown C++ exception error
I moved the Simulator into Applications, and open it directly from there, rather than through Xcode (ie with Xcode closed). While LC Test then worked, I now rather doubt this had anything to do with the problem actually. I have had no problems since then, and have downloaded the latest Xcode, so I d...
- Mon Sep 10, 2018 1:09 pm
- Forum: iOS Deployment
- Topic: unknown C++ exception error
- Replies: 3
- Views: 3896
Re: unknown C++ exception error
I isolated the Simulator app from Xcode, closed Xcode leaving the Simulator running—and LC now communicates with the Simulator, all now good.
- Mon Sep 10, 2018 3:58 am
- Forum: iOS Deployment
- Topic: unknown C++ exception error
- Replies: 3
- Views: 3896
unknown C++ exception error
I am attempting to build a simple iPad app -at this point just to show the splash page- and am getting "644,0,0 unknown C++ exception 573,228,11 revIPhoneSetSimulatorSDK" error. LC finds the Xcode simulator correctly and the simulator is running. The codesigning certificate is current. This is in LC...
- Thu Jan 25, 2018 4:53 am
- Forum: Linux
- Topic: weird text display overwriting problem
- Replies: 7
- Views: 12601
Re: weird text display overwriting problem
Thanks mwieder
I do have Arial installed. But I get the same problems (with various text) when I use the Ubuntu fonts "Ubuntu" or "LiberationSans". I've decided to go with using "Default" which works in all the cases I need at least.
I do have Arial installed. But I get the same problems (with various text) when I use the Ubuntu fonts "Ubuntu" or "LiberationSans". I've decided to go with using "Default" which works in all the cases I need at least.
- Fri Dec 29, 2017 1:48 am
- Forum: Linux
- Topic: weird text display overwriting problem
- Replies: 7
- Views: 12601
Re: weird text display overwriting problem
Thanks guys for your response (and Happy New Year) Richard, I am using Ubuntu 16.04. My user is on Ubuntu 18.10. Good suggestion about the theme, but no help: the program runs from the command line without any messages. I find that a workaround seems to be to set the text font of the label field to ...
- Sat Dec 23, 2017 3:50 am
- Forum: Linux
- Topic: weird text display overwriting problem
- Replies: 7
- Views: 12601
Re: weird text display overwriting problem
the script should have been
of courseset the textsize of fld 1 of cd 1 of stack "myAlert" to 14
put "No external displays detected" into fld 1 of cd 1 of stack "myAlert"
- Sat Dec 23, 2017 2:53 am
- Forum: Linux
- Topic: weird text display overwriting problem
- Replies: 7
- Views: 12601
weird text display overwriting problem
I have a weird problem with text in a label field not rendering properly, with part of the text overwriting the previous part lLiveCode 8.1.9, Ubuntu linux installed under Parallels on a Mac, but confirmed by native Ubuntu user] I have a simple label field in a simple stack "myAlert". set the textfo...
- Fri Dec 08, 2017 4:20 am
- Forum: Talking LiveCode
- Topic: start using stack in standalone
- Replies: 9
- Views: 5733
Re: start using stack in standalone
Solved. I recompiled with LC7.1.3. Here the workaround I installed for LC8 now doesn't work in the development environment, let alone the standalone! But it does throw an error, saying the remote handler (which is in the script of myApp) cannot be found when I explicitly go to the stack myApp, while...
- Fri Dec 08, 2017 1:32 am
- Forum: Talking LiveCode
- Topic: start using stack in standalone
- Replies: 9
- Views: 5733
Re: start using stack in standalone
Hmm, the "weird" bit above about whether called from within the stack or outside. The defaultStack is different in those two cases! That may be the clue I need.
- Fri Dec 08, 2017 1:16 am
- Forum: Talking LiveCode
- Topic: start using stack in standalone
- Replies: 9
- Views: 5733
Re: start using stack in standalone
Thanks. I have been doing that (or equivalent, with my own logging routines). And yes, maybe aborting rather than exit to top, but that's essentially equivalent - except that abort should produce an error message I would have thought. An actual crash might be more informative. I guess I must have a ...
- Thu Dec 07, 2017 10:22 pm
- Forum: Talking LiveCode
- Topic: start using stack in standalone
- Replies: 9
- Views: 5733
Re: start using stack in standalone
Yes. I have a custom alert in the library (myApp) which fires if called from myData except if called from the menu scripts. This is probably the main reason I don't want to use the workaround of going to myApp to call the alert, I want the alert to show on top of the myData window; for other calls t...