I was adjusting some columns on a master/detail form and the detail interactive grid stopped retrieving rows. I'm not sure at what point exactly that it stopped working, but I think it was when I was using the quick edit to adjust the height of the region.
I tried putting everything back the way it was, but no luck. I added another interactive grid on the same table, linked by the same column to the master, and that works ok. I tried exporting the source and comparing the non-working grid to the working grid, to see if something was messed up in the source, but I don't know enough to figure out what differences are significant.
Any ideas on what might have happened? How I might be able to fix it, or at least avoid having this issue in the future?
I switched the interactive grid to an interactive report and saved it, then switched it back to an interactive grid again, and that seems to have resolved the problem.
Related
I had my app working just fine a few days ago and then I noticed the first problem. I had to tap twice in order to make a button go to the next screen. Also happened to the checkBoxes. Had to tap twice to make them change.
But now it got serious. Since yesterday when I tap on a TextField the app freezes and then crashes.
The only significant changes I remember I did were 2: I uploaded an image for the App Icon and I edited the TitleArea UIID. I removed the TOP and BOTTOM margins. It also affected some of my label and button UIID, because now they don't show on the device
When I run the simulator, the doble tap also occurs, but the TextFields work fine and the Button and Label UIID look the way they should.
Any ideas why this happens?
I am right now working with old versions to try to determine the reason, but no luck so far. Thanks
Use a solid color rather than a gradient with the same colors. Gradients are slow and problematic across platforms so you are paying a lot for something that you aren't even using.
We'll need a better test case to reproduce crashing, I think that what you initially saw when you submitted the issue was a regression in the text input that we since resolved in the build servers.
I've been searching the web for over 2 days now for a good and easy to use something to print reports from a WPF application.
I've been trying to use the DocumentViewer but it's a pain to add Controls to it and style them. Is it me or can this only be done in code behind and how can a grid over multiple pages dynamically be generated?
Second I found the control FlowDocumentReader. This looks like an interesting thing since you can add Tables which are much easier to style and I was able to do this in xaml. Unfortunately, I have no clue how to print from it. I tried to edit the template of the reader but without success.
Last I found this post (What's the best approach to printing/reporting from WPF?) but it's dated to 2008 so I'm not sure if the information is still accurate.
My conclusion is that it is pretty hard to get a nice looking report printed from WPF without writing lots of code behind or editing templates which (by me) fail to do what I want.
So my question is, is there any good approach to my problem? I'm really bothered that I lost this much time for something that I thought was so trivial to do.
I was wonder, what about this guy's approach: https://stackoverflow.com/questions/17647939/how-do-we-handle-different-printing-needs-by-using-fixeddocument?rq=1?
Crystal Reports is indeed a good choice for complicated reports but if your reports will be simple in design I'll recommend using CodeReason reports, it's an xaml based reports. Too bad it's not updated anymore but it's really easy to use for simple reports.
For more information: http://wpfreports.codeplex.com/
I have a windows form that keeps resizing itself in design mode after running the debugger. Before running my application, I've checked the size of the form in question and everything looks perfect. Then when I run the program, exit, and look at the form in the designer, the form has automatically shrunk itself...in the designer. It isn't a huge difference, but it's enough to irk the ever-living crap out of me as panel borders get cut off when this happens and it just looks bad.
Does anyone have any ideas on what may be causing this? It's not autoscroll, and the form is double buffered with a fixedsingle border. It's also locked, and the size of the form is definitely not larger than my screen. There doesn't seem to be much of a pattern to when this happens. Sometimes when I run my program, it doesn't resize itself, other times it does...but again, it's resizing itself in the designer which I find pretty weird. Would love to hear some thoughts on what I may be overlooking.
I'm somewhat new to WPF and VB.Net (but not new to programming in general) and I was wondering if someone could help me with an issue that I'm having.
Here's the problem:
I am creating a simple form using WPF in VB.Net and I have a button that I want to disable or enable based on an update to a DataGrid that is located in the form. When I first show the form the button is enabled by default and everything is fine. When the DataGrid changes I can disable the button programmatically by doing btnTest.IsEnabled=False and the button grays out appropriately. However, when I subsequently call btnTest.IsEnabled=True the button becomes enabled all except for the text that is displayed on the button; that text remains grayed out. I can switch back and forth between enabled and disabled several times and the behavior described still manifests. I'm not sure if I'm missing something but this seems to be a really simple problem to me and I've wasted a few hours on it already.
Does anyone know what's going on? I've already googled everything I know.
Thanks
Tom
Just to update this: I actually found out that this was a bug in the BureauBlue theme that ships with .NET. If you have this problem tag me in a comment here and I can send you my modified BureauBlue.xaml file.
A while ago I created a drag-over check box list which allows you to check many check boxes in a single gesture. Do you think it is viable and usable on the web where people might not know how to use it. The default behaviour still works for the individual check boxes.
1 - The idea
The idea is nice and can probably be used in professional applications where you have direct contact with users and can explain them how things work, but not necessarily on public websites where users don't want to RTFM and are just looking for familiar behaviours. Unless it was just a sample exercise or a control meant to be included it in a control pack, it violates the YAGNI principle ;)
2 - The implementation
You certainly noticed that the implementation is buggy (at least on IE7 and FF3.1B2). Sometimes, a gesture above all checkboxes will select all of them but one or two. Moving the mouse over the div's above or below the list will stop the drag (I know it's a "feature", but it's not very user friendly). I Checked the source code and to be honnest, while it looks pretty neat, I just didn't want to deal with it because it is plain javascript. Don't you know that...
3 - Possible improvements
...you can write less and do more with a javascript library, typically jQuery. I would completely rewrite this control as a jQuery plugin. It will provide you with a lot of tools to make your code much easier to write, maintain and extend. Just try it, you'll love it. This is from a technical point of view. From a user point of view, try to make you control as familiar as possible, like what Angela suggested, windows explorer : a nice selection rectangle, the ability to use shit + click, or something like that. Finally, remember that for many windows checklistbox users, "selected" and "checked" are two different things.
The demo definitely needs a few enhancements to make it even a little bit useful (although I am not sure if it would be enough):
Allow the dragging to start somewhere that is not a check box.
Allow selection by dragging over the labels as well.
This problem seems similar to the action of selecting multiple files in a file explorer like Windows Explorer. Maybe it can work like the action of selecting multiple files by dragging a rectangle shape around the items to be selected (select one corner, drag to the other corner)? This has the advantage of being similar to an interface element that people may already be familiar with.
For some reason I can't open your link (it says my ip address was blocked). But I think what you're looking for is what I already did in jquery, I uploaded a plugin which I basically ported from crossbrowser.com's dragcheck functionality, it was to be found at http://plugins.jquery.com/project/dragCheck but currently the jquery plugin site is being revamped and my plugin has disappeared. I'm trying to see if they're going to put it back up or if I have to create a new project again...
Anyways until we get that worked out you can see a demo here: http://jsbin.com/ibihi