Hi guys I have a very weird issue in MVVMCross right now.
I'm trying to close a page by using navigationService.Close(this), but it doesn't close. In the logging I'm seeing the following message: Ignoring close for ViewModel - Matching View for ViewModel instance failed.
I checked on Github where this message is thrown and it is exactly what it says it can't find the view which needs to be closed. But now the weird thing: If I just change the presentation to Modal (which I don't want in this case) the close command just works.
Is this a bug? Am I doing something wrong? Can anyone help me?
Maybe it is because we have a TabbedRootViewModel in which the navigation is done?
Fixed it (somehow) by setting WrapInNavigationPage = true in the TabbedRootViewModel. This did give some other issues like a double navigationBar. Which I fixed by turning off the navigationBar in XAML. So it's not the ideal solution, but it is a solution :)
Related
I am very new to MVC/Kendo, I have a series of tabs like so:
However when I add an icon to the emailing tab a bar appears under all the other tabs:
Could anyone advise as to why this would happen?
Many thanks in advance.
So I have provided a sample Dojo for you which should hopefully help https://dojo.telerik.com/OsIhINOy/4
What I suspect is happening is that you are not applying the k-state-active to the selected tab when clicked which is why the line is still appearing. (you can see this by just deleting the k-state-active class from the first tab.
If you are able to provide a sample of your code in the future it will help in assisting your question better rather than images as it is difficult to tell what may be happening from just an image.
Can anyone tell me how is it called, what is its purpose and how to hide it, please?
I believe that's part of the version control system.
Clicking the little "person's head in a circle" icon should close it.
Finally I got that. This is related to test coverage functionality and as you write unit/ui tests the right side with that red part appears. This has nothing to do with the vcs.
When I open xcode and create layout everything looks pretty much like it should (meaning that the storyboard view controller looks pretty much like the preview)
But when I close out of xcode and re-open it... the view looks like this. This is concerning not just because its difficult to work on, but also because it seems that the storyboard file knows these aren't where they should be. If I click on any individual element it is looking for me to update the constraints for this new layout which is completely inaccurate.
I've tried moving all the items back to the middle, and re-laying out the whole thing, but this takes about 5+ minutes each time I want to make a change. I'm wondering if there is a way to reset the storyboard back to what it should be, or if there is some setting that I have wrong which would result in this change. Any help would be greatly appreciated!
UPDATE!
Ok so I discovered now that I can "Update Frame" to fix the layout. Still not sure why the layout is getting messed up in the first place.
That seems like a bug in xCode 6.1.x (prior to v6.3.xx), which was resolved in a meanwhile.
Here is the official reference :
http://adcdownload.apple.com//Developer_Tools/Xcode_6.3_beta/Xcode_6.3_beta_Release_Notes.pdf
Definite solution of this problem :
You need to update xCode to v6.3 which successfully resolves this problem
I think i've found a problem with kendo panelbar.
In my project i have a kendo panelbar and sometimes i need all items to be disabled.
The problem is that when all items are disabled and you click anywhere inside the panelbar it raises a javascript error. If you click outside and inside again it raises another. I performed some testes and i guess it may be something related to the fact that kendo panelbar try to put focus in the first enabled item whenever you click in a disabled item.
I thought it was something related to the scripts i have in my project, but i found that this error also occurs in the official telerik panelbar example, but you have to open console in developer tools to see the error because the example runs in a frame of the telerik dojo. You can try it. The link is http://dojo.telerik.com/aXoni
I tried google but didn't find anyone with this problem.
I think its strange no one ever found this bug. Am i doing something wrong or is this really a bug in the telerik panelbar and i have to live with it?
Thanks
This definitely seems like a bug so I went ahead and reported it: https://github.com/telerik/kendo-ui-core/issues/307
In the meantime, you can hack around the problem with a mousedown listener during the capture phase: http://dojo.telerik.com/#tjvantoll/OdIj. It's a bit ugly but it'll avoid the error.
The problem: In VS2010, I have a form with a broken design view. It's breaking on a couple of Atalasoft imageviewer controls.
The weirdness: Took me some time to figure this out, but if I go into the forms designer.vb file, and comment out everything regarding these controls, save, uncomment, and save again, the form design view loads perfect. NOTE: I'm not changing anything. Just commenting/uncommenting portions of the designer and saving.
The form design view continues to work fine until I do any of the following:
close the form design view and the designer.vb file and try to view again.
close the solution and reopen.
After doing either of these things, it's back to square one and I have to comment/uncomment/save to view the form designer again.
I'm on Win7, 64 bit. I have worked on this app in the past with no issue. The app builds and runs just fine. It's just a VS form design view issue, and I'm flummoxed.
I'd love to hear any thoughts on how I can solve this. If I can provide any more specific info, please let me know.
I've seen this happen rarely, when something odd gets into the designer file for a form and the designer can't figure out how to display things anymore. A third-party control being part of it could be indicative of some bug with that control's designer-related code.
One thing to try might be re-creating the form in question from scratch, and see if that fixes it. Perhaps something inadvertently got fubared. Also see if there is anything out there with others having designer problems with the same control(s) in question.
Sorry can't offer more direct help; maybe someone else has experienced something more closely related.