I don't have much experience with simulink but everything was working fine until the symbols inside the blocks (integrator, merge, unary minus...) dissapeared and now it is just a white square (they continue working tho). I haven't modified the format or similar that I can recall.
I have also tried to delete those blocks and import new ones from the library browser but the problem persist.
How can I fix this problem?
PD: I can't upload an image sorry :((
I had a similar problem in the past, I used the next commands in the command window.
restoredefaultpath
rehash toolboxcache
It will take some time, but might work.
Related
That's all, sometimes I miss I could do that while working on different parts of a kinda long script or whatever... So I think it'd be nice if, as we can do in a spread sheet by fixing a row for example, we could quickly define certain part of the code we want always visible and then can scroll to any other part of the script while still being able to see such "fixed" lines of code as a reference, copy, etc.
It seemed to me that it could be an already existing feature, but I've been not able to find anything... not even an extension, but maybe someone here knows? Well, I hope it makes sense and thanks in advance!
How about spliting the editor?
Hard to guess for how large "sticky" portion of code you are actually aiming, but if it is just, say, function "signature line" or nesting header in general, you may try experimental "Editor sticky scroll" (editor.experimental.stickyScroll.enabled) feature that was just released in VSC v1.70:
https://code.visualstudio.com/updates/v1_70#_editor-sticky-scroll
This happened suddenly after I restarted my computer, all of a sudden any code I type is highlighted in red. Does anyone know how to fix this? See image.
OS: Windows
UPDATE:
This is the weirdest thing, I simply restarted my computer (again), and it just disappeared. It's a shame, because I didn't get to figure out how it happened, but it's good to know about this Bisect feature in VS Code!
This might have something to do with one of your extensions acting up.
VScode has a nice feature to help you find the specific extension that's causing problems without you having to check each one individually.
VScode bisect function.
Press crtl+p then type bisect
It may be one of your extensions that makes this. You can check it by disabling them one by one(ctrl + shift +X and then choose installed). I guess maybe an extension that belongs these:enter image description here.
Hope helpful.
Last Edit:
It appears I've had an F8 key being pressed non-stop, and it seems to be a shortcut for "Go to Next Error or Warning".
I've wrote a piece of code, it has an error which I'm aware of. Specifically, I'm trying to run a function which doesn't exist yet:
All good, I'm glad it is telling me there's a problem, but... I wish to keep writing stuff in the same file and I simply can't. Every so often the GUI keeps sending the caret (the place where my next piece of text will be written) to the beginning of the problematic piece of code. Simply speaking, I can't keep doing anything until I resolve the problem, since it forcefully intrudes my every action. Even more than that! When I go to a different file, with means of fixing the problem and adding the missing function, it once again interrupts me and forcefully takes me back to the problematic file to show me that there's a problem (??!?!?!). Closing it with "Esc" only closes it once, but it keeps on returning every several seconds.
I don't think it was like that just a week ago, and I didn't install any new plugin since then. I'm currently using the last version, 1.58.2.
How do I stop this work-flow-intruding behavior?
Edit:
I've kept on working for some time and it turns out the issue is much bigger than that. Whenever I type a name of some property, half way through some wild problem would jump and tell me "Cannot find name 'quar'. Did you mean 'quarter'?". The issue is basically the time delay of the problem checks, it's non-existent. It's also too intrusive, moving the caret and jumping between files to show me the existing problems. It's very recent, it didn't happen earlier this week. I've tried disabling different plugins I have and they're not the cause.
This is not exactly your issue, but could be related to what you are experiencing: https://github.com/microsoft/vscode/issues/68776
Try disabling the Outline Explorer and see what happens then.
Furthermore, see if disabling autosave improves anything.
First and foremost: I'm still an emacs noob, so please consider me misunderstanding things.
I'm currently experience weird rendering errors when using child frames in emacs. This problems is consistent over many packages. Whenever a package creates a child frame, it get's rendered poorly.
Example using company-box:
Another package I've the same experience with is lsp-ui or specifially lsp-ui-doc. For the sake of making sure no other package is causing this I'm using this minimal setup. The artifacts still remain:
To me it looks like that the size the child frame should have is the portion thats being displayed + the black artifact (or grey in the lsp-ui pictures. But somehow it only displays a portion of the content correctly and blanks out the rest. You can see that the actual content in the portion being displayed is cut off.
I have to note that this doesn't happen 100% of times. But about 80% I guess. Sometimes the frame is displayed correctly.
I have absolutely no idea what is causing this. One thing that might be of interest is my setup:
OS: Windows 10 (using WSL)
Emacs: 26.3 (running in Ubuntu 18.04 LTS)
X Server: VcXsrv 1.20.5.1 (But I've also tried Xming 6.9.0.31 - same result)
I've trouble finding any information about this online. There's at least one person having the same issue using company-box. He's also launching emacs using wsl and VcXsrv, which makes me think this may be related to WSL/VcXsrv.
I'd appreciate any help.
for anyone who is experiencing the same issues - I have found a solution.
The problem is VcXsrv/Xming. Details about this bug can be found here.
The solution is to switch to another Xserver. I'm currently trying MobaXTerm which doesn't have that problem. However there might be other, better alternatives.
However it's good to have found the culprit in this case for anyone who is facing the same issue.
I just set up Eclipse for PHP Developers on a new machine, and now I have a problem I haven't experienced before.
Normally, I keep track of short-term work that I want to do by adding TODOs in comments on a file. These show up on the right side of the editing window as little blue rectangles. This helps me find the next thing I need to work on.
That part is working, but when I remove the comment the blue rectangles aren't going away. I have used Eclipse for years and never had this problem before.
Anyone know why this isn't working?
For tasks added in the source file's syntax, you often need to Clean and Build the project again to reprocess the file (those are handled in the relevant compiler). For ones that don't get "compiled", check the General->Editors->Structured Text Editors->Task Tags page and have it try to redetect them from there.