Re: [Mono-winforms-list] ISO-8859-15 (Euro) with text
> I'm not sure if the problem is reading in the CSV file is defaulted to > UTF-8 or if it's a display problem. Is there a way to read a CSV file in > as ISO-8859-15 rather than UTF-8? > > Sorry if these seem like 2 questions, it's really 1. You can specify the encoding by creating your StreamReader with the proper encoding. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Native look theme for Windows
> Oh, I didn't know that. Does that mean that I better leave it alone? > I mean, I don't think I'm going to finish this all by my self, so I > don't want to stop someone who can actually write the whole thing. > Or should I send what I have done so far and keep working? > I'm not familiar with the SoC and how it works. In my opinion, it would be worth starting on this now, and then the folks of the Summer of Code (if we accept that proposal, based on how many slots we get) could complement the work, or work on the other native engines (Aqua, Gtk). Also, the summer of code effort would only have code available at the end of the summer and only if it is completed. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Remove horrible MONO_MWF_USE_CARBON_BACKEND env vars
> We could possible provide a env override to force back to X11 on the > mac, but since we dont work on 10.5 anyways (x11) I'm not sure how > much value there is in this. Supporting X might come in handy when we do designer integration into MD. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Regression in PDN3
Hey folks, Today I launched PDN3 and it no longer renders the toolbar, here is what shows up on the Console: X11 Error encountered: Error: BadMatch (invalid parameter attributes) Request: 12 (0) Resource ID: 0x42000FB Serial: 1557 Hwnd:Hwnd, Mapped:True ClientWindow:0x42000FC, WholeWindow:0x42000FB, Zombie=False, Parent:[Hwnd, Mapped:True ClientWindow:0x42000F2, WholeWindow:0x42000F1, Zombie=False, Parent:[Hwnd, Mapped:True ClientWindow:0x42000F6, WholeWindow:0x42000F5, Zombie=False, Parent:[]]] Control: System.Windows.Forms.ImplicitHScrollBar, Minimum: 0, Maximum: 983, Value: 0 at System.Environment.get_StackTrace() in /home/cvs/mcs/class/corlib/System/Environment.cs:line 203 at System.Windows.Forms.XplatUIX11.HandleError(IntPtr display, XErrorEvent ByRef error_event) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 1857 at System.Windows.Forms.XplatUIX11.HandleError(IntPtr , XErrorEvent ByRef ) at System.Windows.Forms.XplatUIX11.XGetWMNormalHints(IntPtr , IntPtr , XSizeHints ByRef , IntPtr ByRef ) at System.Windows.Forms.XplatUIX11.XGetWMNormalHints(IntPtr , IntPtr , XSizeHints ByRef , IntPtr ByRef ) at System.Windows.Forms.XplatUIX11.SetWindowMinMax(IntPtr handle, Rectangle maximized, Size min, Size max, System.Windows.Forms.CreateParams cp) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 5278 at System.Windows.Forms.XplatUIX11.SetWMStyles(System.Windows.Forms.Hwnd hwnd, System.Windows.Forms.CreateParams cp) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 1053 at System.Windows.Forms.XplatUIX11.CreateWindow(System.Windows.Forms.CreateParams cp) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUIX11.cs:line 2675 at System.Windows.Forms.XplatUI.CreateWindow(System.Windows.Forms.CreateParams cp) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/XplatUI.cs:line 450 at System.Windows.Forms.NativeWindow.CreateHandle(System.Windows.Forms.CreateParams create_params) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/NativeWindow.cs:line 112 at System.Windows.Forms.Control.CreateHandle() in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4221 at System.Windows.Forms.Control.CreateControl() in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3587 at System.Windows.Forms.Control.SetVisibleCore(Boolean value) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4769 at System.Windows.Forms.Control.set_Visible(Boolean value) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3259 at System.Windows.Forms.ScrollableControl.Recalculate(Boolean doLayout) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 931 at System.Windows.Forms.ScrollableControl.AdjustFormScrollbars(Boolean displayScrollbars) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 598 at System.Windows.Forms.ScrollableControl.OnLayout(System.Windows.Forms.LayoutEventArgs levent) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:line 611 at System.Windows.Forms.Control.PerformLayout(System.Windows.Forms.Control affectedControl, System.String affectedProperty) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3857 at System.Windows.Forms.Control.SetBounds(Int32 x, Int32 y, Int32 width, Int32 height, BoundsSpecified specified) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 4150 at System.Windows.Forms.Control.set_Size(Size value) in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:line 3105 at PaintDotNet.SurfaceBox.set_Surface(PaintDotNet.Surface value) in /cvs/pdn3/src/PdnLib/SurfaceBox.cs:line 68 at PaintDotNet.DocumentView.DocumentSetImpl(PaintDotNet.Document value) in /cvs/pdn3/src/Data/DocumentView.cs:line 815 at PaintDotNet.DocumentView.set_Document(PaintDotNet.Document value) in /cvs/pdn3/src/Data/DocumentView.cs:line 775 at PaintDotNet.AppWorkspace.CreateBlankDocumentInNewWorkspace(Size size, MeasurementUnit dpuUnit, Double dpu, Boolean isInitial) in /cvs/pdn3/src/AppWorkspace.cs:line 1916 at PaintDotNet.MainForm..ctor(System.String[] args) in /cvs/pdn3/src/MainForm.cs:line 300 at PaintDotNet.Startup.StartPart2() in /cvs/pdn3/src/Startup.cs:line 317 at PaintDotNet.Startup.Start() in /cvs/pdn3/src/Startup.cs:line 262 at PaintDotNet.Startup.Main(System.String[] args) in /cvs/pdn3/src/Startup.cs:line 373 ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] PDN3: Another regression.
The toolbox now only displays two items as well, instead of the whole palette. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [PATCH] Patch for System.Windows.Forms.Application to match MSDN specifications for Application Data
Hello, > These changes are documents in MSDN > (http://msdn2.microsoft.com/en-us/library/system.windows.forms.application.commonappdatapath(vs.80).aspx): > > "If a path does not exist, one is created in the following format: > Base Path\CompanyName\ProductName\ProductVersion" Ah, sorry, I did not understand correctly the thread. Thanks for the pointers! Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [PATCH] Patch for System.Windows.Forms.Application to match MSDN specifications for Application Data
Hello, > Let me ask, is there any documentation on writing tests, I'm a little > unclear on how/where to do this? But most importantly, this seems to change where things get loaded from, where is that documented at? It also seems like some changes to the registry were done, why were those done? > ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Nice test for Winforms and the browser
Hey folks, Check out this nice app that works out of the box on Mono with Winforms. There are still some issues with our LINQ implementation, but it makes use of the WebControl: http://www.albahari.com/linqpad.html Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] MWF Mac.
Hello Geoff, I like the prioritization; Do you think that the stuff in "HIGH" can be achieved by the 1.2.6 release? Hopefully if we get that out of the way, we can get some folks from the OSX community to help out with the MEDIUM/LOW tasks. Another thing that might be a useful contribution is to have someone develop an OSX "theme", something that tries to mimic some of the OSX UI. Am not sure how far this can go though. > Talking with Miguel on IRC today we decided it would be a good idea to update > everyone on the state of the MWF Mac driver in hopes to > prioritize a set of realistic goals for 1.2.6. As of yesterday I have > committed the bulk of my work to get the driver working again. The list > included in this email does not include bugs or performance issues but is a > rough map of the features that are currently > missing / not fully implemented in the driver. > > My first pass at the priority list is this: > > HIGH > 1. Keyboard Driver > 2. Clipping (I have about 80% coverage of the clipping cases; but there > are a lot of edge cases that cause controls to disappear) > 3. Async methods > > MEDIUM > 1. Clipboard > 2. DND > 3. ReversibleDrawing > > LOW > 1. Audio > 2. Systray > 3. Cursors > > I plan on focusing on the keyboard driver in the immediate future. If anyone > is curious as to what is involved you can look at the X11Keyboard.cs for a > sample implementation for X11. > > -geoff > > ___ > 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
Re: [Mono-winforms-list] Winforms WebBrowser control - call for apps
Hello, > I would like to test winforms .net applications that use the > WebBrowser control, and I need your feedback on what applications are > out there that use it. If you have one, or you know of one, please let > me know. Use the archives that I posted to the internal mailing list, they contain full data about who is using the WebControl, and some contain urls. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] XIM support
Hello John, > In the next 4 months, we’ll reach a point where our SWF/MWF app, which > runs on the OLPC, will have to be re-written in GTK or QT for lack of > custom-keyboard ability > ( https://bugzilla.novell.com/show_bug.cgi?id=320988 ). Being a > Windows shop, we don’t have the first clue how to go about adding this > ourselves. When is your hard deadline for this, and what kind of support are you looking for? The XIM as far as I know is used for entering international characters that might not be present on the keyboard (beyond the basic X setup). Do you need something beyond the base X setup? Could you describe what is the particular scenario, there might be a subset of the bug that can be implemented. Miguel > ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] WS_EX_TRANSPARENT implementation for the X11 backend
> The issue is that even with the RGBA colormap and > BackColor.Transparent set for the control it isn't transparent. I have > tried filling the client area in OnPaintBackground with > Brushes.Transparent but that also just results a black client > rectangle. Could it be that Color.Transparent doesn't match what is > expected by X? Are you using a compositing window manager? (Compiz?) ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] (Rich)TextBox: Maximum reasonable string length?
Hello, > yes, the TextBox in .NET is not so fast either, but I'm satisfied with the > performance .NET's RichTextBox. In Windows case, the control is most likely a native control that comes with a C# wrapper. > It's good that you prefer to make things work, although I'm pretty > happy with the latest mono version. All controls I use work really > good (except TreeView and RichTextBox). I think you're not far from > the point you should think about some cosmetic and performance issues > to increase the acceptance of mono. But that's my extern opinion. My > client is not very happy about that (Rich)TextBox issue, but that's > not high prio resp. not so important I think. As Rolf said, our goal right now is to be correct first, and since there are still various areas that need to be corrected we are not likely going to be able to spend much time on these cases in the immediate future. But the beauty of open source is that if this is important to your customer you can work with him to study the performance problem, find out the hot spots and if things go well, submit patches to improve the performance. This has been done repeatedly in Mono. > Mono's progress in the past year was amazing - today I think that it > was a good decision to choose it in early 2006. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [Patch] ToolboxItem - Minor fixes and 2.0 updates
Hey, > I don't have svn access unfortunatly, so if someone else commit, please. Ah, we should set you up: www.mono-project.com/SVN Has the instructions. > ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [Patch] ToolboxItem - Minor fixes and 2.0 updates
Hello, This looks fine Ivan, please commit. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Add missing Find Method to TreeNodeCollection.
Hello, > Here we go. I applied a few small changes and its on SVN. (using System.Generic... needed protection) Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Add missing Find Method to TreeNodeCollection.
Hello Neil,
Your patch was reformatted by your mail program, could you resend as
an attachment?
Miguel.
> Adding some of the missing methods our application relies on.
>
>
>
> Index:
> /home/neilcawse/mymono/mcs/class/Managed.Windows.Forms/System.Windows.Forms/TreeNodeCollection.cs
>
> ===
>
> ---
> /home/neilcawse/mymono/mcs/class/Managed.Windows.Forms/System.Windows.Forms/TreeNodeCollection.cs
>(revision 78512)
>
> +++
> /home/neilcawse/mymono/mcs/class/Managed.Windows.Forms/System.Windows.Forms/TreeNodeCollection.cs
>(working copy)
>
> @@ -25,6 +25,7 @@
>
>
>
> using System;
>
> using System.Collections;
>
> +using System.Collections.Generic;
>
> using System.ComponentModel;
>
> using System.Globalization;
>
>
>
> @@ -434,7 +435,33 @@
>
> nodes = nn;
>
>}
>
>
>
> +#if NET_2_0
>
> + public TreeNode[] Find (string key, bool
> searchAllChildren) {
>
> + List results = new List(0);
>
> + Find (key, searchAllChildren, this, results);
>
> + return results.ToArray();
>
> + }
>
>
>
> + private static void Find (string key, bool
> searchAllChildren, TreeNodeCollection nodes, List results) {
>
> + for (int i = 0; i < nodes.Count; i++) {
>
> +TreeNode thisNode = nodes[i];
>
> +if (string.Compare(thisNode.Name, key,
> true, CultureInfo.InvariantCulture) == 0) {
>
> + results.Add(thisNode);
>
> +}
>
> + }
>
> + // Need to match the Microsoft order.
>
> + if (searchAllChildren) {
>
> +for (int i = 0; i < nodes.Count; i++) {
>
> + TreeNodeCollection childNodes =
> nodes[i].Nodes;
>
> + if (childNodes.Count > 0) {
>
> + Find(key,
> searchAllChildren, childNodes, results);
>
> + }
>
> +}
>
> + }
>
> + }
>
> +#endif
>
> +
>
> +
>
>internal class TreeNodeEnumerator : IEnumerator {
>
>
>
> private TreeNodeCollection collection;
>
>
> ___
> 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
Re: [Mono-winforms-list] What is best to use to identify the mono runtime installation?
Hello, > mono build". On the mailing lists and such people often talk about > "r77343" which is the svn revision. Is that revision compiled into > the runtime in some way that can be extracted at run time > programatically? Is there something better? (Other ideas would > include perhaps taking the build date of one of the core mono dlls or > something). I do not believe that it is available through a call today, but it is available if you run: mono --version (starting with the upcoming Mono 1.2.4 though and recent svn releases). Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Disabling SMDiagnostics.dll on Windows
Hello, > Has anyone debugged olive under VS referencing Mono assemblies and > know how to disable this assembly from being loaded when using > System.ServiceModel.dll? I know that the Windows.Forms developers run into the same issue: they have assemblies that are versioned and signed with the same key as Microsoft. It might be worth finding out from the Windows.Forms team how this is done, and add this to our FAQs. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Paint.NET 3 port is now public.
Hello folks, Since so many people have emailed me to tell me that they want to help with the Paint.NET 3 port and the various controls that Jonathan Pobst has worked on are now functional, I have moved the Paint.NET 3 port from the internal SVN repository that we had at Ximian to Google Code hosting. If you want to help, email me, and I will add your name to the list of contributors. The project home page is: http://code.google.com/p/paint-mono/ The porting strategy is: http://code.google.com/p/paint-mono/wiki/PortingStrategy To get the source go here: http://code.google.com/p/paint-mono/source Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] ClipRectangles and Paint.NET
Hey Chris!
To optimize the rendering in Paint.NET, the application gets a list
of clipping rectangles.
I tried to use the get_ClipRectangles on the Hwnd class through
reflection and it works, but it returns some strange rectangles which
can make the application hang for 20-30 at a time.
I have added some instrumentation code to look at the rectangles
returned and they seem to be out of range, and this seems to hang the
application. Notice that the control's boundary is 212, 159:
Returning 3 rectangles for PaintDotNet.SurfaceBox that has 212,159
{X=-58655,Y=-58655,Width=59013,Height=58923}
{X=0,Y=0,Width=800,Height=600}
{X=0,Y=0,Width=212,Height=159}
Returning 2 rectangles for PaintDotNet.SurfaceBox that has 212,159
{X=-138,Y=-138,Width=267,Height=156}
{X=118,Y=7,Width=11,Height=21}
The hang goes away if I replace the code in SystemLayer/UI.cs with
code that just returns a rectangle that is 0, 0, control.Width,
control.Height, but this is not optimal.
I tried using "Rectangle.Intersect" with the control.Bounds, but it
got me too much of a clipped rectangle, so I suspect am getting
rectangles that have a different origin.
The entire code is in:
svn+ssh://[EMAIL PROTECTED]/extras/trunk/pdn3/trunk/src
Miguel.
___
Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Important regressions in Windows.Forms
--- Begin Message --- Hi, I know I should be posting this to winforms list, but it is rejecting my email... :-( I've just downloaded, compiled and tested latest from SVN. We had several problems, many of them regarding to the list view, which are now fixed. But the bad news is: the tree view is broken (it doesn't even show up), there are many problems on form resizing (our wizard was working correctly two weeks ago or so and now is totally broken). I could try to file all bugs, but it is maybe easier if somehow we can collaborate, maybe making some testing ourselves weekly, maybe giving you Plastic to test... I don't know. Maybe it will also help if somebody (I would do it myself) could check the fixes before they are integrated (branch per task would greatly help here... :-P ) Thanks pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list --- End Message --- ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] webcontrol (mozilla window in windows forms application)
Hello, > when will be webcontrol class implemented into Linux Mono? I know > there is a gecko sharp for Gtk but I have to use SendKeys.Send method > and it is working only in application that is based on Windows.Forms > GUI. We have not yet scheduled this for implementation, there is some early work from Zach but we do not know where that work stands right now. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Caret
Hello, What I would like to see is a separate assembly, say: Mono.Windows.Forms That would contain methods for portability like this. The entry points in this assembly would do something operating system specific. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] More Update on regressions.
Hey folks, Also, SVN fails to startup the new pdn port (pdn272), no window ever shows up, with the following error: X11 Error encountered: Error: BadMatch (invalid parameter attributes) Request: 12 (X_ConfigureWindow) Resource ID: 0x3A000D4 Serial: 29506 Hwnd:Hwnd, Mapped:True ClientWindow:0x3A000D5, WholeWindow:0x3A000D4, Parent:[Hwnd, Mapped:True ClientWindow:0x3A017C8, WholeWindow:0x3A017C7, Parent:[Hwnd, Mapped:True ClientWindow:0x3A017A7, WholeWindow:0x3A017A6, Parent:[Hwnd, Mapped:True ClientWindow:0x3A0179C, WholeWindow:0x3A0179B, Parent:[Hwnd, Mapped:True ClientWindow:0x3A00C3A, WholeWindow:0x3A00C39, Parent:[Hwnd, Mapped:True ClientWindow:0x3A3, WholeWindow:0x3A2, Parent:[]] Control: System.Windows.Forms.ToolStripComboBox+ToolStripComboBoxControl, Items.Count:57 at System.Windows.Forms.XplatUIX11.HandleError () at System.Windows.Forms.XplatUIX11.HandleError () at System.Windows.Forms.XplatUIX11.XGetWindowProperty () at System.Windows.Forms.XplatUIX11.XGetWindowProperty () at System.Windows.Forms.XplatUIX11.GetWindowState () at System.Windows.Forms.XplatUI.GetWindowState () at System.Windows.Forms.Form.get_WindowState () at PaintDotNet.DocumentWorkspace.toolPulseTimer_Tick () at System.MulticastDelegate.invoke_void_object_EventArgs () at System.Windows.Forms.Timer.OnTick () at System.Windows.Forms.Timer.FireTick () at System.Windows.Forms.XplatUIX11.CheckTimers () at System.Windows.Forms.XplatUIX11.PeekMessage () at System.Windows.Forms.XplatUIX11.WaitForHwndMessage () at System.Windows.Forms.XplatUIX11.MapWindow () at System.Windows.Forms.XplatUIX11.CreateWindow () at System.Windows.Forms.XplatUI.CreateWindow () at System.Windows.Forms.NativeWindow.CreateHandle () at System.Windows.Forms.Control.CreateHandle () at System.Windows.Forms.Control.CreateControl () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.ToolStrip.OnVisibleChanged () at System.Windows.Forms.Control.OnParentVisibleChanged () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.Control.WndProc () at System.Windows.Forms.ScrollableControl.WndProc () at System.Windows.Forms.ContainerControl.WndProc () at System.Windows.Forms.Control+ControlNativeWindow.WndProc () at System.Windows.Forms.NativeWindow.WndProc () at System.Windows.Forms.XplatUIX11.DispatchMessage () at System.Windows.Forms.XplatUIX11.WaitForHwndMessage () at System.Windows.Forms.XplatUIX11.MapWindow () at System.Windows.Forms.XplatUIX11.CreateWindow () at System.Windows.Forms.XplatUI.CreateWindow () at System.Windows.Forms.NativeWindow.CreateHandle () at System.Windows.Forms.Control.CreateHandle () at System.Windows.Forms.Control.CreateControl () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.ToolStrip.OnVisibleChanged () at System.Windows.Forms.Control.OnParentVisibleChanged () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.Control.WndProc () at System.Windows.Forms.ScrollableControl.WndProc () at System.Windows.Forms.ContainerControl.WndProc () at System.Windows.Forms.Control+ControlNativeWindow.WndProc () at System.Windows.Forms.NativeWindow.WndProc () at System.Windows.Forms.XplatUIX11.DispatchMessage () at System.Windows.Forms.XplatUIX11.WaitForHwndMessage () at System.Windows.Forms.XplatUIX11.MapWindow () at System.Windows.Forms.XplatUIX11.CreateWindow () at System.Windows.Forms.XplatUI.CreateWindow () at System.Windows.Forms.NativeWindow.CreateHandle () at System.Windows.Forms.Control.CreateHandle () at System.Windows.Forms.Control.CreateControl () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.ToolStrip.OnVisibleChanged () at System.Windows.Forms.Control.OnParentVisibleChanged () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.Control.OnParentVisibleChanged () at System.Windows.Forms.Control.OnVisibleChanged () at System.Windows.Forms.ScrollableControl.OnVisibleChanged () at System.Windows.Forms.Control.WndProc () at System.Windows.Forms.ScrollableControl.WndProc () at System.Windows.Forms.ContainerControl.WndProc () at System.Windows.Forms.Control+ControlNativeWindow.WndProc () at System.Windows.Forms.NativeWindow.WndProc () at System.Windows.Forms.XplatUIX11.DispatchMessage () at System.Windows.Forms.XplatUIX11.WaitForHwndMessage () at System.Windows.F
[Mono-winforms-list] SVN: Recent Winforms regressions.
Hey folks, PDN (the old one) fails to load 3 out of the 4 dialog boxes it used to render, and produces this error message on the console: System.NullReferenceException: Object reference not set to an instance of an object at PaintDotNet.MainToolBar.OnLoad (System.EventArgs e) [0x7] in /home/cvs/pdn/src/MainToolBar.cs:161 at System.Windows.Forms.UserControl.OnCreateControl () [0x6] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/UserControl.cs:80 at System.Windows.Forms.Control.CreateControl () [0x00067] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:3264 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:CreateControl () at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x0029d] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:4476 at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message& m) [0x0] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ScrollableControl.cs:648 at System.Windows.Forms.ContainerControl.WndProc (System.Windows.Forms.Message& m) [0x0003e] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/ContainerControl.cs:517 at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message& m) [0x00a53] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Form.cs:2317 at PaintDotNet.PdnBaseForm.WndProc (System.Windows.Forms.Message& m) [0x000f8] in /home/cvs/pdn/src/PdnLib/PdnBaseForm.cs:297 at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/Control.cs:196 at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x0006b] in /home/cvs/mcs/class/Managed.Windows.Forms/System.Windows.Forms/NativeWindow.cs:179 In addition, it feels like a few of the widgets on the screen do not work properly, or have regressed in the last week or so. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Paint.NET, without the attachment.
Hello,m > Those with access to SVN can pull out their own copy from here: Sebastien has pointed out my mistake, the correct way of pulling it out is by using: svn co svn+ssh://[EMAIL PROTECTED]/extras/trunk/pdn272/trunk pdn272 Once you get it, you must load the pdn272/src/paintdotnet.sln file with MonoDevelop (SVN is required right now) and click "Run". Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Paint.NET, without the attachment.
Hey, Hello folks, The following patch gets Paint.NET 2.72 to start up, the porting effort has taken less time than the time it took to port Paint.NET 1, mostly because I could cut and paste a handful of routines, I did not repeat the same mistakes and because it uses 2.0 APIs. In some cases I had to implement some missing stuff (SafeHandles were the most elaborate, a handful of events and some stubs). The port is by no means complete, tomorrow I have to look at the DrawBitmap which changed a lot since 1.0 and currently does not paint anything. Attached is a patch to get a pristine 2.72 Paint.NET to build with MonoDevelop (Am using SVN as it has some decent Visual Studio 2005 solution importing support). I would love to have a complete Makefile setup at some point, because MonoDevelop still has some odd rules that I can not quite grasp while rebuilding code. Also a screenshot is included which shows a lot of areas that will need some work. Those with access to SVN can pull out their own copy from here: svn co svn+ssh://[EMAIL PROTECTED]/extras/trunk/pdn272/trunk/pdn272 Notice that this tree is not available on AnonSVN. Screenshot: http://primates.ximian.com/~miguel/ScreenshotPDN.png Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Winforms on Solaris
Hello, > Anybody is running winforms on Solaris or Nexenta? If so, could you please > tell how to set it up? You need the standard tools required to build Mono: glib-2.x bison (for the grammar parser) libgdiplus and its dependencies: libjpeg libgif libpng libtiff libexif mono You can get the list yourself by running ./configure for mono and libgdisplus. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] AutoComplete properties patch for Text- and Combobox
ello, > Any suggestions? Instead of using String.Format for the calls that will throw a user-visible error, use Locale.GetText (it takes the same arguments). When we do localization, this will reduce the work we do at that time. In general, I do not like Enum.IsDefined because it boxes the value on every call. I would rather compare to upper/lower ranges which is faster (and besides, in Mono, we are guilty of not really doing Enum parameter checks in a number of places, which one day we might want to do). If this was a common pattern, I wonder if it would be worth having the compiler inline Enum.IsDefined to avoid the boxing? Worth considering. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] ButtonBase.AutoSize Implementation
Hello, > thanks for the hint I've corrected the patch. It resizes now if the image, > font or text has been changed. This should cover all cases, or am I missing > something? My code review comments: Only a few comments, you code should follow the Mono naming conventions for fields, so the field 'autoSize' should become "auto_size". You do not need to use "this.Autosize" or "this.AutoCalculateNewSize", you can remove the "this" from that bit (it happens in a bunch of other places as well). There are two magic constants in there, that am confused about: 35 and 15. What are those for, and why are they needed? Shouldnt those be computed based on some font metric? Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] ButtonBase.AutoSize Implementation
Hello, > the first implementation of Button.AutoSize did not resize in cases where the > Font has been changed. I've corrected it but forgot to send the new Version > to the list. > > Therefore please review this patch instead of the initial one. A few days ago, someone on irc (perhaps jpobst?) mentioned that the problem with the code is that it did not take into account embedded images or other elements that might be added to it. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] OS X Support?
hello, > So far I've been unable to get Mono 1.2 + MWF to work without X11 > running. To test I've been using the following code: Winforms on OSX is only supported with X11 at this point. The native driver is currently not being developed. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Contributing to Winforms
Hey, > so svn and the whole community project thing are new to me.. any > tips/guidance will be greatly apreciated If you feel comfortable with irc, we can answer your questions, come to #mono-winforms or #mono channels on irc.gnome.org Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Dock Panels?
Hello,
> anyone already checked if its possible to use or adept Weifen Luo's DockPanel
> Suite
> with mono winforms? would be great if this could be possibe. :)
>
> here's a link to the suite:
> http://sourceforge.net/projects/dockpanelsuite
Chris is correct, the code does a fair amount of P/Invoke into User32.
Luckly there are only 32 places where this happens, I went ahead and
ifdefed out all the pieces, and added warning messages for all the
missing routines, and packaged it as a tarball.
It does not currently work, the tarball am posting starts up, does not
paint what I believe is the area where the dock is, and I believe the
Makefile generated is incorrect as it is unable to find the string
resources (the names on the resources is wrong).
All my changes are attached as a patch, or available in a ready-to-use
tarball here:
http://tirania.org/dockpanel-port.tar.gz
This could be used as a starting point; Maybe we could provide a
Managed.Helper.Winforms.dll that would provide similar functionality to
the one this library depends on, and eventually we could have a
"Guidelines to port you winforms app with lots of pinvokes".
Miguel.
diff -ruN --exclude='*~' dockpanel.orig/DockSample/Makefile dockpanel/DockSample/Makefile
--- dockpanel.orig/DockSample/Makefile 1969-12-31 19:00:00.0 -0500
+++ dockpanel/DockSample/Makefile 2006-11-12 07:55:23.0 -0500
@@ -0,0 +1,71 @@
+ifndef TARGET
+ TARGET=./bin/Debug
+else
+ TARGET=./bin/$(TARGET)
+endif
+
+MCS=mcs
+RESGEN=resgen
+ifndef (RELEASE)
+ MCSFLAGS=-debug
+endif
+LIBS=-lib:/mono/lib/pkgconfig/../../lib/mono/1.0 -lib:/mono/lib/pkgconfig/../../lib/mono/gtk-sharp
+
+
+DOCKSAMPLE_EXE=$(TARGET)/DockSample.exe
+DOCKSAMPLE_PDB=$(TARGET)/DockSample.exe
+DOCKSAMPLE_SRC=AboutDialog.cs \
+ AssemblyInfo.cs \
+ DummyDoc.cs \
+ DummyOutputWindow.cs \
+ DummyPropertyWindow.cs \
+ DummySolutionExplorer.cs \
+ DummyTaskList.cs \
+ DummyToolbox.cs \
+ MainForm.cs \
+ Extender/Extender.cs \
+ Extender/FromBase/AutoHideStripFromBase.cs \
+ Extender/FromBase/AutoHideTabFromBase.cs \
+ Extender/FromBase/DockPaneCaptionFromBase.cs \
+ Extender/FromBase/DockPaneStripFromBase.cs \
+ Extender/FromBase/DockPaneTabFromBase.cs \
+ Extender/FromBase/Helpers/DockHelper.cs \
+ Extender/FromBase/Helpers/ResourceHelper.cs \
+ Extender/FromBase/Win32/Enums.cs \
+ Extender/FromBase/Win32/Gdi32.cs \
+ Extender/FromBase/Win32/Structs.cs \
+ Extender/FromBase/Win32/User32.cs \
+ Extender/Override/AutoHideStripOverride.cs \
+ Extender/Override/DockPaneStripOverride.cs
+DOCKSAMPLE_RESX=AboutDialog.resx DummyDoc.resx DummyOutputWindow.resx DummyPropertyWindow.resx DummySolutionExplorer.resx DummyTaskList.resx DummyToolbox.resx MainForm.resx
+DOCKSAMPLE_RES=-resource:AboutDialog.resources,DockSample.AboutDialog.resources \
+ -resource:DummyDoc.resources,DockSample.DummyDoc.resources \
+ -resource:DummyOutputWindow.resources,DockSample.DummyOutputWindow.resources \
+ -resource:DummyPropertyWindow.resources,DockSample.DummyPropertyWindow.resources \
+ -resource:DummySolutionExplorer.resources,DockSample.DummySolutionExplorer.resources \
+ -resource:DummyTaskList.resources,DockSample.DummyTaskList.resources \
+ -resource:DummyToolbox.resources,DockSample.DummyToolbox.resources \
+ -resource:MainForm.resources,DockSample.MainForm.resources \
+ -resource:Resources/DockPanel.xml,DockSample.Resources.DockPanel.xml
+
+all: \
+$(DOCKSAMPLE_EXE)
+$(DOCKSAMPLE_EXE): $(DOCKSAMPLE_SRC) # Missing dependency project WinFormsUI ID:{D3C782BA-178E-4235-A3BA-8C11DEBB6BEE}?
+ -mkdir -p $(TARGET)
+ $(RESGEN) /compile AboutDialog.resx DummyDoc.resx DummyOutputWindow.resx DummyPropertyWindow.resx DummySolutionExplorer.resx DummyTaskList.resx DummyToolbox.resx MainForm.resx
+ $(MCS) $(MCSFLAGS) $(LIBS) -r:System.dll -r:System.Data.dll -r:System.Drawing.dll -r:System.Windows.Forms.dll -r:System.Xml.dll -r:WinFormsUI.dll -r:System.Web.Services.dll -target:winexe -out:$(DOCKSAMPLE_EXE) $(DOCKSAMPLE_RES) $(DOCKSAMPLE_SRC)
+
+
+# common targets
+
+all: $(DOCKSAMPLE_EXE)
+
+clean:
+ -rm -f "$(DOCKSAMPLE_EXE)" 2> /dev/null
+ -rm -f "$(DOCKSAMPLE_PDB)" 2> /dev/null
+
+
+# project names as targets
+
+DockSample: $(DOCKSAMPLE_EXE)
+
diff -ruN --exclude='*~' dockpanel.orig/Makefile dockpanel/Makefile
--- dockpanel.orig/Makefile 1969-12-31 19:00:00.0 -0500
+++ dockpanel/Makefile 2006-11-12 08:02:39.0 -0500
@@ -0,0 +1,4 @@
+all:
+ (cd WinFormsUI/; make && gacutil -i bin/Debug/WeifenLuo.WinFormsUI.Docking.dll)
+ (cd DockSample; make && mono bin/Debug/DockSample.exe)
+
diff -ruN --exclude='*~' dockpanel.orig/WinFormsUI/AssemblyInfo.cs dockpanel/WinFormsUI/AssemblyInfo.cs
--- dockpanel.orig/WinFormsUI/AssemblyInfo.cs 2006-02-11 14:31:46.0 -0500
+++ dockpanel/WinFormsUI/AssemblyInfo.cs 2006-11-12 07:58:55.0 -0500
@@ -53,5 +53,5 @@
// documentation for more information on this.
//
[assembly: AssemblyDelaySign(false)]
-[assembly: AssemblyKeyFile("")]
+[assembly: Assembl
Re: [Mono-winforms-list] Mono hosting on firefox [Winforms embedding]
Hello, Am CCing the Mono Winforms List, as I do not know the answer to this, but someone there might have a suggestion. > I want to host the mono runtime in a firefox plugin, to allow somewhat like > an applet (an .net assembly) to run into a browser window. The basic idea is > to load and run via a platform dependand plugin a .NET assembly. While there > are not so many difficulties in loading the mono run-time and calling a > bootstrapper method from the firefox plugin, problems arise when i try to > make something of "visual". > > To be more specific... Under windows, the FireFox insfrastructure makes > available to me a native window handle that is the hosting firefox window. > Under linux i have instead a Window* (X). > > Now, for my purposes i need to use the Mono System.Windows.Forms library, so > the question is: Under linux, how can i embed (->make parent) a UserControl > to a X Window using the supplied (X) Window*. I think the XPlatUIX11 used in > mono windows forms implementation uses X behind the scenes, so the thing > should be possible... Any ideas? > > thx. > > Best Regards, > Giavotto Bruno > [EMAIL PROTECTED] > -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [PATCH] Re: Possible bug with ResxResourceReader class
Hey! > The attached patches fix this problem together with some other > issues I found while testing (see changelogs). > > The test cases pass on MS.NET as well. This is great work! Please commit :-) ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
> I checked the bug database, and the defects I have seen appear to > have already been reported, so I did not report them a second time. > Now I am waiting for the 1.1.18 release before I do anything more, to > see how many issues have been resolved. If you want to help, you could get Mono buliding from SVN and report whether the fixes are working or not. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
Hello, > Ah, but the real question is when we shall see a proper Mac OS X > installer for MonoDevelop, even in its current state. I have looked at > some of the material, but the list of dependencies is incredibly > complex and ever-changing, and I am not even certain if all of the > information is even up to date. MonoDevelop on OS X will happen when Gtk/OSX is ready, before that, it is unlikely that we will package all of Gtk# and its dependencies to run on top of X11. You are free to use third party packages for that, but we do not have the time or resources to change directions until then. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
Hello, > This, along with the inability to use WinForms on Mac OS X, is a major > hindrance to the adoption of Mono by Mac developers, at least in my > opinion. It is not likely that we (Novell) will dedicate many resources to supporting Windows.Forms on MacOS X in the short term. This is one of those instances where someone in the OSX world that cares enough about it would have to step in and contribute the code. Either that, or wait for us to get around to it, but I do not have any dates on when we would do that. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
Hello, > So once that final bug is resolved and there is a consensus that WinForms > works as designed, what are the plans, if any, to simplify the packaging and > deployment processes. Well, that is a completely separate issue, independent of Windows.Forms. > It's been awhile since I've tried to run Mono on Linux and I don't think > I've ever seen MonoDevelop functioning properly. I don't think I've ever > been able to cleanly install Mono in a Linux environment without needing to > know how to resolve dependencies (which can spiral out of control quickly). You should use a mainstream distribution that includes Mono and ensures a seamless integration experience. > I think the question I'm asking is this. Will Mono ever be packaged so that > a non-Linux developer, say a VB 6 developer or less-experienced C# > developer, might be able to throw RedHat, Fedora, Suse, or Debian up on a > computer and quickly start creating usable and cross-platform programs that > can be easily deployed? You can already do that with Fedora, SUSE, Ubuntu and Debian. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
Hello, > Does this mean that a 1.1.18 release should be imminent? My desire/ > need for Mono is to be able to develop relatively simple GUI based > applications that can be compiled and executed on either Windows > (.Net) or Mac OS X (Mono), and the alternatives to WinForms are > simply more work than they are worth of these hobby programs (being > developed for volunteer organizations). Well, Mono 1.1.next is always imminent. What we do need though, is good testing of Windows.Forms to make sure that no major bugs slip through. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] bug counts
Hey, > Sept 8: > 6 Critical > 3 Blocker > 10 Major > Sept 10: > 3 Critical > 2 Blocker > 4 Major > Sept 27: > 0 Critical > 0 Blocker > 1 Major > very, very cool. 1 bug left in the top three. This is great news Chris! ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Text Layout Summit
Hello, > http://live.gnome.org/Boston2006/TextLayout > > We are going to discuss things related to text layout. Hopefully we will > discuss a uniscribe compatible API that could be used by wine and mono > SWF since afaik neither has uniscribe support. This sounds interesting, but is there a reason why Mono should use a Uniscribe implementation instead of Pango? > It would be great if someone from wine and mono could be there. If that > wouldn't be possible we would appreciate your input on what you would need. > > Regards, > Daniel > > P.S. OK to CC me on replies as I'm not subscribed to either list. > > ___ > Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-winforms-list > -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] [Mono-dev] Mono Winforms Team: we are hiring.
Hello, I forgot to say: email your resumes to [EMAIL PROTECTED] > Hello, > > We are looking for some strong developers interested in joining the > Mono Windows Forms team at Novell. > > What we are looking for: > > * Win32 and/or X11 experience; > > * GUI programming experience. > > * Desire to implement lots of new widgets. > > * Boston-based would be best, but we do not mind remote > hiring, provided you are a good communicator on email, > and can use irc to discuss and are in close contact > with your manager. > > * You must be able to show that you can write code, so if you > can show us code you have written before, or point us to > projects you have worked on, or have good references about > your coding abilities, all the better. > > * C# and C knowledge are a must. > > * If you have ever used a decompiler to look at Microsoft.NET > code you can not apply. > > Miguel. > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Porting job
Hello, > BTW, I've been toying with the idea of using Endogine and OpenBlackBox > (via AGG, OpenGL, and possible MyXAML) to write a XAML rendering > subsystem. It's a huge task, I know, but I feel it will become important > to have a non-MS alternative to WPF. Has there been any work done in the > OSS WPF area yet? Some pieces are in place, last year through the Google Summer of Code, Iain McCoy implemented a XAML compiler, and the necessary infrastructure for that. It is all GUI-less. The next stage is to create the GUI components; We have not attempted to look at it so far for a number of reasons: * The API is still very much changing, and tracking a changing API many times results in wasted effort. * At least those of us at Novell want to first ship Windows. Forms and not be distracted by the new shinny object. In the long term, a WPF implementation will likely happen in the open source world (either by us, or other teams) but it feels more bloated than it should. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] MDI bugs
Hello, > There are a few bugs in MDI on mono 1.1.16 for Windows: Do you have a sample test case that we can use to reproduce this? > 1) I can't drag MDI-child using mouse. Mouse resizes window vertically > instead of moving it. > > 2) Redrawing works awfully (see attached files) > > 3) MDI-child's menu not always draw. > > http://www.nabble.com/user-images/3175.png > http://www.nabble.com/user-images/3176.png > http://www.nabble.com/user-images/3177.png > http://www.nabble.com/user-images/3178.png -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] RichTextBox problem in Mono 1.1.16
Hello, > In the newest version of Mono 1.1.16 it doesn't work properly, > especially function LoadFile. In mono version 1.1.13.8 it works > correctly (i'm testing using vmware and ubuntu 5.10, so always the > same, clean environment). In newest version it throws exception when > trying load simple RTF file (with Arial font): Do you have a sample test case that we could debug against? Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Contributing
Hello, > Thanks for your reply. I have simply been using the Object Browser > built into VS 2005 and typing in the enum constants that it lists. I > know that's not a decompiler or ildasm. Not entirely sure exactly > what's a reflector, so I'll ask to be sure. Is Object Browser ok? I > could only find one mention of it in the Mono mailing archive, and it > sounded ok from there. Object Browser is not ok. Please write simple programs to dump the constants, and enter the source code from the documentation. This is the right process as documented on the web site. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Contributing
Hello, > Thanks for your reply. I have simply been using the Object Browser > built into VS 2005 and typing in the enum constants that it lists. I > know that's not a decompiler or ildasm. Not entirely sure exactly > what's a reflector, so I'll ask to be sure. Is Object Browser ok? I > could only find one mention of it in the Mono mailing archive, and it > sounded ok from there. This is best produced as you read the documentation. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Contributing
Hello, > My questions are: > - Is this helpful? (Or will this just get in the way of the MWF 1.1 > effort?) This is helpful. > - What would be the preferred method to submit? This list, bugzilla, or > get SVN access? The mailing list initially is the best thing. > - Anything else I should be aware of? read the www.mono-project.com/SVN to get yourself acquainted with the rules of developing in Mono. In particular it is extremely important that you do not ever use a decompiler, reflector or ildasm on any Microsoft code you are implementing. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] invalidate
Hello,
> The following code draws a line with Mono on Windows but doesn't do
> anything on Linux. I'm using Monoppix with Mono 1.1.8. Can anyone tell
> me if this issue is solved with recent releases?
You are using a Mono which is way too old.
The first Mono to come with a beta of Windows.Forms was 1.1.13, so its
about one year old. The current version is Mono 1.1.15.
> Thank you.
>
> --
> using System;
> using System.Drawing;
> using System.Windows.Forms;
> using System.Threading;
>
> namespace WindowsApplication1
> {
> public class Form1 : System.Windows.Forms.Form
> {
> private int i;
>
> [STAThread]
> static void Main()
> {
> Application.Run(new Form1());
> }
>
> protected override void OnPaint(PaintEventArgs pea)
> {
> pea.Graphics.DrawLine(new
> System.Drawing.Pen(Color.Blue), 1, 1, i, i);
> Thread.Sleep(200);
> i++;
> Invalidate();
> }
> }
> }
> --
> ___
> Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
>
--
Miguel de Icaza <[EMAIL PROTECTED]>
___
Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] some fixes for tests
Hello, > I tried make run-test-ondotnet and got some failures. I believe > that some are due to environment-dependency (like, some tests > result different depending on desktop themes). On some languages > those tests would work, but they don't on this Japanese box. > > It still fails at: I would love to get these changes into the tree, so we can use this as a baseline of what needs to be fixed on Linux. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] ImageList in Mono 1.1.15
Hello, > I've found issue in Mono 1.1.15 on Windows - when I compile simple > application containing only form and ImageList filled with bitmaps - > than mono returns following lines. Should I report it in bugzilla? Yes, please file a bug report, and if you can, please attach the source code that illustrates the problem. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] LD_LIBRARY_PATH
Hello, > "Gtk not found (missing LD_LIBRARY_PATH to libgtk-xll-2.0.so?), using > built-in colorscheme." The program then starts up as it should but > naturally the colors aren't quite right. > > An slocate for libgtk-xll-2.0.so produces: > > /usr/lib/libgtk-xll-2.0.so.0 > /usr/lib/libgtk-xll-2.0.so.0.800.15 > > The first is a symlink to the second...So can anyone here point me in a > direction to getting the color scheme right? Thanks for your time. A quick fix would be to install the -devel packages for Gtk. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Error starting an Application
Hey, > To build the whole thing you need to download both mono and mcs and fully go > through mono/autogen.sh once. After that, you can just update > mcs/class/Managed.Windows.Forms and say 'make && make install' in there. > > Here's the link for docs on how to build mono from source: > http://www.mono-project.com/Compiling_Mono (be sure to use the > mono.myrealbox.com anonymous repository) > > If that's too big a deal (which I could understand), I can upload a new > pre-compiled dll later tonight or tomorrow and you can just 'gacutil -i' > that. > Right now i've got so much debug in the code, you wouldn't want to run that > :-) If we can get a binary of XJS, it might be a good thing to add to our tests as well. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Getting Mono + WinForms to Compile
Hello, > I've been trying without much success to get Mono + SWF to compile on > my OSX machine... You need to provide more details. > Is there anyone who has managed to do this who could possibly provide > some type of step to step, or even assist me in troubleshooting??? > > Thanks, > > -- > Shmarya > --- > [EMAIL PROTECTED] - http://idp.satr-it.com > ___ > Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-winforms-list -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] TextBox error
Hello, > > __ > Sent from the Mono - WinForms forum at Nabble.com: > Re: TextBox error What version is your windows.forms? Remember that Windows.Forms is under heavy development. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] fully portable IDE with GTK
Hello, > Thanks, Miguel. I'll try X-develop, although my long term goal is to > see mono (and monodevelop, by extension) be completely independent of > X. My rationale is that mono will be much more easily accepted in the > traditional IT community if it does not have significant external > dependencies. The native Quartz port of Gtk 2.10 sounds really good. Mono != MonoDevelop, you should stop confusing those. There are *many* Gnome specific applications for Linux built with Mono, and that has *nothing* to do with Mono's own portability. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] fully portable IDE with GTK
Hello, > I'm using Mac OS X and I would love to be able to use monodevelop. MonoDevelop works on MacOS X, you need to use X, as MonoDevelop uses Gtk# which today requires X. Gtk 2.10 will include a native Quartz port. Or alternatively, you can use X-develop which is cross platform and works on OSX and is available today. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] desirable feature for MWF.ListView
Hello, > I can try to put together a patch for the existing ListBox if anyone is > interested. A patch with a test program would be great I think. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] What ImageList bugs do we need?
Hello, > I belive that there are bugs and limitations that should not be copied. For > example Mono runtime accepts 2.0 IL code in 1.x assemblies that is > definitely incompatible with MS.NET. This is probably a bug on the runtime as well. But it could also be said that we are lax in accepting a corner case (that is highly unlikely to happen in the wild), while bug compatibility on Windows.Forms is *very likely* to happen in the wild. For your runtime example: only a hand-constructed IL file would possible run into this "feature" and it would have to be something done on *Mono* and later attempted to be ported to Windows, which market-wise speaking is very small. While the expected behavior of Windows.Forms is something that a vast majority of .NET developers do use and tend to rely on. These people used the API in some form or another and worked around those limitations in one way or another. We want to keep the list of differences to a minimum between .NET and Mono for the .NET APIs, I do not want to come up with a large volume of "Things to look for when porting between platforms". ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] What ImageList bugs do we need?
Hello, > The fact that MS fixed something for 2.0 (which shows they are aware of the > bug), but not in a service pack for 1.1 I think is indicator that MS has the > same thinking, they don't want to break existing apps relying on their buggy > behaviour. I would like to add one thing: Since our implementation uses a single code base for both 1.1 and 2.0 profiles, we should support both behaviors from a single code base. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Window Capture
Hello,
> I've recently found a way to get a window capture with C# on the .NET
> 1.1 Framework using Message class and WndProc method. While on Windows
> it returns me the bitmap of the window, with Mono on Linux, I'm just
> getting an empty bitmap (black bitmap, no window drawing). Is it the
> normal behavior ?
As I explained to you before, Managed.Windows.Forms only implements the
necessary messages required to support its own widgets and not every
possible windows message.
This message is not necessary for Windows.Forms to work, so it has not
been implemented.
Although this could be implemented, it is not really a priority for us.
This is one of those situations where someone who has enough interest
will have to provide a patch if they want to get the functionality.
Miguel.
> the following source code is a click on a button on a form.
>
> ## CODE ##
>
> Bitmap inter = new Bitmap(this.Width, this.Height);
> Graphics gfxInter = Graphics.FromImage(inter);
> IntPtr hInter = gfxInter.GetHdc();
>
> // Complete Window Capture
> Message msg = new Message();
> msg.Msg = WM_PRINT;
> msg.HWnd = this.Handle;
> msg.WParam = hInter;
> msg.LParam = new IntPtr(PRF_CLIENT | PRF_CHILDREN |
> PRF_NONCLIENT | PRF_ERASEBKGND);
> this.WndProc(ref msg);
>
> gfxInter.ReleaseHdc(hInter);
> gfxInter.Dispose();
>
> inter.Save("test.jpg", ImageFormat.Jpeg);
>
> ## CODE ##
> ___
> Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
--
Miguel de Icaza <[EMAIL PROTECTED]>
___
Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Resizing of forms.
Hello, > Today I spent some time figuring out the pieces on how form resizing > works, and I found a pretty good article that describes how form > resizing works and some of their internal methods: > > http://msdn2.microsoft.com/en-us/library/ms135650 Oops, I posted the wrong url, this is the correct url: http://blogs.msdn.com/mharsh/archive/2004/01/25/62621.aspx > > There is one mistake in that article though; It states that the 1.x > mechanism works on 2.x which made me waste a few hours this afternoon > figuring it out. It turns out that the 1.x mechanism no longer works on > 2.x, it has been replaced by a different system. It took me a while to > realize that. > > In the end, I switched from VS 2005 to VS 2003 and all of my tests > started working. > > Am going to try to implement this functionality in my copious spare > time. > > Miguel. > ___ > Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-winforms-list > -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Resizing of forms.
Hello, Today I spent some time figuring out the pieces on how form resizing works, and I found a pretty good article that describes how form resizing works and some of their internal methods: http://msdn2.microsoft.com/en-us/library/ms135650 There is one mistake in that article though; It states that the 1.x mechanism works on 2.x which made me waste a few hours this afternoon figuring it out. It turns out that the 1.x mechanism no longer works on 2.x, it has been replaced by a different system. It took me a while to realize that. In the end, I switched from VS 2005 to VS 2003 and all of my tests started working. Am going to try to implement this functionality in my copious spare time. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Programs compiled on Delphi 2005 using MWF hang on exit
Hello, > Mono is amazing and I'am upgrading with every new release in Debian > Testing repository - currently 1.1.9.1-3. I throw away the Delphi2005 > and using C# and have no problems. > > Anyway, the report I take when executing my old D2005 app in Linux is > pasted at the end of the message. Ah, this is just a piece of code in the KDE handler that does not cope with files that are read protected, in your case: /usr/share/mimelnk/audio/x-ms-wax.desktop I have commited a fix. This had nothing to do with Delphi. Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Re: Magic Library PInvokes
Hello, > Magic Library is a managed window manager. It uses some MS specific > PInvokes. I've attached those files (I left off the enums and structs > files). If you want all the source, go here: Providing emulation for those calls should not be hard, so the library eventually should run. The issue is that the "Magic Window Manager" (am not sure what that is) might not be portable, doing the equivalent on X might require special code paths. It might probably be best if we could get the source code to their library (can not access their site) and add code that detects the windowing system and does the right thing based on that. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Testing apps
Hello Bill, > > QASharp is available from Code Project. Although the code isn’t > great, it does things that challenge the SWF implementation. I’ve > read the status page and am aware that the comments below will be > caused by implementations that are not complete. > > > > 1) the ImageListStreamer doesn’t want to read the images for the > application’s ImageList control > > 2) ActiveMdiClient is not implemented (though Mdi windows do not > seem to work at all for this application) > > 3) RichTextbox properties are missing from the RTB > implementation (even as stubs) Could you file three separate bugs for those, so that we can follow up on each one of them appropriately? ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Default OpenDialog icons
Helll, > Here are some of original Windows icons ( I don't think Microsoft are > going to sue us for them ). I've tryed to merge them to > mcs/class/Managed.Windows.Forms/resources/System.Windows.Forms.en.resx > But the MWFResourceEditor/ tool dumps me out this when trying to save the > changes: We can not use the Windows icons, because they its artwork owned by Microsoft. We should be using some of the icons designed by the Ximian artists for the Gnome Desktop as a replacement, as those are free icons that we can legally use. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Howto mix WinForms and Cairo?
Hello, > I'm not sure I understand what you mean with 'mix'. The cairo contexts we > use are not accessible to your app (they are kept internal to libgdiplus). > You should be able to use Mono.Cairo without any problems, assuming you're > not trying to draw on Winforms' windows. That's a no-no, since you don't > have access to the X drawables you'd need to setup a cairo context. > The proper way to do that is to use System.Drawing, which is compatible with > Winforms. Whenever you want to draw on a window, you override OnPaint, and > as part of the events, you get a System.Drawing graphics context With that > context you can use any System.Drawing method to draw whatever you need. > > Maybe a description of what exactly it is you are trying to do would help. I wonder if the Winforms handles are X handles, and if so, they could be used with Cairo. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Re: Ongoing effort to upgrade Cairo to 0.5
Hello,
> so the development of porting is in closed way?
Nope, you just have to use the Anonymous repository:
www.mono-project.com/AnonSVN
miguel
>
> On Wed, 2005-08-10 at 17:05 +0200, Matthijs ter Woord wrote:
> > Vladimir,
> >
> >
> > It would be funny when you could logon using Miguel's credentials.
> >
> >
> > Greets,
> >
> > Matthijs
> >
> >
> >
> > ----- Original Message -
> > From: "Vladimir Moushkov" <[EMAIL PROTECTED]>
> > To: "Miguel de Icaza" <[EMAIL PROTECTED]>
> > Cc: "Mono Winforms" <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 10, 2005 5:02 PM
> > Subject: Re: [Mono-winforms-list] Re: Ongoing effort to upgrade Cairo to 0.5
> >
> >
> > > On Wed, 2005-08-10 at 10:52 -0400, Miguel de Icaza wrote:
> > > > Hello,
> > > >
> > > > > It seems that Cairo guys froze their API:
> > > > > http://lists.freedesktop.org/archives/cairo-announce/2005-August/25.html
> > > > >
> > > > > My be porting effort should continue now.
> > > > > Is there any progress already ? Can I help with something?
> > > >
> > > > There is a hard to debug crash that Hisham posted about that would be
> > > > nice if someone debugged.
> > > >
> > > > >
> > > > > regards,
> > > > > vlindos
> > > > >
> > > Where can I get latest libgdi sources ?
> > > svn
> > > ssh://[EMAIL PROTECTED]/source/branches/libgdiplus-cairo-upgrade
> > > doesn't work ("Permission denied")
> > >
> > > -vlindos
> > >
> > > ___
> > > Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
> > > http://lists.ximian.com/mailman/listinfo/mono-winforms-list
> > >
> >
>
--
Miguel de Icaza <[EMAIL PROTECTED]>
Novell, Inc.
___
Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Re: Ongoing effort to upgrade Cairo to 0.5
Hello, > It seems that Cairo guys froze their API: > http://lists.freedesktop.org/archives/cairo-announce/2005-August/25.html > > My be porting effort should continue now. > Is there any progress already ? Can I help with something? There is a hard to debug crash that Hisham posted about that would be nice if someone debugged. > > regards, > vlindos > -- Miguel de Icaza <[EMAIL PROTECTED]> Novell, Inc. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Threading problem
Hello, > Is there currently a problem with threading and winforms? If I run an > app which uses System.Threading and winforms, I get the following when I > quit Winforms is not a multithreaded toolkit. You must use Control.Invoke to perform Winform calls from a different thread. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Re: Ongoing effort to upgrade Cairo to 0.5
Hello, > I'm tyring to get libgdiplus working fully with Cairo from CVS (0.5+) > and I seem to have hit a problem in gdip_pen_setup (GpGraphics > *graphics, GpPen *pen) in the following: > > cairo_matrix_multiply (&product, &pen->matrix, > &graphics->copy_of_ctm); > cairo_set_matrix (graphics->ct, &product); Do you have a sample C# test case to debug this against? > On other notes, some of the features work, you can try out the test > program (image drawing) and some of System.Drawing also works with > this. Does Winforms start up with it? Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] MWF painting VERY slow compared to .NET
Hello, > Slowness of MWF drawing comes from Cairo. MWF uses libgdiplus for drawing, > libgdiplus uses cairo/libpixmain backends for drawing and uses version > 0.3.0 of Cairo. Currently Cairo is version 0.5.2. The problem is that > Cairo isn't yet stable project as API is changed even on minor version > change. On mailing lists of Cairo there is talk of soon releasing of > version 1 which means freezing the API. But 'soon' could be month or year > by my opinion. Although Cairo is known to be a part of the problem, another part of the equation might be the event loop processing. I do not remember the details, but Gtk+ spent quite a bit of time dealing with improving their main loop and event processing to improve performance. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Realist time frame
Hello, > I'm putting together a research proposal which will involve mono and use > MWF. Realistically, how far off is a full implementation? It's just so I > know roughly what to put into the paperwork. We are very close to feature completion at this point, a lot of work remains on testing and qa: a lot of applications need to be put through the API, bugs reported, fixed and so on. We will likely open a beta in late August to get people's input on this. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] transparency on a window
Hello, > Is there a solution to implement transparency on a window ? I know that this > functionnality is not yet fully supported with System.Windows.Forms, but is it > possible with Gtk# ? And if yes, please could you show me were can I find > information or sample code about this ? Eventually it will be supported, it is not very hard, but it will require major upgrades to your windowing system. So do not expect this to work on the short-term. In the medium-term (6 months from now) most Linux distributions will have all the components in place to make this happen out of the box. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Error running SWF app
Hello, > Sorry all, this is probably easy but I can't figure it out. I was > running fine until I just updated from SVN (my source was maybe a week > old). Now I get the following when I run a test app; obviously it > can't find the X11 lib. SWF apps were working prior to my updating > from SVN; did something change? I have libX11.so.6.2 in my > /usr/X11R6/lib/ directory, and that path is in my /etc/ld.so.conf file > (if that provides any info). I had the exact same issue, I had to edit my LD_LIBRARY_PATH to point to /usr/X11R6/lib to make it work. Am not sure why this is happening, I think the intention was to not depend on the "-devel" packages which are the ones that ship the version-less .so In this process, someone forgot to test the code. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] No updates on http://mwf.mono-project.com/
Hello, > http://mwf.mono-project.com/ > Latest date which present at root page is [28. January 2005]. > This cite looks like there is no mwf development. > Its blog has same problems. We moved most content to the Wiki in February-March, we should probably add redirects on mwf.mono-project.com. Since Jan 28th, 2005 there have been 338 commits to the mailing list, and also the following release statements have been made since that release, these are copied from the Mono release notes: Extensive progress on the Windows.Forms support code since the March 18th release. Jackson wrote a new double-buffering framework to bring our implementation in line with the expected behavior. Databinding is now supported on this release (simple and complex data binding), not all controls are ready though, controls that support it: ListBox, CheckedListBox and ComboBox (Jackson and Jordi). Alexander Olk implemented the file dialogs and did various touch-ups to other dialogs and widgets. Complete widgets: ImageListStreamer (Jackson), Prototype widgets: DataGrid widget and data container widgets (Jordi) and RichTextBox (Peter) Windows.Forms continues to improve in every part of the toolkit. In addition to Jordi, Peter and Jackson's ongoing contributions, Alexander Olk contributed various of the common dialogs code; Jonathan Chambers contributed the Property Grid widgets and Geoff Norton continued to maintain the OSX driver. > 1.1.7 release under windows has same problems as 1.1.6 > (no RichEdit, bad background clearing,strange items in Forms.controls list > (my application thinks that there must be only that objects which the > application add in it, but some of them has but type and casting throws an > exception, the application works under MS winforms fully correct)) > Image.FromStream - is also absent (i hope 1.1.8 fixes this bug too). As you can see from the release notes RichEdit is still in prototype mode. The best thing to do is to file a bug report for every problem you are aware of, so we can properly track this issue. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Error building mono
Hello, > Probably a simple question (not simple to me, as I can't figure it out). When > compiling mono with the latest source from svn (running FC3) I get: > > libtool: link: `checksums.lo' is not a valid libtool object > > Anybody want to send me a clue? It seems like corruption if you interrupt a compilation, so it leaves these empty files. Just do make clean; make ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] basic assistance
Hello, > > For now, you must do this from a Terminal. > > > > Actually, no; just open up /Applications/Utilities/Console.app and the > macpack application will log all exceptions/console output to there. > > > But it sounds like Macpack is a good candiate to have a Windows.Forms > > front-end that is itself macpacked! > > > > Due to the state of the OSX driver; this should probably be a cocoa# > app for now; not a MWF app. Using MWF means that it is self-contained in the mono/mcs package set. > PS> My report on "problems" is garnered from a quick email catch up; I > could be mistaken so take it with a grain of salt; I'll follow up later > this week > -- Miguel de Icaza <[EMAIL PROTECTED]> ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] basic assistance
Hello, > At the risk of sounding completely stupid, how do I "run what macpack > generates"? If I double-click in the Finder, the app silently does > nothing. How do I run it from the command line to see the stderr? Is > there a place where mac apps output there stderr and I don't know about > it? For now, you must do this from a Terminal. But it sounds like Macpack is a good candiate to have a Windows.Forms front-end that is itself macpacked! Miguel ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] MWF no more
Hello, > After update my X server to XOrg 6.8.2 from compiled sources i can't > run MWF apps anymore, maybe this is because i'm using an old glibc > version (2.2.4). When i try to run any MWF app i got this error posted > here: > > http://pastebin.ca/6912 > > The same doesn't happens with Gtk#. Try running mono under gdb, and get a stack trace once the thing breaks. Something like this: gdb mono (gdb) handle SIGPWR ignore noprint pass (gdb) handle SIGXCPU ignore noprint pass (gdb) run program.exe ... (gdb) where ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] libgdiplus/System.Drawing patch: native support for indexed Bitmaps
Hello, > Please find attached the following files: > > * libgdiplus.diff (patch -p0 in ./libgdiplus) > * System.Drawing.diff (patch -p0 in ./mcs/class/System.Drawing) > * lockbits.tgz (tar zvfx in ./) >From my quick review of the code, this looks great. The has_next and stream processing routines seem to only be used in one routine, so am left wondering if it might not be best to have those as static functions so the compiler could inline some of it. What is the performance impact on applications after this change? Jordi, Peter, do you have any objections on getting this into the tree? In any case, the code looks very solid, I would like to offer you an SVN account as well. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Documentation
Hello, > The code doesn't have to be complete to be documented. The APIs are well > known. Yes, the only problem is that our tool that produces the "stubs" to document has not been stress tested enough, so you might save yourself some trouble by just documenting the pieces that are complete. Miguel. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
