Matthias Melcher wrote: > [STR Closed w/Resolution] > > Fixed in Subversion repository.
First of all, thanks for doing all this work. Looks good so far :-) > I hope that you all like the changes. fl_message and friends can now take > HTML formatting by starting the message text with "<html>". <a href=...> > style links are resolved by calling fl_open_uri(). All this now works very > nicely for creating a somewhat usable "About" box and much more. > > Link: http://www.fltk.org/str.php?L1626 > Version: 1.1-current > Fix Version: 1.1-current (r5792) However, there are some points I'd like to have changed: The fixed width of 410 pixels doesn't seem appropriate to me, and is not compatible with the previous versions of fl_ask() and fl_message(). I'm using some messages with wider text lines with embedded line breaks (\n) to format the text, but these preformatted text lines get broken by the shorter line width. I tried to make the window resizable at least, and here is my patch: fltk-1.1/src$ svn diff Index: fl_ask.cxx =================================================================== --- fl_ask.cxx (revision 5798) +++ fl_ask.cxx (working copy) @@ -163,7 +163,8 @@ h = max_h + 30 + msg_inp_h; message_form->size(w, h); - message_form->size_range(w, h, w, h); + message_form->size_range(w, h); + message_form->resizable(message_form); message->resize(20 + 50, 10, message_w, message_h+10); icon->resize(10, 10, 50, 50); @@ -250,6 +251,7 @@ if (!prev_icon_label) icon->label(iconlabel); resizeform(); + message_form->init_sizes(); if (button[1]->visible() && !input->visible()) button[1]->take_focus(); =================================================================== However, this (first try) patch leaves the size range (min values) at the width and height of the rendered text with the width of 410 pixels, and this doesn't look good - and the user has to resize the window, if s/he knows how to do at all. The previous version resized the widget according to the rendered text width and height. I'm aware that HTML rendering is a totally different story, but wouldn't it be possible to treat HTML and plain text differently? If so, this would be the most compatible way to the former behavior. Any ideas, opinions ? Regards Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
