A place for those passionate about port, and for those new to it. We hold lots of Port tastings: please join us!
https://www.theportforum.com/
I suspect that the people who mostly want that are people who regularly drink Port at The Bunghole using white wine glasses that are significantly larger than ISO or Reidel Port glasses.jdaw1 wrote:mostly, people want glasses divvied over however many sheets it takes, up to six glasses on each. The default does that.
Fair, but that is the target audience of the default behaviour.DRT wrote:I suspect that the people who mostly want that are people who regularly drink Port at The Bunghole using white wine glasses that are significantly larger than ISO or Reidel Port glasses.
jdaw1 wrote:Maybe something likeCode: Select all
/GlassesOnSheetsMode /SpreadOverSheets def  % /SpreadOverSheets /Custom /GlassesOnSheetsMaxPerSheet 6 def  % For all glasses on one sheet set to a big integer /GlassesOnSheetsCustom [ [ 0 1 2 3 ] [ 4 5 6 7 ] [ 8 9 10 11 ] ] def
jdaw1 wrote:Actually, maybe ‟GlassesOnSheets” could have a better name. Suggestions?
The new parameters look fine to me.jdaw1 wrote:any comment on either of:
Code: Select all
/GlassesOnSheetsMode /SpreadOverSheets def  % /SpreadOverSheets /Custom /GlassesOnSheetsMaxPerSheet 6 def  % For all glasses on one sheet set to a big integer /GlassesOnSheetsCustom [ [ 0 1 2 3 ] [ 4 5 6 7 ] [ 8 9 10 11 ] ] def
Aha! That made it click. GlassesOnSheets is an array that specifies each of the glasses, so it must contain a number of elements equal to the size of the other arrays that detail the Ports being consumed (CircleArrays, Titles, et al). Thank you.jdaw1 wrote:orCode: Select all
/GlassesOnSheets [ [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 ] ] defCode: Select all
/GlassesOnSheets [ [ 0 1 17 {} for ] ] def
I don't speak PostScript, so I won't attempt actual code. However, could GlassesOnSheetsMode specify either /Multiple or /Single? Specifying /Multiple would then require /GlassesOnSheetsMaxPerSheet to be defined, while specifying /Single would attempt to put all glasses on a single sheet. (Essentially setting /GlassesOnSheetsMaxPerSheet to the size of CircleArrays, Titles, et al.)jdaw1 wrote:I also don’t like the default of GlassesOnSheets. But, mostly, people want glasses divvied over however many sheets it takes, up to six glasses on each. The default does that. Please suggest an alternative parameterisation that would capture the two possible modes: auto ≤6; and truly custom.
Edit: Maybe something likeThat seems to come much closer to the intuition of what’s wanted, and keeps some nasty code out of the parameters. Objections?Code: Select all
/GlassesOnSheetsMode /SpreadOverSheets def  % /SpreadOverSheets /Custom /GlassesOnSheetsMaxPerSheet 6 def  % For all glasses on one sheet set to a big integer /GlassesOnSheetsCustom [ [ 0 1 2 3 ] [ 4 5 6 7 ] [ 8 9 10 11 ] ] def
Actually, maybe ‟GlassesOnSheets” could have a better name. Suggestions?
No. GlassesOnSheets is an array of arrays, outer length = number of sheets, innermostly holding pointers to the elements of Titles etc. But GlassesOnSheets can omit some elements of Titles, and can include duplicates.Glenn E. wrote:Aha! That made it click. GlassesOnSheets is an array that specifies each of the glasses, so it must contain a number of elements equal to the size of the other arrays that detail the Ports being consumed (CircleArrays, Titles, et al). Thank you.
If GlassesOnSheetsMaxPerSheet is, say, 9999, what’s the difference?Glenn E. wrote:However, could GlassesOnSheetsMode specify either /Multiple or /Single? Specifying /Multiple would then require /GlassesOnSheetsMaxPerSheet to be defined, while specifying /Single would attempt to put all glasses on a single sheet.
Effectively none. Having /Single would simply be an obvious shorthand method of setting GlassesOnSheetsMaxPerSheet appropriately. That functionality could also be covered by an appropriate comment.jdaw1 wrote:If GlassesOnSheetsMaxPerSheet is, say, 9999, what’s the difference?Glenn E. wrote:However, could GlassesOnSheetsMode specify either /Multiple or /Single? Specifying /Multiple would then require /GlassesOnSheetsMaxPerSheet to be defined, while specifying /Single would attempt to put all glasses on a single sheet.
I think it makes the code more readable and more understandable for the non-programmers who use it.jdaw1 wrote:But you prefer changing /Multiple to /Single to changing 6 to 9999? OK, I can live with that.
Nobody has ever said that to me before I’ll enjoy a moment of smugness.Glenn E. wrote:your commenting of the code is outstanding.
Obrigado.jdaw1 wrote:[(S) /atilde (o)]
(see www.jdawiseman.com/papers/placemat/plac ... oundstring).
Your ‟ã” is in a Windows encoding. If PS2PDF.com runs on a different OS, it might have a different encoding. Hence this robust and general ASCII-generated methodology.
Code: Select all
/GlassesOnSheets [
[ 0 1 2 3 4 ]
[ 5 6 7 8 ]
[ 9 10 11 12 13 ]
] defCode: Select all
/PageOrderingNonDecanterLabelGlasses [ GlassesOnSheets length {0} repeat ] defSorry, failed to notice this. Consider: arrange on as few sheets as possible subject to each sheet having ≤6. That’s the default. Now consider: arrange on as few sheets as possible subject to each sheet having ≤9999. That would be the same as saying ‟put them on one sheet”.DRT wrote:Does "For all glasses on one sheet set to a big integer" mean what it says, or should it say "For more or fewer than 6 glasses on one sheet set to the required integer"?
That feels like an integer, rather than a richer description of which glasses on which sheets.DRT wrote:Perhaps "GlassesPerSheet" describes it better?
My thought when suggesting /Multiple was to preserve the current default, which is to say that /Multiple implies however many sheets are required to keep the number of glasses per sheet at or below 6. My thought was also that when the number of glasses isn't evenly divisible by 6 that the glasses would be as evenly distributed among the required number of sheets as possible. So 5-5-4 rather than 6-6-2. I believe that all of that is how the software currently works, correct?jdaw1 wrote:But if we had done /GlassesOnSheets /Multiple def (start reading from post 448), we wouldn’t know the number of sheets.
Suggestions from programmer-type readers would be welcomed.
That feels like an integer, rather than a richer description of which glasses on which sheets.[/quote]DRT wrote:Perhaps "GlassesPerSheet" describes it better?
Correct.Glenn E. wrote:the glasses would be as evenly distributed among the required number of sheets as possible. So 5-5-4 rather than 6-6-2. I believe that all of that is how the software currently works, correct?
I think the problem is different. Several parameters are arrays of the same length as GlassesOnSheets (e.g., BackgroundTextsGlassesTexts, PageOrderingNonDecanterLabelGlasses and PageOrderingStickyLabels). Currently, at the moment those parameters are set, it is possible to know how long is the array GlassesOnSheets (length = GlassesOnSheets length, which is easy). But if GlassesOnSheets /Multiple def, then those parameters cannot know how long is GlassesOnSheets. Which would be difficult.Glenn E. wrote:At this point, though, I recognize that we are overloading /GlassesOnSheets. (It seems that I have not been a programmer for too long.) /Multiple and /Single are inappropriate for /GlassesOnSheets, but the functionality can be covered by something like what Derek is suggesting.
I have not dug into the code in depth, so the answer to this question may be obvious. Or obviously difficult.jdaw1 wrote:Currently, at the moment those parameters are set, it is possible to know how long is the array GlassesOnSheets (length = GlassesOnSheets length, which is easy). But if GlassesOnSheets /Multiple def, then those parameters cannot know how long is GlassesOnSheets. Which would be difficult.
In that long line of code embedded in the default value of GlassesOnSheets. So it would be trivially easy to replace the 6 by a parameter deffed the line before: /GlassesOnSheetsMaxGlassesPerSheetInDefault 6 def. Would that make you happier?Glenn E. wrote:At what point is the current behavior set to 6 glasses per sheet? Could the code that sets that to 6 instead use a new parameter /MaxGlassesPerSheet that could be explained and set by the user early enough to avoid the difficulty with knowing the length of GlassesOnSheets?
It is worth re-visiting an earlier observation on a related problem:PhilW wrote:perhaps by defining an array of default maximum glasses per paper-size or as an approximation based on paper length and width? This function is then used by the default /GlassesOnSheets (instead of '6')
The same problem is happening here: both code, and UI.As quoted [url=http://theportforum.com/viewtopic.php?p=44092#p44092]here[/url], a [url=http://www.conandalton.net/]competent programmer[/url], by email wrote:In the placemat code, the parameters lines are playing two roles - one as plain old code, another as user interface.
The problem is that the default value of several parameters needs the length of GlassesOnSheets. If that is absent or /Multiple, then its length is not known whilst the other parameters are being defined. That’s the problem.PhilW wrote:but that if the user had not provided a definition
I can see that issue based on the planned/updated implementation to allow use of /Multiple; I was suggesting an alternative - varying the original default definition of /GlassesOnSheets to take into account paper size for maximum number of glasses on each sheet; this should then be overridable by user with original syntax as previously; Similarly if no user definition were supplied then the default would set /GlassesOnSheets as it has done for the last few months (with the modification for page-size based limit on maximum glasses per page) and the length would thereby be being known for other parameters, as previously.jdaw1 wrote:The problem is that the default value of several parameters needs the length of GlassesOnSheets. If that is absent or /Multiple, then its length is not known whilst the other parameters are being defined. That’s the problem.PhilW wrote:but that if the user had not provided a definition