I really like how IntelliJ displays the information of the type of parameters that you are required to fill in as you are writing the code. The problem is that this info sometimes disappears if u click somewhere to check something etc. I never quite know how to get it to display that information again in same fashion. So I always spend some time to fiddle around until it displays that info again in the same fashion. I know you can hold down on ctrl and hover over the method name to bring up parameters information but its not quite the same and it then does not highlight on what parameter you are currently on. IntelliJ also brings up required parameters type of information when you are starting to go wrong. It brings up this big separate box and you can get very clear view of what needs to be done. I've taken a screenshot of the type of information that I'm on about. Both of them are on the same pic.
Please check it out.
My question: is there a way to bring this information up via keystrokes or mouse input at will? I've tried to google for an answer but I haven't had any joy. Please advise as I'm sure someone else might like this information too.
Thank you.
PS. I know that a good code does not usually have that many parameters but in my case there is not much that can be done.
Default shortcut for that is CTRL-P when cursor is inside the brackets.
Whenever i go to a particular area it always teleports back to the center hallway.* Example:(https://www.dropbox.com/s/mye0k8n9ysua6cb/Video%203-29-2017%206-24-13%20PM.avi?dl=0)
I've tried deleting and changing a bunch of objects and I'm pretty sure it's related to the player
The code is quite interesting so I'll just link the project(https://www.dropbox.com/s/bmjj7fyxc5qasbg/Undertale%202%20above%20the%20underground.project.gmx?dl=0)
I am using game maker studio 1.4
You didn't explained your problem very well, however, if you used the Previous room event that might be the problem because it backs the previous room that listed not the one used.
and you can create an invisible object to teleport between rooms, for example;
create an object like level1_2 then create a sprite & collision box for it.
place it in the hallway then use goto_room(room_level2); with the collision event.
duplicate the object level1_2 and rename it to Level2_1
change the code to goto_room(room_level1);
this should cause no problem because it is the by far the most reliable time-consuming way.
So, I am planning on designing a dungeon crawler (like Nethack), and I was wondering how I could get the user's input for moving the player. I originally planned to get a character input (W,S,A, or D) and then when the user presses enter, the movement takes place.
However, now I'd like to implement this without the mandatory enter press, so that merely pressing W would move the player forward by one space. I don't really need syntactically correct code, just pseudo-code of a concept would suffice.
What is the best way to understand a complex LabView VI that controls a motor?
My goal is to control the motor from a joystick.
The wiring diagram shown below allows a LabView user to control the motor from the LabView GUI: move a slider up and down either increasing or decreasing the desired velocity. As the slider's value changes, it is fed into a bunch of math controls and eventually gets converted into a command string for the motor to interpret. This command string, if I understand correctly, is bunch of bytes that get written to the serial port.
Instead of using the LabView GUI to control the motor, I would like to use the joystick.
What is the best way to approach this?
The joystick has pitch,yaw,roll,and throttle. Which one relates best to the velocity of a motor?
The answer to your title "What is the most efficient way to quickly understand how a complex LabView VI works?" is probably to do some combination of the following:
Look at the VI's inputs and outputs to try and understand what they are there for. The label and caption of controls and indicators may be helpful, also right-click to check the description and tip.
As well as controls and indicators, look for other I/O: queues, notifiers, global variables, file read/writes, instrument communications, and for any data storage that persists between calls such as an uninitialised shift register.
Look at the overall structure of the VI to see how it executes, e.g. is it a one-off operation, does it execute different cases depending on some input, does it loop until a certain condition happens, does it use a state machine structure, etc
Break down the VI's structure into smaller pieces that you can understand. You could print the diagram out and annotate it by hand, or add frame decorations and text comments to the diagram to record what you deduce. If the diagram is cluttered or poorly laid out, rearrange it as you go along (use Ctrl-click and drag on the diagram background to add blank space where you need it).
Set probes on key wires and watch them while the VI runs to see what happens
If possible, manually set the VI's controls to example values and run it to see what happens (this may not work if the VI depends on other parts of a program running at the same time)
Write a test wrapper VI that calls the complex VI and supplies it with example data or inputs to see what happens.
To address your specific question about the VI diagram you've posted, I can see various controls for quantities such as Velocity, Position, Amplitude, Max A (amplitude?), Frequency and so on. You need to decide which of these quantities should be controlled by which axis or output of your joystick. Then you need to add code that reads those values from your joystick, and modify the existing code so that the parameters you want to control are supplied by the joystick values instead of the front panel controls. You could probably just put the joystick reading code inside the existing loop, wire the joystick outputs to join up with the wires from the front panel controls you want to replace, and then change the relevant front panel controls to indicators from the right-click menu so that they will show the values you are getting from the joystick.
The best way is to write one from scratch. But you could analyse the code by clicking the Highlight Execution button to display an animation of the block diagram execution when you run the VI, and use probes to check intermediate values. And you probably should also do an on-line course, e.g. LabVIEW Training: Learn LabVIEW in Three or Six Hours
My answer to your third question is "throttle.".
I was wondering if its possible to customize the behavior of IntelliSense in VS 2012. I also have Resharper installed if that can do it. My desire is to minimize the amount of movement of my hands from the core keys. Typically when IntelliSense comes up I start typing and it narrows the list down to say 3-4 items. Then I need to move my right hand to the Down Arrow Key. I was wondering if I could use the Space key to cycle through the short list of 3-4 items and then hit Enter or ; to select the value I wanted. I can always keep typing the item I want but sometimes that will take 6+ keystrokes since the names are similar. Anyway just wondering as I would think that would be an improvement in speed.