I can't compile as a universal binary with Perl support and pretty
much nobody ever requested Perl support so...
> Anyway, ran:
>
> ./configure \
> --enable-gui=macvim
> --enable-perlinterp
>
> Forced it to build in 32 bit mode (a few libraries aren't ready for 64 bit,
> don't know about Vim itself).
>
> The compile itself goes fine until I run xcodebuild... Getting the following
> when it tries to build the icons:
>
> PhaseScriptExecution "Make Document Icons"
There have been a number of threads about this in the past week or so.
Check the archives.
> The app it produces works well, perl works, but for what ever reason,
> transparancy doesn't work (I get a white mask over the window when I adjust
> the transparency level, but it doesn't actually affect the alpha).
That's a new bug which I can confirm. I'll put it on my todo...thanks
for letting me know about it.
Björn
Does anybody have a clue why transparent views no longer work on Snow
Leopard? I just looked into this bug but I am a bit stumped. Calling
setAlphaValue: on the window containing the text view will make the
view transparent (as on pre-10.6) but it also makes the window itself
transparent (so you can see through the title bar for example).
Any help would be appreciated.
Björn
> Does anybody have a clue why transparent views no longer work on Snow
> Leopard? I just looked into this bug but I am a bit stumped. Calling
> setAlphaValue: on the window containing the text view will make the
> view transparent (as on pre-10.6) but it also makes the window itself
> transparent (so you can see through the title bar for example).
It does work for me with the old Tiger Build (Snapshot 49) on Snow
Leopard. Do you see it only with a new one build on Snow Leopard?
Frank
--
frank hellenkamp | interface designer
solmsstraße 7 | 10961 berlin
+49.30.49 78 20 70 | tel
+49.173.70 55 781 | mbl
+49.3212.100 35 22 | fax
jo...@depagecms.net
http://www.depagecms.net
http://immerdasgleiche.de
http://everydayisexactlythesame.net/
Indeed, snapshot 49 works but not my custom binary built for 10.6.
So, apparently something has changed in the 10.6 Cocoa framework which
breaks transparency. *sigh*
Björn
Hi Josh,
Use the official snapshot that I build instead, it fully supports
transparency (since it is built against the 10.5 SDK).
I am not working on the transparency issue: this feature was
contributed in the first place so I am not too familiar with it. I
poked around quickly but couldn't figure out how to fix it, thus I am
waiting for somebody who actually uses this feature (I don't) to fix
it and send me a patch.
Björn
I can confirm this.
I did a fresh built from git master (against both 10.5 and 10.6 SDK).
All I get is a grayed background in Vim but no transparency.
In addition I did try the same using the core-text branch,
which (apart from not being transparent at all) does some strange ghosting
when you scroll text with transparency < 100.
Cheers,
Shirk
----------------------------------------------------------------------
BitSpin.org :: don't get twisted up!
----------------------------------------------------------------------
Huh?! Transparency works for me when passing the "--with-macsdk=10.5"
to configure. Are you sure the compilation was ok (e.g. did you make
sure you didn't mistype something)?
Transparency _does_not_work_ when using the 10.6 SDK. This is what
has been reported already (click the link to the Issue report in
Joshua's post).
> In addition I did try the same using the core-text branch,
> which (apart from not being transparent at all) does some strange ghosting
> when you scroll text with transparency < 100.
Core Text does not support transparency (it never did) -- it's just
another one of these things that I haven't gotten around to.
Since transparency seems so important to many people I strongly urge
anybody who uses this setting to try to fix the outstanding issues
(fix 10.6 SDK, fix Core Text) and send me a patch. This is extremely
low priority for me at the moment since I do not use transparency at
all. Please help me out!
Björn
Let me reformulate that:
"The MacVim Core Text renderer does not support transparency (it never did)."
Obviously I am not claiming that the Core Text API does not support
transparency. ;-)
Björn
Since transparency seems so important to many people I strongly urge
anybody who uses this setting to try to fix the outstanding issues
(fix 10.6 SDK, fix Core Text) and send me a patch. This is extremely
low priority for me at the moment since I do not use transparency at
all. Please help me out!
>
> Huh?! Transparency works for me when passing the "--with-macsdk=10.5"
> to configure. Are you sure the compilation was ok (e.g. did you make
> sure you didn't mistype something)?
Holly Steve Jobs! You're right!
I did a separate compile in a new git checkout (same config flags) and now transparency works!
Strange enough.. make clean; git clean -fxd should have resulted in the same.
I can state that these flags work for me even on SL:
./configure --enable-perlinterp --enable-pythoninterp --enable-rubyinterp --with-features=huge --enable-gui=macvim --with-tlib=ncurses --enable-multibyte --with-python-config-dir=/System/Library/Frameworks/Python.framework/Versions/2.6//lib/python2.6/config/
Cheers,
Shirk
----------------------------------------------------------------------------------
BitSpinn.org - don't get twisted up!
----------------------------------------------------------------------------------
George Harker wrote the original transparency patch (search the
vim_mac archives). Unfortunately this is not going to be an easy fix
for anybody (I think) since the problem lies with some change within
the Cocoa frameworks between versions 10.5 and 10.6. I'm guessing the
best way to attack this problem is to look around and see if any other
app has working transparency code for 10.6 and try to adapt that.
Björn
Craig,
please have a look at my last reply to this topic.
I included my configure flags which will produce a working
transparency-supported AND
python2.6 capable build.
There is a typo in the --with-python-config-dir option (two slashes
before "lib"). Don't know if that is the problem since I've never
used that option myself (so I can't say for sure if it should work or
not). After the configure phase you can open up src/auto/config.mk to
make sure that all (Python) flags are set correctly. If not, just
edit the file, then make (note that calling "configure" will overwrite
that file though). (Don't ask me exactly what the "correct" flags
are...you'll have to experiment for yourself to figure that out.)
Björn
I'm sorry to tell you this but figuring out transparency is not the problem..
I had a look at this problem for some time now and I did come up with a fix
that enabled a completely transparent vim window (like afloat does).
This was irritating since everything - including the menu and toolbars
was transparent.
What seems broken (or changed) in 10.6 is the feature to have a transparent
View within an otherwise opaque window..
Cheers,
Shirk
----------------------------------------------------------------------------------
BitSpinn.org - don't get twisted up!
----------------------------------------------------------------------------------
Thanks for the suggestion: I did not take a look at it because of
Shirk's post saying the entire window is transparent (including the
title bar etc.).
Does anybody know of any other (open source) app that manages to do
transparency right on 10.6?
> I'm sorry to tell you this but figuring out transparency is not the problem..
I don't think we should give up quite yet...
> I had a look at this problem for some time now and I did come up with a fix
> that enabled a completely transparent vim window (like afloat does).
> This was irritating since everything - including the menu and toolbars
> was transparent.
I'm glad you took a look at the problem. I also managed to get to the
"everything is transparent" stage, but obviously that is not good
enough. The only way this would be useful is if we were to draw all
the window decorations manually and make sure they are opaque, but
this is a bit crazy.
> What seems broken (or changed) in 10.6 is the feature to have a transparent
> View within an otherwise opaque window..
Well, Terminal.app manages to do it...so it is definitely possible
(but probably only by using some private API).
By the way: transparency on pre-10.6 already did use a private API to
disable a window shadow or something like that. So anybody looking
into this problem need to keep the private API option in mind (it may
be the only way to get this to work). Again, the best thing would be
to find some other app that manages to do it and adapt that (obviously
Terminal.app won't be of much help here, unless somebody at Apple were
to give us a hint).
Björn
oops, disregard that, I'll post to the mailing list instead ^^
2009/11/18 Donuts <duf...@gmail.com>ah, too bad... but that reminds me, Adium has transparency where the title bar isn't affected... but I don't think they're open source.2009/11/18 René Köcher <shi...@googlemail.com>
On Thu, Nov 19, 2009 at 5:47 AM, björn <bjorn.w...@gmail.com> wrote:
> By the way: transparency on pre-10.6 already did use a private API to
> disable a window shadow or something like that. So anybody looking
> into this problem need to keep the private API option in mind (it may
> be the only way to get this to work). Again, the best thing would be
> to find some other app that manages to do it and adapt that (obviously
> Terminal.app won't be of much help here, unless somebody at Apple were
> to give us a hint).
In vim-cocoa I am using exactly the same piece of code (the private API
you mentioned) and transparency works out of box.
I didn't follow this thread lately so I'm not sure what your problem is,
is that related to linking with a specific SDK that could disable the
transparency?
- Jiang
On Thu, Nov 19, 2009 at 9:16 AM, Jjgod Jiang <gzj...@gmail.com> wrote:
> In vim-cocoa I am using exactly the same piece of code (the private API
> you mentioned) and transparency works out of box.
OK, this patch fixed the transparency problem by setting correct blend mode
(kCGBlendModeCopy instead of kCGBlendModeNormal) before using
CGContextFillRect().
Only for the Core Text renderer though.
- Jiang
Thanks a bunch Jiang! I can confirm that it works too.
Maybe the problem with the default renderer is due to some change in
NSTextView...? At any rate, the next snapshot will include the Core
Text renderer and I think most people will want to use that instead of
the default renderer anyway, so the transparency issue with the
default renderer may not be that urgent anymore.
Björn