I want to display uitable in matlab GUI.(uitable data is not fix it is going to update in 15 stage).
when i run my code in my laptop my monitor is not flicker, but when i run same code in another laptop it start blinking.
i want to know the cause of this problem(i mean the code not changed only ,i run it in another computer).
note:i guess it is related to CPU clock but i am not sure.
it is not related to CPU or laptop graphic card. it is about matlab version.i write my original code in matlab 2013a but when i run it in matlab 2009 ,it had problem n displaying uitable but in matlab 2012 or newer version that problem solved and the blinking did not occur.
Related
I have a Mac application project that builds and runs in XCode 10.2.1 using Swift 4. When I try to convert it to Swift 5, the process starts, and then at about step 32 (of about 158), the machine locks up to the point where it either reboots, or I have to force it to shut down. What should I be looking for to stop this from happening?
By “lock up” I mean everything stops. The spinning wheel graphic in XCode that indicates that things are going on stops spinning. The mouse pointer freezes. The keyboard is non-responsive. Any on screen animations stop (eg if the pointer is the Spinning Pizza of Death - that stops spinning) If I leave it long enough, it may reboots - two chimes.
I have tried converting another project, and that converts without any problems. So I am going to assume that there is something specific to the project I have that’s the problem
I have tried this on two machines - my 2012 Mac Mini with 16GB RAM, and a MBP which is a couple of years newer with 8GB RAM. Same problem on both.
I have also tried setting the Swift version from 4.0 to 4.2 in the project. The same thing happens - the machine processes the change and locks up during the process. However, this time before locking up I get the Force Quit dialog window, and a message telling me that all available application memory has been used up, and I should force quit applications. At this point, the machine freezes, so I can’t do that.
I’ve tried a few searches on the subject, but have found nothing that describes my problem.
I have no code to show because I don’t know what code is causing this (if anything - it could be a bug in XCode of course). It could be a setting in the Xcode project file.
Desired results - Xcode converts my project from Swift 4 to Swift 5.
Actual results - Xcode locks up the machine completely. I have to force power down my Mac and reboot.
So the question is - what should I be looking for to get around this issue? Has anyone else had this problem? What can I try to resolve this? The freezing and rebooting is a bit alarming.
What worked for me is to move one view controller from each storyboard file and save the file. For some reason Xcode crashes my computer if I don't do that every time I reopen Xcode. After I saved each storyboard file, I converted the project to Swift 5 with no problems.
I am running Matlab on Windows 10. On Windows 10, I have the option, "Size of Text, Apps and other items" set to 175%. When I open Matlab, all the buttons and Matlab code appear larger as expected for 175%. However, when I run a matlab code, the size of the matlab icons and the matlab buttons becomes much smaller (roughly by about 75%). I think it is not detecting that my windows setting after the first run. Is there any way I can fix this. As my laptop screen is rather small, I need to use 175% zoom to be able to see the icons clearly.
I had a GUI made using GUIDE. Suddenly when I reopened MATLAB the GUI window got resized, zoomed-in and cropped, missing the top of it. This shows in GUIDE itself as well.
I'm using the same computer and MATLAB version. I already tried to restart MATLAB and the computer itself.
The only thing I can think of that changed is a second monitor I was using, but I tried plugging it in and out, and it didn't help.
This doesn't happen in other GUIs I'm using.
Specs:
Windows 8, MATLAB R2013a, 1920x1080 screen resolution.
Try changing the units of all the controls to normalized.
MATLAB sizes GUIs based on system information about the size of the screen, so adding a second monitor could change that system information and confuse MATLAB. You could test if that is what caused the problem by unplugging the new monitor and restarting the computer/program.
For one project I had to change the units on everything to characters so that it would size appropriately for various screen sizes. Normalized should work too, however, it won't revert the gui to how it was before it got jacked up, only keep it from changing again.
So, try reverting to your original screen configuration and restarting the computer. If that resolves the problem, change your units to normalized or characters.
The Matlab proposal in Area 51 was closed as duplicate of "Stack Overflow", so I assume this is the appropriate place for this question.
Does the 2013a version of Matlab support retina display? I have 2012b and the plots and figures and pixelated looking.
I don't know about retina displays (I think that's a Mac OS thing, I'm on Windows), but MATLAB plots are not anti-aliased.
At least thats the case in the current version, it seems MATLAB is working on updating its graphics system to be AA by default.
There is an undocumented way to get smooth lines you can also play with.
Finally there are other tricks to get nice smooth plots (by drawing at a higher resolution, then subsampling and saving the image). Take a look at this FEX submission: myaa
It looks fine in 2013a but in 2013b it looks blurry. The reason is that the in versions before 2013b Matlab used the native mac java engine but since apple is abandoning this, mathworks is forced to use another java engine.
See here: http://www.mathworks.com/support/solutions/en/data/1-N0GH8T/
We've received the new Microsoft Surface v2 this week, and I've done something such that it broken the Surface Mode.
What should happen
I could double-tap the shortcut to Enter Surface Mode, say ok to the dialogs that popped up, and it would take me to the SurfaceLoader (a program that just shows a ring of particles pulsing in an out of the center). After a moment, the water-simulation Attract program would pop-up, where I could touch the center surface logo to see the list of registered Surface programs.
What happens instead
I double-tap the shortcut to Enter Surface Mode (turning on debugging), and nothing comes up past SurfaceLoader. It seems that the other programs are running, but SurfaceLoader is aggressively maintaining focus.
What might have messed things up
Installed my Surface 1 Application
Made my Surface 1 Application run on startup
Installed Surface SDK Samples
(Maybe) accidentally moved an important file elsewhere - (just because its so easy to accidentally moving things on the Surface in Windows 7 Touch.)
Let's go over each of these.
For my Surface 1 Application, built in XNA using the Surface 1 SDK, we used an .msi installer to install the program. It ran, but being that Surface 1 is built around a small program called SurfaceInput.exe running in the background, the program did not respond to input. The program was run at startup through a registry key.
I have uninstalled the program through the control panel (double check this)
I have double-checked the registry to make sure the keys are not still there
For the Surface SDK Samples, I got them from the Microsoft Surface 2 SDK at: http://www.microsoft.com/download/en/details.aspx?id=26716. After installing the SDK, I navigated (on the Surface) to C:/Program Files (x86)/Microsoft SDKs/Surface/v2.0/Samples/Surface Code Samples.zip. I extracted the zipped files, and installed them with InstallSamples.bat. Installation succeeded normally.
At some point, I was able to see a list of these in the Surface Application Launcher screen. I can no longer get to that point, so I'm unable to exactly recreate my steps.
I'm not sure where these examples extract to - the placement does not seem to be contained in InstallSamples.bat file, and I cannot find them with Windows Search. Perhaps they are built in the same folder and merely registered elsewhere with the Surface, but since then I have done a series of System Backups. When examining the Surface Configuration Editor, BingSurface is the only Application registered with it, leading me to believe these are probably not the cause.
Finally I may have accidentally moved some arbitrary file to some other directory. This does sound rather horrible of me, and while I don't recall an instance where I've done this, it is incredibly easy to accidentally move a file or folder when Surface is in Windows 7 Touch mode. Even while writing this, I somehow moved the taskbar from the bottom of the screen to the top of the screen while it was locked with just two touches. I don't think this is the problem, but its easy enough to do that I can't rule it out either.
To remedy this, I have tried Windows System Restore. I was able to restore to a point after installing my Surface 1 app, but I have tried twice to Restore to the original state of the surface without success. I waited 10-20 minutes for System Restore to show progress, and both times it stayed on the Initializing screen. It was not graphically frozen, as the Windows loading circle was spinning, but from my previous experiences 20 minutes seemed to be way too long for this process to be going correctly.
Things that do not work
Running Enter Surface Mode w/ debugging - eternal loading screen. Can alt+tab to see Attract is running, but does not switch focus to Attract window. Can hear the sounds of Attract play when I touch the surface on the loading window.
Running Surface Shell - eternal loading screen. Can hear the sounds of attract play.
Running Enter Surface Mode w/ debugging in Single Application Mode set to SurfaceBing - eternal loading screen. Alt+tab reveals its running, but does not switch focus to bing window.
Running Surface Shell in Single Application Mode set to SurfaceBing - eternal loading screen. Alt+tab reveals its running, but does not switch focus to bing window.
Running Surface Loader - running it directly causes same problems as above.
Things that do work
Compiled Sample Project RawImageVisualizer on separate system - runs great on the surface. Can see what the pixelsense is seeing.
Launching Bing for Microsoft Windows Directly - works just as it should
Launching Attract directly from C:\Program Files (x86)\Microsoft Surface\v2.0\Attract - watery program comes up just as it should.
Environment Lighting Optimizer - works totally fine.
It seems like something happened to SurfaceLoader, such that it thinks it should always be on top of everything. I shall give System Restore another go, allowing it a full hour. I will also double-check the properties of SurfaceLoader to make sure it doesn't have anything akin to "run on top" checked.
I know Surface 2 is new, but I would greatly appreciate any tips you have.
You've probably figured it out by now, but for posterity's sake, I'm guessing you didn't have permissions set correctly. You should always run the Surface Shell/Enter Surface Mode as Administrator or set the properties to always run as admin. Your own programs always need high level permission. If you don't run as admin, it seems to raise the alert window you get when Windows7 asks for higher level permissions but you never see it. It just waits and waits. "Surface Mode" is actually just a special user that's hidden until you enter it and never runs Windows Explorer or shows the desktop. So you have to deal with Windows 7 permissions to have programs run for both users. Hope that helps!