Hi and thank you for reading.
I use Eclipse Debugging mode to understand some components of a massive Framework. Now I have something like Workflow A and Workflow B. I have set breakpoints in workflow A and understood how it work. Then I have set breakpoints in workflow B, but would like the breakpoints in workflow A to be there but not be called, so I can use them again at a later point.
What I would like to have is a way to enable all breakpoints in workflow A or workflow B without removing the breakpoints. Is there a way to do that?
Thanks,
evgeni
In the Breakpoint view menu (click the inverted triangle icon on the top right), look under the 'Group by' entry. You can use either breakpoint 'workingsets' and have a custom grouping or group by projects or files. Once you have a grouping enabling/disabling everything in a group becomes trivial.
Related
I have a number of breakpoints scattered throughout my code. I don't want to lose them, I just want to temporarily turn them all off so that the breakpoint I just added is the only one that is triggered. In other words, to have "active" and "inactive" breakpoints. Is this possible in Eclipse? I'm running Neon, 4.6.3.
In the run menu, about halfway down - there's "Skip All Break Points" - or you can do CTRL+ALT+B
Just don't forget to toggle it back else you'll be wondering why none of your breakpoints are no longer working - been there, done that.
Note and update as you wanted to only disable specific breakpoints, but still have some or a new one enabled. Too accomplish this:
Window->Show View->Debug Tree Node Select "Breakpoints" - this opens a view with all of your breakpoints. Select all of them, select disable - now select just the one (or two) that you want!
If you mean Java breakpoints, yes, you can just right-click on them either in the Java Editor or in the Breakpoints View and turn them on and off at will. Support in other languages is dependent on the language.
http://help.eclipse.org/neon/topic/org.eclipse.jdt.doc.user/reference/breakpoints/ref-enabled_option.htm?cp=1_4_0_1
The refactoring menu in Xcode 9.1 is completely greyed out. I wanted to extract a method from existing swift code and got the following screen:
Do I have to enabled something special to get access to the new refactoring features?
Try cleaning your Xcode. Also try clearing out derived data and restart Xcode.
Clean Build --> (Command-Option-Shift-K)
Delete DerivedData folder in ~/Library/Developer/Xcode/DerivedData
Refactor option hides if you select version editor.
Thanks #paul
I had to change to the Active Schema to the one that matched the Target Membership of the file I was editing.
In other words:
In Project Navigator, select the file you're editing
Show the Inspectors panel on the right
Show the File Inspector
Observe the Target Membership values and set the Active Schema (at the top, by the Build and Stop buttons) to match.
Select text, right click, select Refactor
Observe all the Refactor options are now enabled.
This happened to me too and I could not find anything on it so...
My first post is born.
Mike T. hit on a small portion above (incomplete syntax).
Nothing is wrong. Xcode is amazing! It seems the Refactor/Extract feature is pretty smart. The option is not available if it does not make sense to extract a method.
It may not make sense to extract a method for many reasons. Xcode disables the feature when it encounters them in the selection. A few that I noticed are:
variable declarations
a solitary print statement
continue statements in the selection but I don't include the for loop container. (i'm impressed)
my guess is that there are a bunch of conditions...
Small thing for me was that the code I was trying to access was inside a closure so when I was selecting it and right clicking to Extract to a Method, it was greyed out. removing self on both instances, I could then select both lines to then extract to method
self?.activityIndicator.stopAnimating()
self?.activityIndicator.removeFromSuperview()
Both lines were inside a closure for a UIAlertAction. So removing self allows you to extract to a method in this case. Then just call self on the extracted method inside the closure and it should work.
self?.hideSpinner() //extracted method name
As other posters have already said, its best to make sure you're able to refactor what you want by selecting the right code.
Is there a way to remove only the unselected breakpoints in eclipse?
The reason is so that i could easily remove those breakpoints that i'm not currently involved in.
I don't want to break my flow of concentration with choosing things that aren't near the things i'm concentrating on.
I could just then disable all and select only those that i'm interested in debugging while not forgetting which debugs mattered in this most current problem.
OR...
Is there an invert selection of breakpoints?
There is a 'Breakpoint'-View you could start with ALT+SHIFT+Q,B (or using Window->Show View->Breakpoints).
You can select, activate and even delete All/selected breakpoints.
If you are working at a specific topic, try using MyIyn, as you can even focus your breakpoints on the task you are working at.
In a multimillion line project, sometimes when searching for a bug, you can end up creating several dozen breakpoints. Often these breakpoints are searching for slightly different things.
Eclipse displays the class, line number, and method in which the breakpoint lies, but that's not always enough for me to keep track of everything. Sometimes I will know that there are a couple of specific things I want to look at, and I'll have a set of breakpoints digging through each of them. It would be really useful to be able to create breakpoint categories to help me keep track of where everything I want to look at happens.
I'm wondering if there is a way to do this, either in stock eclipse, or with a plugin.
Found it.
In the breakpoints view, open the view menu and select Working Sets.... This will allow you to create categories. Once you create a new working set and select the breakpoints to include in it, you can open the view menu again and select Group By > Breakpoint Working Sets. This will group your breakpoints into categories.
I know there are about a million questions on this topic, I have read them and they have been unhelpful so far. I am very new to eclipse so forgive me if I get things a bit wrong.
I have an eclipse project with some Lua files. I am using Luaeclipse to provide a Lua perspective and syntax highlighting.
I simply want to be able to do this:
-- TODO Implement this thing
And have it show up in the Tasks view. I know this is possible, but it just won't work for me.
Under Project > Properties, I have gone in to Lua settings and set the "Enable searching for Task Tags" checkbox, and I have double checked the the tags I am searching for are correct.
I don't know what else to do, this should be easy.
Edit
Here is what my workspace looks like, with the relevant settings shown.
Adding task tag in Lua editor didn't trigger adding task into "Tasks" view. I think it may be a bug of the eclipse plugin in Luaeclipse.
Declare that, i haven't used Luaeclipse. So, maybe you should check whether it support tasks tag in Lua editor firstly. The way to check follows:
You can open menu "Window" -> "Preferences", then filter by text "Task Tags".
If there is no "Task Tags" under "Lua"(Or something else), maybe you can't use tasks tag in Lua editor.
If there is, maybe you can try to trigger adding task manually.
You can set "Case sensitive task tag names" to be checked and "Apply". Then there will be a dialog to let you decide whether rebuild project to scan task tag, and select "No" (we don't want to change it really, just let its state change.)
Select "Restore Defaults" and "Apply", the dialog would pop up again. In this time, you can select "Yes" to let it scan tasks tag in your project to trigger adding tasks into "Tasks" view.
Hope what I supposed works.
Edit: Maybe, you can try LDT(Lua Development Tools), it works well.
Turns out my project wasn't in the build path... Adding it fixed everything.
Try to "touch" or "tickle" the lua file in question: Make any little edit (add and remove a space) then save it. If your scenario matches mine, the TODOs will magically appear.