- renamed several functions
46 lines of code changed in 1 file:
merge 5.3 changelog to trunk (DAV test checkin)
18 lines of code changed in 1 file:
* use !LocallyModify for several flags
117 lines of code changed in 12 files:
- added LocallyModify::old_value()
2 lines of code changed in 1 file:
merge from e4fix [8417]
9 lines of code changed in 1 file:
- no longer re-activate modal windows (which forced them to re-popup and follow the mouse). Did not work properly on all WMs.
2 lines of code changed in 1 file:
- cppchecked (1.53)
153 lines of code changed in 30 files:
- GBK_system error no longer gives hint to look at console window, when it failed to start that window
12 lines of code changed in 1 file:
* use
- 'urw bookman l' as replacement for ps-Avantgarde
- 'liberation sans narrow' as replacement for ps-Helvetica-narrow
* added some new fonts (mostly fixed fonts)
- increase chance user finds a scalable-monospaced font on his system
* check
- font-array-sizes @ compile time
- valid xfig-fallbacks @ DEBUG runtime
83 lines of code changed in 3 files:
* decide on a per-font-basis whether ARB uses a scalable font or not
- previously the decision only depended on scalability of "-adobe-times-medium-r-*--.."
* replaced debug flag by ifdef-DUMP_FONT_LOOKUP
* fixed a crash when trying to dump information for unloaded scalable fonts
60 lines of code changed in 2 files:
- avoid to save mapfile if MEMORY_TEST==1
5 lines of code changed in 1 file:
* property file loading
- missing fallback for 'Save loaded Properties' when no saved properties existed yet
- GB_login now always prints full-path of loaded properties to console
22 lines of code changed in 3 files:
* cosmetic questions changes
4 lines of code changed in 2 files:
* renamed menu separator functions
* removed macro AWMIMT
270 lines of code changed in 20 files:
* added 'Never ask again' switch to most modal question dialogs. This is a workaround to make it possible to work with macros where modal questions are used. See also #179
- added unique IDs to all calls to aw_question / AW_repeated_question::get_answer
- replaced most calls to aw_popup_ok with aw_message (most of them only worked-around the non-standard way of EDIT4 to show aw_message)
* added 'Reactivate questions' to all properties menus
* hardcoded unused default-params from aw_ask_sure, aw_popup_ok + aw_popup_exit
317 lines of code changed in 42 files:
* AWT_reactivate_all_advices
- renamed into AW_reactivate_all_advices
- moved into AW_insert_common_property_menu_entries
* call this from all ARB applications
* move properties menu rightmost in ARB_PARSIMONY
37 lines of code changed in 12 files:
add aw_question include forgotten in r8355
1 lines of code changed in 1 file:
* removed unused default-param from AW_repeated_question
* use AW_repeated_question in GDE-reimport (used similar inline code)
* replaced a few more uses by aw_message / aw_ask_sure
33 lines of code changed in 4 files:
* moved aw_question() and relatives into aw_question.hxx
85 lines of code changed in 56 files:
- change result expected by unit-test (according to [8351])
37 lines of code changed in 1 file:
keep a bit more data when cleaning an ARB DB for PT-server use
* the SAIs HELIX and HELIX_NR in addition to ECOLI
* all of presets/
We need the latter to keep the ARB file sufficiently complete to be opened
by arb_ntree. Previously, GBT_get_alignment_width would fail. NT_repair_DB
would cause a segmentation fault. Keeping all presets costs a bit of
memory/space, but the ability to open a database from lib/pts for
inspection seems more important than saving a few bytes (and fixing
NT_repair_DB much more difficult).
For the same reason, I think HELIX and HELIX_NR should be kept, as they
are expected by BI_helix. Since the cost is negligible, I'd argue for
keeping them just in case.
(Alternative solution, not pursued: always keep a cleaned and a full copy
of the ARB database in lib/pts, possibly changing the suffix on the
cleaned databases to express that they are no longer compatible)
4 lines of code changed in 1 file: