gtk# window freezes when it maximizes - c#

I've created an application with Glade and GTK# in windows XP:
at startup window is not maximized
I click on "Search" and a listview is filled with data from a database:
image http://www.microline.eu/Capture-1.jpg
I click on maximize button the window freezes and does not respond
any suggestions?
Thanks
Added informations
On linux it works well
No code on maxime routine
My idea is that there is a bug in resizing procedure in GTK# for Windows

It's difficult to diagnose your problem without knowing what your code looks like - do you have any resize routines?
To solve your problem, I'd narrow down the potential culprits. Remove or hide one or more controls until you can find which control is responsible for the freeze on maximize.
Once you narrow down which control is causing the issue, determine whether it's the data in the control causing the issue. If it's the grid, see if the freeze still happens when there's no data in the grid.

If I change property Window position from Always center to None, then maximize works well.

Related

WPF controls hosted on Winforms application stop updating

I have a legacy Winform application (quite large and monolithic) where we now host WPF controls for the newer functionality.
After some interaction and updating, I get it into a state were all the WPF controls (only) stop updating. Ie if I set a property in the bound view model, the UI does not update. Also controls such as splitters and sliders do not work. Event if I invoke a WPF dialog, the radio button on it does not work.
All the Winforms controls work fine. It is although there is some WPF layer that has stopped functioning.
I have checked everything I can think of, ie everything occurring on correct threads, rendering in SoftwareOnly etc. Pausing the application, I see no locked threads, or anything else suspicious. I don't see any exceptions.
I am now at a loss on how to diagnose what is wrong here.
Does anyone have any ideas on how I can diagnose such an issue? Ie is there anything common like this that can occur with WPF on Winforms? I have never come across this before!
Thanks in advance for any help here.
[UPDATE1]
I just noticed, if I resize the WPF winforms parent container, THEN the WPF control updates..

C# launch form when images fully loaded

I'm making C# application design with images, but when I launch it, I see loading images (~1sec), so how to make simple loader, when images (background, logo, etc..) fully loads, to show my app? I know it's possible but I don't know how to. Thanks so much!
This sounds like standard behaviour. The controls get painted one by one in z-order and if one is slow the rest may appear to flicker.
You could try double buffering the whole form as shown here:
How to fix the flickering in User controls
Alternatively you could suspend the layout while everything is drawn and resume it afterwards:
How do I suspend painting for a control and its children?

Windows Message Pump pausing when clicking a Scrollbar control

I've set my XNA game's DeviceWindowHandle to a PictureBox with Dock set to Fill on a Form, effectively providing the powerful array of .NET controls to my game. I'm aware this comes with a handful of niggly things to clean up, one of which is my problem explained below.
I'm trying to figure out if it's possible to avoid the WM pump pausing when doing things like clicking to drag a ScrollBar control, or right clicking in a TextBox control, this ultimately causes my renderSurface (the dock filled pictureBox) to stop being drawn to temporarily. Information on this seems sparse, though it's likely i'm not looking in the right places.
I could tie in some custom drawn XNA ScrollBars and set ShortcutsEnabled on the .NET TextBox's to false, but i would rather fix the root of this problem if possible.
Thanks in advance.
XNA works by having a game loop. WinForms and native c++ Windows GUI apps work by having a message pump. Sounds like you have fused the two somehow.
Perhaps you need to call the base Game.Update() somehow from within your forms's Control.WndProc

c# Form not completely repainting in RDP session

I have a strange problem and I can't seem to figure out a solution.
I have a windows forms application written in C# .net4.0.
In this application, there's a panel where i draw a chart on.
This chart is drawn on the "Paint" event of the panel.
There's also a button which launches another application on top of this application which displays other information
All of this works fine, untill I close the opened application.
When I Close it, i see my first application again but parts of it haven't been repainted.
It seems that the panel with the chart repainted correctly, the rest of it's container panel didn't.
I removed the "Paint" event of the Panel with the chart as a test and then, everything worked fine (offcourse no chart was drawn)
Strangly, I only do have this problem when the programs are in an RDP session.
On my local pc, everything works/refreshes fine.
If anybody can help me on this, it would be very much appreciated!!
For clarity I have added screenshots below:
we have a lot of rendering problems on RDP too.
Try setting the values mentioned here:
http://blog.tedd.no/2011/04/28/optimizing-rdp-for-casual-use-windows-7-sp1-remotefx/
Also we have implemented additional refreshes when using our application over rdp, although weird, it seems to help. We haven't found a really good and clean solution yet.
You can also alter RDP behavior in the options menu when you start the RDP session. We are using transparency, for example, and had to turn of bitmap caching.

tooltip appearing behind the form/window! (C# / VS 2008)

For some strange reason, my toopltip in the VS 2008 C# winforms application shows up behind the form! It's very frustrating and I can't figure out what I should do. Anyone face this before? Ideas?
(PS - I'm doing a toolstip.show programmatically within the form)
There are a few things you might want to check:
Make sure the tooltip knows what its parent window is.
Make sure the window the tooltip belongs to is in the foreground (no, this isn't a requirement for displaying tooltips, it just helps debug.)
Try giving focus to the owner of the tooltip. If that fixes the problem, then there's probably an ownership problem with your tooltip.
Try bringing your page element to the front. (Right click on element, bring to front). Is this happening on all tool tips you have configured? And no, I have not seen this before
There is a similar (and known) problem with tooltips appearing behind the Windows task bar. The problem is sporadic and I have never seen a solution. If you're also seeing this behavior sporadically (and I suggest that you try this on different machines), then it may be related. Otherwise, if the problem is consistent across multiple machines, let's see your code, because you're probably doing something wrong.
I have a similar issue. I have a user control written as C++ WTL, being used in a C# .NET2 app. If the control is just on the form then the controls tooltips work fine, however if the user control is on a panel or in a group then the tooltip is behind. I've tried changing the WTL code to force the tip to the front, this works but causes issues with lost focus/selection in other controls.
This problem is almost always caused by the window being TopMost. Try using SetWindowPos to set your tooltip to HWND_TOPMOST. I haven't tried this though...
I've seen this issue happen in both Windows.Forms and Delphi (native windows) based applications, caused by the interaction of "stay on top" with the Windows API.
Essentially, marking a form as TopMost makes it stay on top of some windows, but not others - Window management has more than two distinct levels.
What I found is this: my applications would behave themselves when run normally, with tooltips showing on top. Problems would occur when switching to- and from- other applications - somehow the "TopMost" of the windoww would become "very-ultra-top-most" (non-technical term ;-) ) with the tooltips appearing behind the window.
Having described the problem, I'd like to offer you a solution - but I never did find a good one. Sigh.
Hope that the additional information will be enough for you to find the solution you need.
I have seen this happen on Windows XP, particularly on the taskbar.
Are you sure it's an issue with your application, rather than the OS?

Categories