| [ Return to Bugs & Features | SVN ⇄ GIT ]
STR #3433
Application: | FLTK Library |
Status: | 1 - Closed w/Resolution |
Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
Scope: | 3 - Applies to all machines and operating systems |
Subsystem: | Documentation |
Summary: | Add contents of Article #415 on resizing to the docs |
Version: | 1.4-current |
Created By: | greg.ercolano |
Assigned To: | engelsman |
Fix Version: | 1.4.0 |
Fix Commit: | c132ac564ed46464c05de0a70e2afc3822916a67 |
Update Notification: | |
Trouble Report Files:
Trouble Report Comments:
|
#1 | greg.ercolano 22:45 Nov 10, 2017 |
| Subject says it all; include actual images instead of ascii art.
Here's the article: http://www.fltk.org/articles.php?L415
I'd suggest making a special section for resizing, as it's a tricky thing to understand.
And since Fl_Group is responsible for all resizing, it's existing section describing how the demo works should also link to the new section. | |
|
#2 | engelsman 16:09 Jul 06, 2020 |
| I would like to tackle this STR as an introduction to Github, pull requests, and because it "only" involves documentation.
I already have some code for generating layouts and images similar to the ascii art in Article #415, and which could possibly become examples in their own right. They will need to be updated for new headers, footers, copyright, urls, etc.
For the moment, I only intend to create a resize.dox page between custom.dox and editor.dox, and to draw on the text from Article #415. After that, the figure numbers in later chapters will need to be bumped... | |
|
#3 | greg.ercolano 17:37 Jul 06, 2020 |
| Sounds good to me -- obviously I haven't had time to get around to it. | |
|
#4 | engelsman 16:15 Jul 10, 2020 |
| Created pull request 102 containing text and images
Figure numbering in new chapter and following ones to be updated. Inline Fl_Group documentation should also point to new chapter.
Programs for generating images to be attached in separate request.
D. | |
|
#5 | engelsman 16:34 Jul 14, 2020 |
| Created pull request 104 with the examples/resize code, tidied up a bit since I generated the images for the dox.
Not sure that the code is the clearest it could be as examples of resizing, and it's a standalone directory
D. | |
|
#6 | engelsman 01:12 Jul 15, 2020 |
| The new resize documentation describes the case where the resizing involves stretching the group from its original size. There's nothing there about shrinking the group below its initial size, but I do remember seeing a note somewhere about setting a minimum size for height/width, or was it a range, but I'm afraid that I don't remember the details.
There should also be a note somewhere, in Fl_Group maybe, that it is advisable, or good practice, that widgets do not overlap or extend outsize the group boundary. | |
|
#7 | AlbrechtS 05:09 Jul 21, 2020 |
| Can we close this STR?
If yes (I think so) please don't forget to add the Git commit number.
Thanks. | |
|
#8 | engelsman 00:04 Jul 25, 2020 |
| Fixed in Git repository.
This is the last in a series of three related commits:
First commit: 70385593387e1f47549e050c3aaea047a96bc7a2
add resize documentation as per STR3433 add resize chapter to documentation, plus images, based on Article #415: How does resizing work? https://www.fltk.org/articles.php?L415 see also https://www.fltk.org/str.php?L3433
Second commit: 46c1500bf37077713742a04bf47ef90405016f39
fix doxygen links in Fl_Group.H fix dead links to Fl_Group::resizable(Fl_Box *box) reorder paragraphs to highlight different behaviour add link to new "How does resizing work?" chapter in dox
Third commit: c132ac564ed46464c05de0a70e2afc3822916a67
add resize examples as per STR3433 add example code for creating images for resize.dox based on Article #415: How does resizing work? https://www.fltk.org/articles.php?L415 see also https://www.fltk.org/str.php?L3433 | |
[ Return to Bugs & Features ]
|
| |