I'm using Vaadin 6.8.9. Recently, I come across a issue. The table doesn't present properly as follow image. The headers are not able to appear. I tried to re-install tomcat7,and compile widgets couple times. The issue is still there. The issue only occur on my machine. I couldn't figure out the problem.
Could anybody have this issue ever? Give me some clues. Thanks very much.
Related
I use to work with VS Code and the Atlassian plugin for Jira. It have been working quite well since few months on.
Right now I'm not able to create a new issue, neither open an existing (assignated) issue, and create a branch from there.
did you experienced similar issue? how can I solve.
i've been searching everywhere but nothing cames out.
Any help apreciated.
Below is the Xamarin Forms solution but I have witnessed the same in WPF solution too. App.iOS project has blank configurations.
What's worse, you are not able to Add New ones by scrolling down and pressing <New...> - It does nothing. If you try to <Edit...> and remove/rename the blank ones, you get an error "The operation could not be completed".
I would like to remove blank rows, and be able to add new configurations using the <New...> button.
What I've tried:
Cleaning and rebuilding project
Rebooting Visual studio and PC
Tempering with App.iOS.csproj file, no blank data in there, nothing looked wrong to me.
So maybe this will help you. I had the same issue on my solution today and found your post.
I tried messing around with the sln file manually without luck.
My solution:
Since my project was x86 only I ended up clicking the edit in the Active solutions platform: dropdown.
I removed the items x64 and Any CPU. Then I went to each project and checked if it still had those two entries. Some did and I removed them. To my surprise when I then clicked the dropdown for one of the projects that had blank entries they were gone and so was the ones for the second project that had the blank entries too. Hopefully this will work for you.
We are doing some work around sharing UI across apps, both entire views and also individual controls, so the structure we end up with is (on Android):
Android App
View (Activity + Layout) pulled in from a NuGet package
Control (Layout) pulled in from another NuGet package
So the app pulls in the view and the view pulls in the control.
The problem we’ve seen is that resource IDs defined in the control’s layout don’t end up in the Resource.designer.cs of the app such that when the app runs we see a crash when FindViewByID is called.
Interestingly we have implemented the above in three different apps, it works in two and not the other, so I’m left thinking it is ever a difference in the build config somewhere or its pure chance and we can’t rely on this pattern working.
Has anyone seen this before?
Update:
Having paid closer attention to the build output I can actually see warnings being generated for the missing controls:
Warning XA0106: Skipping MyControl.Resource.Id.myId. Please check that
your Nuget Package versions are compatible. (XA0106)
Old question I know, but in case anyone needs it:
I experienced very similar problems after updating to Xamarin.Forms v4.1.0.581479, and followed James Esh's comment above, and JimmyGarrido's response here to get a resolution: https://forums.xamarin.com/discussion/89661/a-lot-of-warnings-appear-in-a-new-empty-xamarin-forms-xaml-project
The simple answer in my case was to remove the PCLAppConfig Nuget package. There may be other packages in your project which were built using an old version of the Xamarin.Android.Support* packages. Unfortunately I haven't found a way of diagnosing which package specifically causes the problem, so updating, then removing and retesting one-by-one led me to the solution.
Let's say before I check in, on the team explorer I right click on a file and compare it to workspace/latest version (doesn't really matter which, and the location neither, it's the same thing with code reviews, Changeset details->compare with previous) it will only show the deleted/red lines in the file, although it does show the added (green) parts in the scrollbar.
Have anyone had this problem before? I imagine a reinstall might just work, but I'd like to avoid it, if I can.
If the error is only occurs for your machine. It's more likely related to VS. Usually reinstall vs is the final solution.
You can also try the suggestion as Sachi commented, try to clear TFS and VS cache. This may do the trick.
If it's not work, still suggest you to reinstall VS. Even though this may not be a good solution. After all, it's very likely you have taken a long time to trouble shooting the weird issue and still can't find the root cause.
I recently changed from developing iOS apps on a MacMini to a new MacBook Pro (2.2 GHz Intel Core i7). While working in XCode, I occasionally get pop-ups when the system is apparently trying to do an autosave and runs into a problem.
The pop-ups state "The document [filename] could not be autosaved. The file has been changed by another application. Click Save Anyway to keep your changes and save the changes made by the other application as a version, or click Revert to keep the changes from the other application and save your changes as a version."
Examples of the filename are: AppDelegate.m, MyLoginViewController.m. There shouldn't be anything else that is changing those files.
I can't do anything within XCode until I choose one of the options. Sometimes it seems like the system is trying to overwrite my newest code with an old version of my code, sometimes it seems like it is trying to save my newest code. So, sometimes Revert is what I need to do to keep my current version, and other times Save Anyway is what I need to do. However, sometimes, I can't tell what the system is trying to do and I choose the wrong option and lose hours of work.
This has happened numerous times over a span of three weeks.
I am using OS X 10.7.2 and XCode 4.2.1. The code is on my MacBook's hard drive.
Does anybody have any idea why this is happening?
Thank you.
This is a huge problem, and it looks like it's Lion's force-fed "file-versioning" that is destroying work.
I typed quite a bit of code into my source and saved it regularly (pretty much after every complete paragraph). Suddenly I couldn't find an entire section that I'd just written. I even did a project-wide search, in case I'd accidentally entered it in the wrong file. Suddenly Xcode raised a dialog saying it couldn't autosave the file because it had been modified externally. Did I want to "revert", or save what was in the editor?
In the several times I've seen this come up on two systems over the past few weeks, I've chosen to save what's in the editor, thinking that obviously it must be the most recent version. WRONG. I hit "Revert", and the block of code reappeared.
There is so much wrong here, it's hard to decide what's the most offensive.
Confirming that this happens on XCode 4.3.2 on an iMac running 10.7.4.
I have found that this bug may be related to having the same file open in more than one tab or window in XCode. If you carefully avoid ever having more than one window open on a given file at a time I think you can avoid this problem. However, it undermines the very useful ability to apple-click method names to navigate to the file that contains them.
This has cost me hours of original work and been the source of immense frustration. The derisive comments from others are simply inadequate.
I heard they had a complicated fix for it already at Apple, but unfortunately, it was "accidentally lost" and now they can't remember which files need what changes to make it work again. :-/