search

pure-data / pddp

Pure Data Documentation Project
9 stars 2 forks source link

[expr]-help: string-subpage is too high #246

Closed umlaeute closed 2 weeks ago

umlaeute commented 2 weeks ago

my laptop has a native resolution of 1920x1080.

The string-functions has a screen-height of ´1083` pixels (according to the patch file), which does not account for window bars and other decorations. which in turn means that the entire subpatch is not visible.

i think that the documentation patches should all have a reasonable maximum size, that fits on a 1024x768 screen.

porres commented 2 weeks ago

I already worked that out in my doc updates branch

porres commented 2 weeks ago

hmmm, I see you probably mean already the new changes I made. I said it because the original one (and the original changes weren't made by me) were even using a higher vertical range

porres commented 2 weeks ago

the resolutions I have to choose from on my macbook air are

1024x666 / 1280x832 / 1470x956 (default) and 1710x1112

I was using the default one...

my laptop has a native resolution of 1920x1080.

I think this is a good standard for current computers. I get older ones don't have this resolution, but worst case scenario people can just scroll.

How about I use the lower 1280x832 resolution I have?

umlaeute commented 2 weeks ago

i was referring to the original documentation. thanks for addressing it.

but worst case scenario people can just scroll.

Unfortunately not (or rather: I guess this is highly dependent on the window manager you use).

Pd automatically enables scrolling if the patch contents are outside the desired size of the window (rather than the actual size ( - this might be a bug in Pd... or not). as of https://github.com/pure-data/pure-data/commit/6f9a4077513bd9b997714495c8e574b81b58cb41, the content fits nicely into the requested 692x1083 pixel window (as the lowest element is a numberbox at +65+1034).

so no scrollbars appear.

since my window decorations take 60 pixels from the top of the window the numberbox lies outside of the visible canvas area (which goes down to 1020) fullscreen-expr

I still think that 1024x768 is a better maxsize (with my "look how old-school we are" attitude ;-))

umlaeute commented 2 weeks ago

btw, here's a quick way to sort the subpatches by size:

# sort by height
grep  "^#N canvas " *.pd | sort -nk 6

# sort by width
grep  "^#N canvas " *.pd | sort -nk 5

(at least with GNUsed, i haven't checked on Darwin)