On Fri, 2016-04-08 at 14:38 +0000, Jonathan Wilkes via Pd-list wrote:
Hi list, Here are some binaries to test out the alpha 0 release for the GUI port of Pd-l2ork.
Wow.. impressive work you've done and I think I'm not even remotely able to grasp what it meant to achieve this. I very much like its native look (I checked on Ubuntu 14.04). Also the GUI tab in the preferences dialog, very neat. And the canvas zoom is probably going to be _the_ killer feature with all the hi-res displays coming up.
Some observations (from Ubuntu 14.04 i386):
'vanilla' would use bold fonts.
I sometimes have to click on Menus twice for the selected item to show up. I couldn't figure out a reliable pattern. Affected entries: 'Media->Test Audio and Midi' or 'Edit -> Preferences'
I can't load many of my patches in this nw-version of Pd-l2ork. When I do so, the patch canvas never appears and I get repeating messages 'watchdog: signaling pd..' on stderr. The process 'nw' uses 100% of a core and I have to kill pd-l2ork. Some simple patches work fine and I haven't figured out a pattern of what kind of patches are affected which are not. However, the behaviour of a certain patch is consistent (either it loads always ok or it never does so). UPDATE: Not true. It just takes that much time to load the patch. The one I just loaded took more than 2 minutes to load.
What version of Pd-vanilla is this based on? Or is not related to vanilla anymore? I stopped caring about Pd-l2ork when I figured it contains some fixes that shifts position of iemguis around. This renders a lot of my patches unusable because they are not displayed in the GOP area anymore. I'd love if patches would work in both flavors, but right now it seems as a patch author you need to decide one.
Is it correct that externals for Pd-l2ork are binary-incompatible with externals built for Pd-vanilla? I'm just interested to know, maybe this isn't such a huge issue, since Pd-l2ork has so many externals pre-compiled.
Roman