Hi,
I submitted a pull request that fixes a problem in MWF, reported as
https://bugzilla.xamarin.com/show_bug.cgi?id=23869: when
TextImageRelation is set to anything other than Overlay the image moves
correctly when the button is pressed but the text doesn't move. If there
is no image at all then
Hi,
I'm working on some improvements on the experimental Pango rendering
support (see my pull request
https://github.com/mono/libgdiplus/pull/27 in libgdiplus for details).
In doing so I came across some deficiencies in the MWF code that aren't
noticeable with the current Cairo rendering.
The
Hi,
I'm working on some improvements on the experimental Pango rendering
support (see my pull request
https://github.com/mono/libgdiplus/pull/27 in libgdiplus for details).
In doing so I came across some deficiencies in the MWF code that aren't
noticeable with the current Cairo rendering.
The
From: Miguel de Icaza [mailto:mig...@xamarin.com]
There is no need to presume, the actual issue was just articulated on a
thread, please read it.
Pull requests do not work well with Mono. They need to be discussed in the
mailing list
Did I miss something? Do you not recognize that
On 21/10/2014 13:05, Edward Ned Harvey (mono) wrote:
From: Miguel de Icaza [mailto:mig...@xamarin.com]
There is no need to presume, the actual issue was just articulated on a
thread, please read it.
Pull requests do not work well with Mono. They need to be discussed in the
mailing list
Hi,
At my firm we are running multiple webapplication using mono (nginx +
fastcgi-mono-server2.exe) on a cluster of 4 VM, 2 vcpus.
One of them is restarted every day at 1h45 (small memory leak).
3 weeks ago we went from 8VM with 1vcpu (no restart problem) to 4VM with
2vcpus, and now,
it's the 3rd
Hi
since this PR https://github.com/mono/mono/pull/866, if you set
globalization responseEncoding=utf-8/, charset=utf-8 isn't added to the
content-type header, thus breaking all accents ... (http default charset is
ISO-8859-1)
I've sent a radical PR (https://github.com/mono/mono/pull/1338) to
Did I miss something? Do you not recognize that there's a problem here?
Yes, you did not read my email on the other thread.
What are we supposed to do when we do all that stuff - discuss in mailing
list, pay for Xamarin, contact Xamarin support, file or find bug in
bugzilla, and even write
Unfortunately there were issues, most obviously with an exception trying
to show a textbox.
So I read up on how to file a bug report
(http://www.mono-project.com/community/bugs/make-a-good-bug-report/) and
did so, with a test case that shows the problem in a straightforward
manner.
Glad
On 21/10/2014 16:18, Miguel de Icaza wrote:
Unfortunately there were issues, most obviously with an exception
trying
to show a textbox.
So I read up on how to file a bug report
(http://www.mono-project.com/community/bugs/make-a-good-bug-report/)
and
did so,
And that's impossible without some level of time-investment in engagement
- such as having somebody respond to bug reports even if this is to say
sorry this is unmaintained - your problem
Seems like you just volunteered to do this for all the bugs that come in
for Windows.Forms :-)
If only
On 21/10/2014 16:37, Miguel de Icaza wrote:
And that's impossible without some level of time-investment in
engagement - such as having somebody respond to bug reports even
if this is to say sorry this is unmaintained - your problem
Seems like you just volunteered to do this
On 21.10.2014 13:05, Edward Ned Harvey (mono) wrote:
From: Miguel de Icaza [mailto:mig...@xamarin.com]
There is no need to presume, the actual issue was just articulated
on a thread, please read it.
Pull requests do not work well with Mono. They need to be
discussed in the mailing list
Did
Hi,
As I continue to try to get on top of the odyssey that is building Mono
for Windows I came across an oddity over at Appveyor.
It appears the latest Windows Mono 3.2.3 release tarball available from
the mono-project link below is actually 3.3.0/master sneakily
masquerading as 3.2.3.
Seems
Hi all,
I'm still working through implementing methods to mvc/webapi, however, I've
found that the newer versions of WebApi are reliant on async controllers.
Now, my perception is that this means that the note on the mono
compatibility page around the Async Pipeline needs to be implemented for
On 21/10/14 15:40, Etienne Champetier wrote:
How can i run the unit test on windows/.net?
Build the code in mcs/class/System.Web/Test/ as an assembly, and run it
with NUnit (in particular, you can just run the tests
WriteHeadersNoCharset and WriteHeadersHasCharset from class
From: Miguel de Icaza [mailto:mig...@xamarin.com]
I have not seen you discuss any pull requests on the mailing list. Did I miss
something?
In order to respond to this question, I just reviewed all the history of my
pull request, but there was a lot of volume in disjoint places (github,
17 matches
Mail list logo
