Mercurial > pidgin.yaz
view README.CVS @ 8506:887c0259b47b
[gaim-migrate @ 9242]
" 6: Using CTRL+Up to get back a previous line breaks the
formatting on any new text entered on that line. Text,
while being entered appears extremely small, and when
it's sent, the formatting is slightly smaller and may
lose other elements of formatting.
the problem was that in the key_press_cb in gtkconv.c
was using
gtk_text_buffer_get_text(gtkconv->entry_buffer, ...);
this was not giving us the html tags. So I changed it
to gtk_imthml_get_markup(GTK_IMHTML(gtkconv->entry));
Then I added a signal so that the toolbar gets update
when gtk_imhtml_append_text_with_images is called so
that the toolbar can be updated as well.
I also rename the format_functions_update to
format_buttons_update since it, to me atleast, makes
more sense and because I couldn't think of a better
name than format_function_update, which would have been
very confusing.
theres one issue that I was not able to fix in this.
I'm planning on looking into it later, but after
ctrl-up/down the closing tag gets added and ends at the
last character from the buffer. Which means formatting
returns to normal (ie plain text) if you type after
you've used ctrl-up/down." --Gary Kramlich
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Fri, 26 Mar 2004 14:14:16 +0000 |
parents | 17a446f5e99b |
children | e4a27c9aec4c |
line wrap: on
line source
If you plan to use gaim CVS, PLEASE read this message in its entirety! Gaim is a fast-moving project with a somewhat regular release schedule. Due to the rate of gaim development, CVS undergoes frequent bursts of massive changes, often leaving behind brokenness and partial functionality while the responsible developers rewrite some portion of code or seek to add new features. What this all boils down to is that CVS _WILL_ sometimes be broken. Because of this, we ask that users who are not interested in personally tracking down bugs and fixing them (without a lot of assistance from the developers!) avoid CVS and use releases. Since releases will be made often, this should not prevent anyone from using the newest, shiniest features -- but it will prevent users from having to deal with ugly development bugs that we already know about but haven't gotten around to fixing. If you are interested in hacking on gaim, please read README and HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note that they may be somewhat out of date at times.) Win32 developers, please read README.mingw. By far the best documentation, however, is the documented code. Not all parts of gaim have yet been documented, but the major subsystems are falling fast. If you have doxygen, you can use the Doxyfile in the toplevel directory to generate pretty documentation. Otherwise (or even if you do!), the header files for each subsystem contain documentation for the functions they contain. For instance, conversation.h contains documentation for the entire gaim_conversation_* API, and account.h contains documentation for the gaim_account_* API. If you have questions, please feel free to contact the gaim developers by email at gaim-devel@lists.sourceforge.net, on IRC at irc.freenode.net in #gaim, or via the sourceforge forums at http://www.sourceforge.net/projects/gaim. Please do as much homework as you can before contacting us; the more you know about your question, the faster and more effectively we can help you! Send patches to gaim-devel@lists.sourceforge.net or post them in the Sourceforge forums at http://www.sourceforge.net/projects/gaim.