I'm developing a plugin for custusX. I prefer developing on my own PC which is not connected to a tracking system.
For video, custusX uses a webcam to generate synthetic 'example data'. Is there also a tracking source with synthetic tracking data available that can be used for developing? (Preferable two different tools tools which move around all the time). If so, how can I enable it?
Currently if I try to access the tool configuration or to initialize tracking I only get Configuration file [] is not valid, could not configure the toolmanager. in the console.
There is a debug feature available:
Preferences->Debug->Run Debug Tool
This will create a tool and move it along a hardcoded path determined by the extent of the currently loaded volume. In order to work, this requires that you already have loaded a volume.
You should consider if you really need this. Alternatively, simply turn off the auto-start tracking in
Preferences->Automation->Auto Start Tracking
The auto-start streaming can also be turned off.
If what you need is to move the slice planes, note that the mouse also is a tool which always is present. this tool can be moved by interacting with the 2D views or directly in the Tool Properties Widget.
Another debug feature is:
Preferences->Debug->Debug manual tool
This will give manual tool the properties of the first physical tool (need to start tracking or at least run Tracking->Tool configuration). This can be used to move a probe or a tool. Will only allow you to move one tool though. To show the tool you will have to right-click in the 3D view and select "Show Manual Tool".
The manual tool can be moved by clicking in 2D/3D views or by using the "Tool Properties" widget. To change the tool orientation you have to use the "Tool Properties" widget (press the Toggle Edit Matrix button to open the tool controllers).
Combining this with "Run Debug Tool" (described by Christian) can give you two moving tools, one following a hardcoded path, and the other one controlled with the manual tool.
Related
Can anyone explain these three debug symbols on VSCode I have found on the internet?
My vs code has the one with the play icon.
All demos online on debugging have the one in the middle. How do I get that?
Also, node js debugging is installed but I think it shows as disabled, with no option I can find to enable it.
To answer your question directly [TL;DR]: you already have it if you are using the latest version of vscode. It will take you to the same view as the one on the right
If you look at the codicon libray ref the middle one you pointed out is not present.
Visual Studio Code made changes in February 2020 ref that incorporates running and debugging to be something more harmonious:
User studies revealed that new users have difficulties finding how to run their programs in VS Code. One reason is that the existing "Debugging" functionality is not something that they relate to "Running" a program. For that reason, we are making "Run" more prominent in the UI.
The main menu Debug has become the Run menu.
The Run and Debug view has become the Run view and the corresponding Activity Bar icon now shows a large "Play" icon with a small "bug" decoration.
So in other words, there is no difference. The 'Run' and 'Debug' view is synonymous and the icon reflects those changes. As they noted, the Debug view is now called the 'Run' view, but it still offers debugging and breakpoints.
There are 2 possibilities you are running into however:
The tutorials and guides you are using are out-dated (showing an outdated version of vscode)
The tutorial or guide is using an extension that offers debugging capabilities. Extensions have some control over the icon you see
The extension is for single file debugging, according to the June 2020 ref notes, vscode recommends the following:
For debug extensions that want to improve the single file debug experience by adding a "Run" and/or "Debug" button to the editor, we recommend following these guidelines for a consistent look and feel:
Contribute Run and/or Debug commands in the package.json (see Mock Debug):
Use the command titles "Run File"/"Debug File" or "Run Python File"/"Debug Python File".
Use the $(play) icon for Run and $(debug-alt-small) for Debug.
Where their codicon library was updated in June to reflect the following:
As you can see, none of them are prefixed with verbiage like 'run', but they all represent the same functionality.
Additionally, you may see this icon as well:
This represents the panel (view) where the output of your debug will go.
I am using Developer Studio 3.8.0 on top of Eclipse Lunar to develop an BPEL project...
I have able to create a partner link, assign the input message variable, and invoke the partner link.
however, I found out that after sometime, the message variable (the input/output variable used when calling a partner link) become un-expandable.
see the snapshot below
I tried to create a new message variable with the same partner link ( of different operation), and the message variable is expandable. (see shap shot below)
this is very annoying, because I am totally depending on the graphic designing iterface; and it become almost impossible to any job when complex composite variables become un-expandable in the GUI
anyone has any idea? or any suggestion?
cheers
WSO2 Developer studio is using the JDT UI elements in Eclipse platform[1]. However in some cases, JDT UIs are not working properly with lower window resolutions. In your attached screenshots, we can see that it has very low resolution.
So please try to increase the resolution first. If it is not working, edit your bpel with the source view. You can switch to the source view by clicking on the source view tab in bottom of your Gups.bpel window.
[1] https://www.eclipse.org/jdt/ui/
I am trying to create a single chrome app to display(by using 3840x1080 resolution) on both monitors.
when I try to move a window, from one monitor to other, I am able to see only half of the window on one screen. Is there any settings to make it work like extended monitors
This was apparently a limitation of Chrome OS.
Keyword was: this bug is marked as Verified (fixed) in May. However, see this comment:
Please note that this feature was developed for specific enterprise use case, and will always be behind a flag. In other words, this will not be on by default for general use.
You can enable it using about:flags starting from M44 though.
So, to use this, you apparently need to set the "Enable unified desktop mode" flag in chrome://flags/. I can't confirm since I don't have a Chrome OS device to test.
I'm new to Eclipse. I may need a better understanding or a plugin that would provide me with features described below. While doing some Android development, and I while making changes to my code at one point Eclipse warned me that this emulator doesn't support hot-swapping and if I want to disconnect. I'm used to see status in either the toolbar or in some log from Visual Studio. Is there a way to see this feedback in Eclipse?
My problem is that there are quite much implicit stuff in eclipse I would like get feedback of and control, like whether I'm
connected or not to a device,
if I'm attached to a process on it or not with debugger,
some kind of build log with a timestamp so I know it happened,
the automatic uninstalling and installing of the project on the device
which project is "active" ("featured") in "Run" and "Debug" buttons/configurations
Is there a plugin that can give me explicit commands over these automatic features? Like a toolbar or command. What I would expect of this tool:
be able to indicate the current status (eg. currently connected or not)
gives me control to eg. connect
gives me control to eg. disconnect
Preferably on a toolbar, as I know some of these are available as menu commands.
Furthermore I tried to configure my toolbar by Window menu -> Customize perspective..., but pin-pointing the features I want made my Eclipse put empty space up for the buttons I disabled, and next time I got to the same config screen it got the checkboxes wrong and displayed some stuff active what was actually disabled.
I have a GEF editor which represent a finite state machine. Editor's input (and output) is XML. What I am looking for is a way to debug my editor visually.
The way editor works is you create a state Start->Email->End, XML that is created is send to the server and there magic happens, of course Email object has properties that you set: from email, to email, subject, etc. What I am looking for is a way I can launch a debugger and step through each step of execution. So for example if I break at Email step I would be able to see what message was, whom it was for and what server returned at the end.
Is this something that is possible to accomplish and if so are there any articles I need to read to familiarize myself with how to create this debugger?
I found some discussion about Eclipse debuggers (1,2) but nothing about what I am interested in doing.
There are two different issues here.
One is writing a debugger engine, that manages the execution of your model, for example steps the execution, allows querying the variables/states, etc., and another one that outputs the result in your editor.
The articles you have linked work with the first issue: creating an engine that executes the model in the background, and integrates the engine into the Eclipse environment using 1) the launch framework to execute it similarly as Java programs, and 2) allows displaying the state in the textual editors.
You want to display the state in graphical editors. Because graphical editors have much less in common, the back-annotation of the debug state has to be done manually (instead of the generic support for text editors). Basically, I would create actions that set up breakpoints, and update the model to be able to store/query the execution state, and then update the GEF views to display it on the GUI. For this you have to change your Figures and your EditParts at least, and possibly other places as well.