Breakpoints and Code Completion

Enjoyed your interview on .Net Rocks!

Breakpoints were mentioned during the interview. I’ve noticed that I can’t always set a breakpoint. In one method I had to move the first line of code down a line from the method declaration before I could set it as a breakpoint. In another method I couldn’t set a breakpoint at all. Both methods were () -> Bool in a WPF window code-behind file. Am I wrong to think that it’s probably too early in the Beta process for this to work? I also noticed there is no code completion. Again, I’m thinking that perhaps it’s just too early, or will code completion not be supported?

I was able to create a working Tic-Tac-Toe game. Next I’ll try for something more ambitious like Renju. Thanks again for all you’ve done so far.

1 Like

Using VS or Fire? There was a bug in todays build that causes some issues with code completion (and breakpoints) but the next build should have it working perfectly again:

Code Completion can still be a bit flaky in some scenarios. Concrete examples will be appreciated when you run into problems, so that we can address them. “in general”, CC should be there and usable.

In Visual Studio 2013 Community Edition in a WPF application. An example: when typing “MessageBox.” there was no “Equals/ReferenceEquals/Show” tooltip. Another example: when typing “btnButtonName.” no tooltip showed. I didn’t have occasion to try it against native Swift types, so perhaps there is/was only an issue when going against Framework types?

I last used Silver on Tuesday night. If either problem exists the next time I’ll upload some screen shots. Thanks.

Installed 8.1.82.1723 this evening. The problems I had were in 8.1.82.1719.

Breakpoints seem fine now.

Code Complete is not always working as I would expect. “MessageBox” is tooltipped while typing “Message”, and all its methods are apparently tooltipped after pressing period, so that seems to be working fine now. Typing the period after the name of a WPF Button does not seem to tooltip anything but its Swift properties/methods.So perhaps the code complete works for static Framework properties/methods but not for instance ones?

Also, there seems to be no type information tooltipped for mouse hovering over a variable name, as happens in C# code in VS. Will that not be supported, or added in later?

Those should work, indeed. Could yo dome a favor and post (or email to support@, if it is confidential) the complete project?

thanx,
marc

I will when I return home, which won’t be for about ten hours or so.

1 Like

Something I just discovered is that in the Button_Click function the btn variable does have Code Completion work as expected. That is the variable set in this line

if let btn = sender as? Button

But in the functions below, directly typing the name of a WPF button, such as btnTL, only brings up the Swift options for Code Complete.

Here is the complete solution:
SilverTest.zip (199.3 KB)

Update:

The mouse-hover type tooltipping seems to be working with most everything but the WPF buttons.

Would it be possible to have code completion selected from TAB as well as ENTER?

In a different app I added a reference to the Sugar.dll but didn’t see it in the Object Browser. Is there any kind of API documentation on what’s in the Sugar library? Or is there a way I can inspect its objects?

Oh, I see there is some info here:
http://docs.elementscompiler.com/API/Sugar/
I guess either the documentation or the implementation is incomplete

bugs://71586 got closed with status fixed.

Bob, please, unset the system variable Platform. Remove folder \obj\MCD, in your project, rebuild and retest. Some HP computers have this set by default and it’s breaking MSBuild.

1 Like

I am running on an HP notebook. Following your instructions worked. Thanks!

BTW, it’s no big deal to me, but I was wondering if part of the implementation will include a Swift REPL, like F#? I could use SwiftStub if wanted to test some code really quick, but a REPL in the the IDE might be nicer. Just curious.

it’s not part of our current plans, but certainly something we’re considering long term,