[Mono-winforms-list] MonthCalenar Problem with Mono 2.10.6 and WinForms
Hi, there! I created a WinForms app in Linux, thinking it would work flawlessly in Windows... However, it does only work right (as created) with Mono for Windows, not with .NET in windows. The calendar looks bad, it appears duplicated, and if you click in the next or last arrows, then it always advances abuot four months. Here is the app in Mono 2.10.6 correctly running on windows (as in mono for linux): http://img202.imageshack.us/img202/2596/winformsmonthcalendarmo.png Here is the very same app (same binary) running on windows, with native .NET: http://imageshack.us/photo/my-images/267/winformsmonthcalendardo.png/ Any idea? ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Start an App right after login
Hi, Assuncao, I tried many different ways to add an executable (winforms) created in C# using mono to start automatically after login, but all my attempts didn't work. Does anyone know how can I do it? I'm running my application on Raspbian (Debian distro). So you are trying to achieve that in a Linux distro. Anyway, I think that what you are describing is more related to a installer or something like that, than to the C#/mono program itself. The best way I can think of is to create a .desktop file, like the ones you can find in /usr/share/applications, and copy it to the .config/autostart directory of the user. -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Regression in Winforms Support for version 3.0
Hi, all of you. I've finally found a solution to this problem by myself. Since probably many people will stumble upon this, I think it is better to somehow register it. The problem seems to be in System.Drawing. When you try to launch an application using WinForms, it crashes with: == Unhandled exception ...snip... Missing dll: /tmp/install/lib/libgdiplus.so == This is particularly confusing on Windows, where one would think this file should be already present. The key to this problem is already in the Xamarin bugtrack system, bug 8309: https://bugzilla.xamarin.com/show_bug.cgi?id=8309 The problem seems to be related to the following two lines in the file $INSTDIR\etc\mono\config: == dllmap dll=ggdiplus target=/tmp/install/lib/libgdiplus.so / dllmap dll=ggdiplus.dll target=/tmp/install/lib/libgdiplus.so / == Being INSTDIR the installation directory of mono. Note that this happens in Windows, maybe that etc could be confusing, but it is just a subdirectory of the mono installation. Removing both lines immediately solves the problem. == Because bugs happen :) Locate $mono-prefix/etc/mono/config and add an os=!windows attribute to all gdiplus gdi32 DLL mapps. == Thanks Robert. I found the solution just before reading your message. I suppose I've been more taxative. This bug invalidates the use of this version of Mono for any final user trying to run an application employing WinForms, and there are quite a lot out there. An yep, bugs happen. However, the bug was found in 11/2012 (mono 3.0.1), and bug 14586, a duplicate of this bug, was (re-)found in 09/2013. Currently, in 4/2014 (mono-3.2.3), the bug has not still been solved, while the fix seems just to add an os=!windows attribute to those lines. I understand that WinForms is not a valuable asset for Xamarin, but this seems strange anyway. -- Baltasar ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Problem loading WinForms
Hi, HelenCR, That symptoms seem to corresond with an application compiled for an old .NET version. Recompile the application for .NET 4. -- -- Baltasar ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] [Announcement] Winforms GUI Generator
Hi, there! This is to announce the work of Adolfo Álvarez, who created a Winforms application which makes it possible to build basic to medium (in complexity) interfaces. It creates an XML file which can be later loaded in your app in order to create the GUI and connect the signals. There is a GitHub repository here: http://github.com/aalvlopez/generadorWinforms/ User manual (unfortunately, docs in Spanish, though images are self-explanatory): http://github.com/aalvlopez/generadorWinforms/tree/master/Documentacion/Manual%20de%20usuario Example application: http://github.com/aalvlopez/generadorWinforms/tree/master/ProbandoLibreria Hope you like it. -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
[Mono-winforms-list] Building Managed.Windows.forms.dll
Hi, there, I'm trying to help solve a bug in Windows forms, specifically that unresolved one that makes apps crash when one edits any text field in a DataGridView, after a second time. However, while I was able to compile a DLL thanks to Stifu, when the app is initialising it complains about 'keyboard.resources' Not being available. In the resources folder of the Manages.Windows.Forms directory, there is a promising create-keyboards.sh which compiles create-keyboards.cs and executes create-keyboards.exe I tried that, and it generated keyboards.resx (not 'keyboards.resources'). I tried to include it in the Managed.Windows.Forms project anyway, but compilation then fails because of the 'create-keyboards' assembly missing. I tried to include create-keyboards.exe above as a referenced assembly, but that did not work. Any clue? Thanks, -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] WinForms designer
http://stackoverflow.com/questions/27884840/what- should-be-done-to-integrate-winforms-editor-into-monodevelop What should be done to integrate WinForms designer into monodevelop? Is there the templates for MonoDevelop to create WinForms applications? What is the current state of these works? Your link does not work, at least for me. It's easy to create a WinForms application, even lacking a designer: you just need to know about Panels, and the design is just a recursive task. If you still want a designer, then you should maybe consider using SharpDevelop: http://www.icsharpcode.net/OpenSource/SD/ ...which includes a Windows Forms designer. If you still want a designer to work with MonoDevelop, then you could consider the work of one of my students. It is 1) a designer that generates an xml version of the interface, and 2) a framework which is able to rebuild an interface from the xml file. The main advantage of this is that you can change the GUI quite independently of the source code. ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] Mono-winforms-list Digest, Vol 110, Issue 2
Hi, Windows Forms is no longer mantained. The mono team considers Winforms deprecated, in the sense that it should not used to create new software. About your specific issue, this is probably related to the windows forms implementation in mono (via System.Drawing). In this FAQ: http://www.mono-project.com/docs/faq/winforms/ They say that you must be running a composite desktop in order to be able to have transparency in your windows. This means to me that your best bet is to have an alternative display mode in which you don't rely in transparencies. -- baltasar ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Re: [Mono-winforms-list] WinForms deprecated?
> > I don't understand how WinForm can be deprecated? > > The whole point is to get to easily cross-platform deployment and > fracturing the GUI element wrecks that capability. > Well, I'm not a Mono Team authority, but yes it is. You can find an e.mail thread in which Miguel de Icaza reports that WinForms is buggy and incomplete: "Hey, Mono has an implementaiton of Windows.Forms, but it is both old, unmaintainted and known to have some bugs. Some people have been able to use it effectively, but we do not currently have an active maintainer, so we encourage developers to pick something like Gtk# instead." I've been unable to find something like that quoted text in the oficial mono pages for WinForms... due to this, people will continue to try to use it as a valid asset. >From what other people has been reporting here, using WinForms in a Mac is a complete nightmare, so you can only create cross-platform apps for Linux and Windows, in any case, while Gtk# works for all three platforms. > I was gearing up to work on a Wayland back-end to WinForms ... is this a > lost cause now? > I will answer that in a generic way: if the use you have to make of WinForms is valid for your application, then you can do it. But if you find something that does not work, then you're lost and alone. -- baltasar ___ Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-winforms-list
