Also tried on a MacBook Air 2012: no flickering.
So unless you have done a reinstall of Xojo (you still haven’t said) and still see the problem there is absolutely no point in doing a screen recording.
iMac Early 2008, OS X 10.11.6, Xojo Version 2017 R 2.1
- IDE does not flicker,
- apps built with Xojo do not flicker.
[quote=350662:@Marco Hof]Are you perhaps switching between user accounts?
Somehow, I always have the flickering when testing Apps on a second/different user.
Never tried it with the IDE itself but all my Apps flicker on macOS when I create a different user so I can emulate a fresh install.[/quote]
I have seen this too.
It’s edited
MacBook Air Early 2014
It wasnt what I was trying to say at all
I’ll refrain from commenting further
Interesting article: https://blog.xojo.com/2017/09/13/an-insiders-top-10-code-free-tips-to-being-a-skilled-programmer/ from Geoff Perlman I hope the internal XOJO developer also read it 
I like the first topic Be curious ask questions and seek answers
Tried switching to another user account but I see no flickering at all.
I haven’t tried it with High Sierra but it’s happening with quite some versions already. But I guess not with everyone then.
https://forum.xojo.com/33834-flicker-in-second-user
Perhaps it’s related.
Did you boot on the Recovery volume and fired Disk Utils application on your boot disk ?
[quote=350722:@Marco Hof]I haven’t tried it with High Sierra but it’s happening with quite some versions already. But I guess not with everyone then.
https://forum.xojo.com/33834-flicker-in-second-user
Perhaps it’s related.[/quote]
Strange thing is when i have other programs open, the problem seems to be gone, looks like xojo is using alot of processing time. Or it’s refreshing too fast?
But only on the MacBook Air the iMac has no problems.
I’ll try to login to feedback again.
For the third and final time: have you tried to completely remove and reinstall Xojo?
Yes i did this 2 times (Remove and Reinstall);
1st without any cache clearing didn’t work.
2nd with cache clearing and it did work. IDE is normal again.
Thanks…
Really wish there was a menu item to trash the cache.
The number of times this causes issues, and the number of times people can’t work out where the cache actually is…
[quote=350749:@Jeff Tullin]Really wish there was a menu item to trash the cache.
The number of times this causes issues, and the number of times people can’t work out where the cache actually is…[/quote]
Feature request 
https://forum.xojo.com/31649-solving-problems/0:
from xDev March/April 2016, www.xdevmag.com
Solving problems
Youre stuck. Your code should work, but it isnt. Or it does something unexpected and weird. Now what?
-
Use the debugger to follow code execution
Im always amazed by how many people dont follow their code in the debugger when they look for bugs. If you follow along in the debugger, then you can see which variable might not contain what you think it should contain. For example, integer overflow errors are easy to spot in the debuggerso use it! And keep in mind conditional breakpoints as mentioned in xDev 12.5 Sep/Oct 2014 Tip 3. -
Restart Xojo and clear the cache
I have Xojo running all the time and my computer only gets restarted when theres a system upgrade. But sometimes Xojo gets confused and things dont work or dont behave as youd expect. A restart of Xojo often fixes that, but sometimes I need to restart the computer (usually when Xojo has been running for weeks or months). Its worth repeating the tip from xDev 12.3 May/Jun 2014 Tip 6 by Christian Schmitz from MonkeyBread Software again: “For me the Cache folder has symbolic links named ‘Xojo’ and Real Studio’ which point to /tmp, so every time the Mac restarts, I get a cleared cache.” So no need to clear the cache by hand anymore. -
Make a sample project
If you see the problem in a small sample project, then you can not only exclude some unexpected side effects from the rest of your code, it will also make finding and fixing the problem much easier.
If you cant recreate the problem in a sample project, then the bug wasnt where you thought it was anyway, and youll save a lot of time not following the wrong lead.
Basic rule: if you cant be bothered to make a sample project, then you dont need help that urgently, if at all. -
Check feedback
Maybe someone else has reported the same problem and maybe it is a known bug. If you are lucky, there might even be a workaround. So dont wait for others to remember the bug report or for them to check feedbackdo it yourself! -
Implement a tracking system
With event-driven programming, it is sometimes difficult to figure out what is called when and wheredont simply assume that events happen in a certain order. Thomas Tempelmans free MethodProfiler (see xDev 13.6 Nov/Dec 2015 Tip 5) might be able to help. -
Then and only then ask on the forum
Describe your problem and provide a link to the sample project. Dont expect who-knows-how- many people to create sample projects based on your more or less accurate description just because you are too lazy and cant be bothered. Henry David Thoreau (xDev 12.4 Jul/Aug 2014 Intro) would be very cross with you about wasting so much life time.
All these recommendations should be obvious, but too often I see people asking for help on the forums that havent done the basic trouble-shooting. I know I have been guilty of it myself - but Ill try to do better… (Oh look, a flying pig!)
P.S. Some more emphasis on this tip from Christian “Mr. Monkeybread” Schmitz:
Its worth repeating the tip from xDev 12.3 May/Jun 2014 Tip 6 by Christian Schmitz from MonkeyBread Software again: “For me the Cache folder has symbolic links named ‘Xojo’ and Real Studio’ which point to /tmp, so every time the Mac restarts, I get a cleared cache.”
Thats very helpful, thanks Christian and Markus.
ps…I promise you, /tmp doesn’t always get cleared.
But that’s an off-topic discussion for some other time/post, and definitely ‘Actually Restart the Machine’ is the best advice.
[quote=350760:@Markus Winter]P.S. Some more emphasis on this tip from Christian “Mr. Monkeybread” Schmitz:
Its worth repeating the tip from xDev 12.3 May/Jun 2014 Tip 6 by Christian Schmitz from MonkeyBread Software again: “For me the Cache folder has symbolic links named ‘Xojo’ and Real Studio’ which point to /tmp, so every time the Mac restarts, I get a cleared cache.”[/quote]
Cute idea, but I’m pretty sure I reboot my mac less frequently than I upgrade Xojo versions