/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /* * This file is part of the LibreOffice project. * * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. * * This file incorporates work covered by the following license notice: * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed * with this work for additional information regarding copyright * ownership. The ASF licenses this file to you under the Apache * License, Version 2.0 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
class LogicalFontInstance; namespace vcl::text { class ImplLayoutArgs; } namespace basegfx { class BColor; } class SalGraphics; class GlyphItem;
// all positions/widths are in font units // one exception: drawposition is in pixel units
// Unfortunately there is little documentation to help implementors of // new classes derived from SalLayout ("layout engines"), and the code // and data structures are far from obvious.
// For instance, I *think* the important virtual functions in the // layout engines are called in this order:
// * LayoutText() // * AdjustLayout(), any number of times (but presumably // usually not at all or just once) // * Optionally, DrawText()
// Functions that just return information like GetTexWidth() and // FillDXArray() are called after LayoutText() and before DrawText().
// Another important questions is which parts of an ImplLayoutArgs can // be changed by callers between LayoutText() and AdjustLayout() // calls. It probably makes sense only if one assumes that the "string // related inputs" part are not changed after LayoutText().
// But why use the same ImplLayoutArgs structure as parameter for both // LayoutText() and AdjustLayout() in the first place? And why // duplicate some of the fields in both SalLayout and ImplLayoutArgs // (mnMinCharPos, mnEndCharPos, mnLayoutFlags==mnFlags, // mnOrientation)? Lost in history...
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.