1. 07 Nis, 2013 31 kayıt (commit)
  2. 06 Nis, 2013 9 kayıt (commit)
    • Tor Lillqvist's avatar
      Need more headers to make sure we have CGRect · d0d2c12a
      Tor Lillqvist yazdı
      Change-Id: I8766ba5258f923d47474fa77e14eb7fbff530ffc
      d0d2c12a
    • Tor Lillqvist's avatar
      Add some more interesting sources · 99bf1f24
      Tor Lillqvist yazdı
      Change-Id: Id0fdba93a5d3a46a79cebea8839bdfd467ef4f6f
      99bf1f24
    • Tor Lillqvist's avatar
      NSLogging changes · f3dbb35c
      Tor Lillqvist yazdı
      Change-Id: I42991d7a9c9e0bd4a023739051393935efa5c29f
      f3dbb35c
    • Tor Lillqvist's avatar
      Remove unused variables · a85c0279
      Tor Lillqvist yazdı
      The LayoutManager for some reason has both a ToolbarLayoutManager
      pointer field, and a uno::Reference to an aspect (or whatever term one
      should use) of the same ToolbarLayoutManager. (I.e. esssentially two
      fields for the same thing. Why it doesn't create such variables where
      needed instead I don't know.)
      
      Anyway, for some reason there were lots of instances where a local
      variable was initialised with this second field but then never used. I
      removed those. (Surely just copying the field into a local variable
      doesn't have any interesting side effect that would explain this
      pattern?)
      
      Change-Id: Ibdfbd9476c39d3e83b58e81469b94d9a87444ca8
      a85c0279
    • Tor Lillqvist's avatar
      Bin some not longer interesting NSLogging · 49c3be89
      Tor Lillqvist yazdı
      Change-Id: I1afd93fc9a56e85a30991bce9ca2350764cf1ec2
      49c3be89
    • Tor Lillqvist's avatar
      Pre-cache type_info for com::sun::star::ucb::InteractiveAugmentedIOException · 9e6afcf1
      Tor Lillqvist yazdı
      It seems to be the type_info most commonly looked up dynamically, even
      the only one in an initial test. I think it is a good idea to avoid
      dlsym() if possible.
      
      Change-Id: I0379c534e10efefafdd253ee651f6c74e4aa47d5
      9e6afcf1
    • Tor Lillqvist's avatar
      Simplify after 6215c718a5884ed7301b97dc9f7e3f1d1f9ce96c · 2b8be1c6
      Tor Lillqvist yazdı
      Change-Id: If0a6296c9b226c479413b475788d0c11d6ee7318
      2b8be1c6
    • Tor Lillqvist's avatar
      We need to acquire the yield mutex here · 8ed93fef
      Tor Lillqvist yazdı
      Otherwise we get an assertion failure in a dbgutil build from the
      DBG_TESTSOLARMUTEX() in OutputDevice::ImplReleaseGraphics() when
      quitting, at least in 64-bit LO on OS X.
      
      Change-Id: Ieb54e6b58033279f807fe91f4f6139018f643903
      8ed93fef
    • Tor Lillqvist's avatar
      Create a justified line if asked to · 6a0c8c72
      Tor Lillqvist yazdı
      The end result is still not satisfactory but it is getting closer.
      
      Oh how nice it would have been to have some clean useful documentation for how
      the text layout machinery works. The number of entry points in the low-level
      "backends" (like CoreTextLayout) is quite small, so I doubt it would have
      required lots of text to document the "protocol" used between the upper layers
      and the layout machinery. Now one just have to use educated guessing aided by
      lots of debugging printout. But this is true for most of the codebase, of
      course.
      
      Change-Id: I791f190819a187418865279f6a5b4aa598e01d3c
      6a0c8c72