Anylogic showing "event loop exception null" when I change the time unit after inputting the number - anylogic

This appears every time when I add a block and want to change the delay time. At first I input the number in the field in the rectangle, and then when I click on the time unit option in the circle, I will get this "event loop exception".
If I change the time unit first and then the delay time, the change in delay time will not be saved and I have to change it again. I have no clue why this happens.
I'm using Macbook and the Anylogic version is the newest.

This should not happen and it may be related to the Mac version. Make sure you run the latest AnyLogic version, obviously.
In addition, delete your Workspace folder, sometimes this solves these kinds of issues (back it up, of course).
On Windows, you can find it in C:\Users\MyUserProfile\.AnyLogicProfessional\Workspace8.8, but you should be able to find the equivalent location on your Mac :)

Related

VSCode annoying problem focus behavior, keeps jumping to a problem

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.

Constant error: "A setting has changed that requires a restart to take effect"

"press the restart button to restart Visiual Studio Code and enable the setting."
Now Im going to preface this by saying that this is quite possibly the most annoying thing I have ever experienced in my years computing.
I'm new to VS Code and as such I am knee deep in my settings.json a lot of the time. Especially moreso when Ive just installed a new extension and it comes with loads of parameters, alnd all sorts of goodies - sort of like I did today when I got home from work.
I open settings.json. I add a comment line indicating a new section for my new extension's myriad of settings I half understand, and move any auto-generated config settings from the bottom to the freshly minted position. I start typing, the widget pops up letting me know about all 70+ settings I can fiddle with as much as I please.
I hit tab on the first entry, it goes down. Tab again, "true" goes down.
"A setting has changed that requires a restart to take effect"
OKAY no problem VS code. Quick restart, back to my config.
I start typing the extension again, I get 200ms in or however long it takes for that widgit to appear, and
"A setting has changed that requires a restart to take effect"
I watch the text in my editor contort as the settings are unloaded and reloaded and unloaded again.
I got the first 4 characters of the extension name typed out before this lovely notification reappears.
Now,
when this happens a few times its a little irritating.
BUT THIS IS CONSTANT .Every. Single. Line. I try to add. Each and every setting. Sometimes 2 or 3 times before I actually get the string down, never-mind its value.
I don't know what to do, I am legitimately going to rip my hair out. This is by far easily up there with one of the most frustrating things I have ever been forced to endure. It is relentless.
I dont know what else to do. Ive tried all I can think of.
I just want to learn and use my new extension.
Please for the love of anything help me.
Please.

Xcode stopped showing predictions

I use Xcode 4.0.1..Suddenly I noticed that my xcode stopped showing predictions...(for example if I use the name of the button and after that it use to show all the property of the button such as enabled,hidden etc)...My Xcode isn't showing any predictions now, it leads to some errors and consuming long time with out these predictions..Where I want to change this settings?
Sometimes exiting XCode and restarting clears up strange behavior like this. Also, Mac OS X needs a reboot from time to time. Unfortunate, but true.
Could it be that you haven't imported the correct class(es)?
I have this problem when I get the compiler confused -- like during a refactoring and a large block of code, protocol names, interface properties, etc. are being changed. I will clean and compile -- allow the errors, then it starts to work again.
Also, if I have unbalanced braces, brackets, parenthesis, etc. that precedes the code I am working on, then it will stop autocompletion. As soon as I balance the statement(s), it works again. Sometimes, I have to clean and recompile.

why are my eclipse code error labels lagging

so when you make syntax errors, etc, eclipse will automatically put in an x button on the line number and then when you fix the error, that x button is supposed to disappear
normally, it should disappear right after the error is fixed, but in my case, it would disappear for up to 5 seconds after the error is fixed which is abnormal
anyone knows why this is the case?
The behavior your describe is not abnormal. Validation is expensive and if done completely in realtime would bog down your actions (like typing). Instead, validation tasks are queued and are typically executed during a pause in keyboard activity. If you type energetically, you will notice that the validation doesn't update for quite a while. The exact experience will also vary with the power of your computer.

iPhone -- Hunting Line of Code Being Executed

I am working on an iPhone project containing a ton of code. The application receives outside requests and performs actions. However, I cannot figure out exactly where the app begins executing code for a particular event. Is there some functionality in Xcode which would allow me to solve this problem?
Thank you.
Have you tried setting break points in your code? Click on the line numbers column in Xcode on the number to set a break point.
Without knowing more about what these requests are or where they are coming from, its hard to give any advice on what tools Xcode might have, but looking in any project files named <xxx>AppDelegate.m or <xxx>Controller.m would be a good start, placing breakpoints on likely sounding methods.
I figured out that you can use the Instruments Profiler to this end.
Start the profiler
Choose "Time Profiler"
In the bottom left section make sure the following are checked: Show Obj-C only and Hide System Libraries
In the timeline, click on the the point before the event occurred.
Click the left-most icon in "inspection range" (located on the top-bar immediately to the left of clock)
In the timeline, click on the point after the event completed. (optional)
Click the right-most icon in "inspection range"
Inspect the Call Tree.