A piece of one card appears on another

[dunbarx]

I am making a gadget for my niece. There are two cards in the stack, filled with graphic objects.

All of a sudden, a thin ghost-like portion of the bottom of card 1 "appears" on card 2 when I navigate to card 2. There is nothing actually there, and if I click on any part of that phantom with the pointer tool, it disappears. I can in fact erase the phantom with the pointer tool, as if it were the eraser for the painting tools.

When I go back to card 1, that same phantom area of cd 2 appears back on cd 1.

As a master of stupid Kludges, the only way I can fix this is to place a blank field over the areas on each card, select it upon navigation, and then deselect it. Those two fields will "erase" the phantom, simply by coming "forward" for an instant.

Here are screenShots of the bottoms of the two cards. The first is the bottom of card 1, the second, below the three circles which are actually on card 2, is the phantom bottom of card 1.

Corruption?

Craig

[richmond62]

Your operating system?

Your version of LC?

The dimensions of your stack?

[dunbarx]

Mac OS !0.17.7 Catalina

LC 9.6.1

Dimensions of my stack, Richmond?

Craig

[stam]

I’ve had visual artefacts like that when something has crashed in the background (can be a completely silent crash like with the geometry manager)

If in a new stack with no code you just copy the patterns on two cards, does this still happen when switching cards?

Alternatively could one of these to have been made into a background?

S.

[richmond62]

Mac OS 10.17 . . . REALLY?

[jacque]

There was a similar problem on mobile some time ago with both card redraws and scrollers. I'd say it's an engine bug, but there have been several updates since 9.6.1 so it may have been fixed. It might also be related to the way menubars scroll the stack on Macs. Do you use a menubar?

[LCMark]

@dunbarx: Try updating to 9.6.8 - there's a 99% chance that that will make the issue go away... (The 1% is reserved for the possibility of it being something you are doing in script causing it without realizing ).

[richmond62]

Just installing 9.6.1 on my main machine (MacOS 13 beta):
Setting up a stack with 2 cards and LOTS of graphic objects on the first card:
-

-
and NONE on the second card:
-

-
and, as you can see: no obvious problems at all.

So:

1. I have missed something?

2. You have missed something?

3. You have a 'poisoned' LC 9.6.1 setup?

[richmond62]

I should also like to add that there has been a lot of negative flack about MacOS 10.15 (Catalina) and MacOS 11 (Big Sur),
so, if possible, I would recommend that you update you system to MacOS 12 (Monterey), which, from my experience at least,
is significantly better.

[dunbarx]

Thanks all.

This happened right in the middle of development. I was happily moving from one card to the other when it just appeared.

Richmond. OS 10.15.7

@Mark and Jacque. I will try the updated version of LC.

@ Stam. Same with restarting the machine, never mind restarting LC. No backgrounds, AND the same controls copied to a new stack also do this.

My kludge works, but I will update LC and report back

Craig

[dunbarx]

Tried in v.9.6.8. Same problem.

No other stack I have exhibits this oddity, so fortunately it is something about the controls on this stack. I believe this because of the fact that I copied all objects onto a new two-card stack and still have the same issue. So what then? That lots of graphics (there are about 550 on both cards) are the cause? That one or more graphics themselves are corrupted and have infected the whole? Can a control be corrupted in the first place?

Know that a standalone acts exactly the same.

@MarkW. Any interest in seeing this stack? I can live with it, but it makes me nervous.

Craig

[LCMark]

@dunbarx: file a bug in the quality center and email the stack to support if it’s sensitive; otherwise just attach and we will take a look.

[dunbarx]

LCMark.

Filed bug 23826. Non-sensitive stack attached.

Craig

[dunbarx]

So it seems there is an engine bug having to do with the vertical placement of Mac menuBars. The issue is confined to an area the width of the card and exactly the height of such a menubar.

I have lots of "custom" menus in my stacks and never noticed anything odd before this one. I suspect other mac developers have done similar things.
Anyway, it likely will not damage anything nor cause a crash, so my kludge will stay in place, and I can move on.

Craig

[stam]

So it seems there is an engine bug having to do with the vertical placement of Mac menuBars. The issue is confined to an area the width of the card and exactly the height of such a menubar.

I have lots of "custom" menus in my stacks and never noticed anything odd before this one. I suspect other mac developers have done similar things.
Anyway, it likely will not damage anything nor cause a crash, so my kludge will stay in place, and I can move on.

Craig

Good to hear you solved this although i don't understand - can you adjust the vertical placement of a mac menu bar? How is it affected by what happens on a card? Or do you mean menubar as in what the IDE does - some kind of toolbar, as opposed to actual menus?