The following lines:
sys_fontlist[i].fi_hostfontsize =
atom_getintarg(3 * best + 2, argc, argv);
sys_fontlist[i].fi_width = atom_getintarg(3 * best + 3, argc, argv);
sys_fontlist[i].fi_height = atom_getintarg(3 * best + 4, argc, argv);
are how Pd finds out the actual font size from teh Tk front end; in Pd extended the font patch comments these lines out, so Pd assumes the font size is exactly as specified. This leads to problems like clicking on one place and getting text selected in another. I never understood why the lines were commented out.
I'm not sure how wise it is to make a relase of Pd that depends on having a particular font installed... looks like this breaks a lot of machines.
cheers Miller
On Tue, Oct 23, 2007 at 08:01:16PM -0400, Hans-Christoph Steiner wrote:
Yup, you don't have Bitstream Vera Sans Mono working/installed. It
has a distinctive lower L..hc
On Oct 23, 2007, at 7:15 PM, Luke Iannini (pd) wrote:
Here's a new pic demonstrating the issue, by the way (I'll add it
to the tracker) The 1px wide canvas is demonstrating where I am clicking, and the
actual cursor is visible to show the result.On 10/23/07, Luke Iannini (pd) <lukexipd@gmail.com > wrote:
Sounds good to me! I think my biggest "blocker"-level issues with
the extended 0.40.3 builds are the mismatched font-cursor handling
in object-boxes with the new fonts, and the inability to use >~/ mtx_*~ and so on (though I believe IOhannes may have fixed that
recently?).What mismatched font cursor handling? If there's a bug, please
report it on the tracker. :-)I did, and apparently it was fixed : ). Anyway, the description is
exactly the same: http://sourceforge.net/tracker /index.php? func=detail&aid=1650752&group_id=55736&atid=478070Can this be reopened or should I submit a new one?
Cheers Luke
<Picture 1.png>
kill your television
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list