Re: [Mono-winforms-list] Too slow performance on RichTextBox?
I'm actually surprised at that Windows performance. Typically Thread.Sleep
only has a 15ms resolution... try appending 15 times between each sleep.
On Mar 27, 2012 7:16 AM, "sharkal" wrote:
> Hi,
> at the meantime i wrote a small test programm where it does the following:
>
>while (indexCounter < maxIndexCount)
>{
>var timestamp = (String.Format("{0:yyMMdd
> HH:mm:ss:fff}", DateTime.Now));
>
>rtxtOutput.AppendText(indexCounter + " " + timestamp +
> " This is a output text
> to test the output time.\n");
>indexCounter++;
>Thread.Sleep(1);
>}
> So the while loop do nothing more, than writing the actual timestamp to
> the
> textbox, sleep 1ms and write the next text out.
> If i do this with mono, i have a time differents of ~ 15-20ms , in windows
> it is around 1-2ms.
>
> The Richtextbox is all with the default settings.
> Does anyone knows how to get a better performance here?
>
>
> --
> View this message in context:
> http://mono.1490590.n4.nabble.com/Too-slow-performance-on-RichTextBox-tp4485123p4508543.html
> Sent from the Mono - WinForms mailing list archive at Nabble.com.
> ___
> Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
>
___
Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Implementing a window manager in C#
We've ported Mono to a device that has a tiny GUI (no real concept of a "window", just some control-like widgets) and it's time to implement the XplatUIDriver. The device has no keyboard, clipboard, mouse cursor (it's touchscreen)... no system colors, no keyboard shortcuts, etc. I figure that more than half of the functions can be stubbed, behave statically or be otherwise brushed aside. Can someone describe what happens when, for example, the mouse is clicked over a button? An understanding of the execution path would greatly help us understand the 100+ functions in XplatUIDriver.cs as we sort through the code. I'm particularly interested in how an application drawing something on the screen gets it to the GUI. What major players are involved, and in what order? GDIPlus? Forms? Graphics object? Visual Theme? XplatUIDriver? A brief outline would be great. We also need to decide if it would be useful to leverage the existing system's image widgets. Blitting onto a widget and moving the widget around is accelerated, but it might be simpler if we just write a window-manager in C#. Except for menus and drop-downs, we intend on all windows being full-screen with no titlebar. Anyone have an opinion on this? Ideas for a high-level strategy? - Michael "Kipp" Mudge Welch Allyn, Inc. Skaneateles, NY Office: 315-554-4057 ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Porting Mono winforms to a new OS/Window Manager
We are working on getting Mono WinForms up and running on our device, and I'd like to make sure that we're on the right track and have a good understanding of what is ahead of us. Through the project, most of our issues have been unknown unknowns - so if you can anticipate any obstacles, it would be very helpful. We use a GUI manager called PegX - it is fairly primitive. As I understand it, there is some dependency between LibGDIPlus and the GUI, and XPlatUIDriver is also meant to map to the GUI. What is the description of these relationships? PegX does make use of some hardware acceleration, so we would like to leverage that as much as possible. Also, the current implementation of LibGDIPlus has dependencies on many things - FontConfig, FreeType, LibPNG, XLib, GLib, Cairo. We only have FreeType and Cairo completely ported. Are there parts of LibGDIPlus that we can cut out and replace with calls straight to PegX, and minimize all of the remaining dependencies? Is there someone who can help guide us? The system is touchscreen-only. How much do we need to be concerned with the UI message pump? The only touchscreen events are down, move and up. How might we detect that the cursor has clicked on a textbox so that we can pop up our onscreen keyboard? And most importantly, what questions have I failed to ask? Thanks, - Michael "Kipp" Mudge Welch Allyn ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
