Bill Medland billmedland@mercuryspeed.com writes:
Bill Medland (billmedland@mercuryspeed.com) Allow runtime increase in the maximum number of fonts processed.
Do we really need a config parameter for that? Actually, do we really need a limit at all?
On January 8, 2004 04:45 pm, Alexandre Julliard wrote:
Bill Medland billmedland@mercuryspeed.com writes:
Bill Medland (billmedland@mercuryspeed.com) Allow runtime increase in the maximum number of fonts processed.
Do we really need a config parameter for that? Actually, do we really need a limit at all?
No idea.
Can you pass something to XListFonts to say "no maximum"?
I had a client who actually (seemed to) fell over that limit (using x terminals etc.). It seemed that a trace message that told the client to change a compile-time constant wasn't much help. So I made the change. That was ages ago. (It didn't actually help; there were other issues; I don't remember).
Anyway, if you don't want it then throw it away.
Bill Medland billmedland@mercuryspeed.com writes:
No idea.
Can you pass something to XListFonts to say "no maximum"?
I guess INT_MAX would work, though I haven't tried it. If it doesn't work we can keep the current limit, but then double it and retry until we get all fonts.
It seemed that a trace message that told the client to change a compile-time constant wasn't much help. So I made the change. That was ages ago. (It didn't actually help; there were other issues; I don't remember).
Anyway, if you don't want it then throw it away.
Well, if you encountered the problem we might as well fix it. And I agree the message is pretty much useless, we should do better than that.
-
Alexandre Julliard -
Bill Medland