영어에서 Logical tree 을 사용하는 예와 한국어로 번역
{-}
-
Colloquial
-
Ecclesiastic
-
Ecclesiastic
-
Programming
-
Computer
Diagram of logical tree.
논리적 트리 다이어그램Diagram of logical tree.The DOM model represents a document with a logical tree.
DOM 모델은 문서를 논리 트리로 표현합니다.Diagram of logical tree.
논리 트리의 구성Composition of the Logical Tree.Categories: Board Game, Puzzles Tags: adornment, balls, baubles, board, color,en, logical, tree, xmas.
카테고리: 보드 게임, 퍼즐 태그: adornment, 불알, baubles, board, 색,EN, logical, 나무, xmas.For instance, the logical tree reports the Text value of a TextBlock, which is a string.
예를 들어 논리 트리는 문자열인 TextBlock의 Text 값을 보고 합니다. For instance, the logical tree reports the Text value of a TextBlock, which is a string.Overriding the Logical Tree.
논리 트리 재정의Overriding the Logical Tree.In most cases, the logical tree is a more useful representation of the elements in a WPF application.
대부분의 경우에서 논리적 트리는 WPFWPF 애플리케이션의 요소를 좀 더 유용하게 나타낸 것입니다. In most cases, the logical tree is a more useful representation of the elements in a WPFWPF application.Composition of the Logical Tree.
논리 트리의 구성Composition of the Logical Tree.The logical tree is used for resource lookup when both the logical tree and the visual tree are present.
논리 트리와 시각적 트리가 모두 있을 경우 논리 트리가 리소스 조회에 사용됩니다. The logical tree is used for resource lookup when both the logical tree and the visual The Purpose of the Logical Tree.
논리 트리의 용도The Purpose of the Logical Tree.Advanced control authors can override the logical tree by overriding several APIs that define how a general object or content model adds or removes objects within the logical tree.
However, resource lookup can also extend beyond the immediate logical tree.
그러나 리소스 조회는 직접적인 논리 트리를 넘어 확장될 수도 있습니다. However, resource lookup can also extend beyond the immediate logical tree.In addition to the concept of the logical tree, there is also the concept of the visual tree in WPF.
WPFWPF에는 논리 트리의 개념 외에 시각적 트리라는 개념도 있습니다. In addition to the concept of the logical tree, there is also the concept of the visual tree in WPFWPF.The LogicalTreeHelper class provides the GetChildren,GetParent, and FindLogicalNode methods for logical tree traversal.
LogicalTreeHelper 클래스는 논리 트리 순회를 위한 GetChildren, GetParent및 FindLogicalNode 메서드를 제공 합니다. The LogicalTreeHelper class provides the GetChildren, GetParent,and FindLogicalNode methods for logical tree traversal.Also, the logical tree provides a framework for certain notifications, such as when all objects in the logical tree are loaded.
또한 논리 트리는 논리 트리의 모든 개체가 로드된 경우 등의 특정 알림에 대한 프레임워크를 제공합니다. Also, the logical tree provides a framework for certain notifications, such as when all objects in the logical tree are loaded.Themes themselves can also reference system values outside of the theme logical tree if the resource references are dynamic.
테마 자체는 리소스 참조가 동적인 경우 테마 논리 트리 외부의 시스템 값을 참조할 수도 있습니다. Themes themselves can also reference system values outside of the theme logical tree if the resource references are dynamic.This topic defines what the visual tree and logical tree represent, discusses how such trees relate to an overall object tree concept, and introduces LogicalTreeHelper and VisualTreeHelpers.
이 항목에서는 시각적 트리와 논리적 트리가 나타내는 항목을 정의 하 고, 이러한 In order to appear in a UI at all, a ContentElement must be hosted in a content host that is both a Visual and a logical tree participant.
UI에 표시 되려면 ContentElement은 Visual 및 논리적 트리 참가자 인 콘텐츠 호스트에서 호스팅되어야 합니다. In order to appear in a UI at all, a ContentElement must be hosted in a content host that is both a Visual and a logical tree participant.Both the visual tree and logical tree are synchronized with the current set of application elements, reflecting any addition, deletion, or modification of elements.
시각적 트리와 논리적 트리 둘 다 현재의 애플리케이션 요소 집합과 동기화되므로 요소의 모든 추가, 삭제 또는 수정이 반영됩니다. Both the visual tree and logical tree are synchronized with the current set of application elements, reflecting any addition, deletion, or modification of elements.This example of processing XAML into an object tree is so far seemingly an example where the created object tree is basically the logical tree.
지금까지 XAML을 개체 트리로 처리하는 이 예제는 생성된 개체 트리가 기본적으로 논리 트리인 경우로 보입니다. This example of processing XAML into an object Objects that are not in the logical tree can reference keyed resources, but the resource lookup sequence begins at the point where that object is connected to the logical tree.
논리 트리에 없는 개체는 키 지정 리소스를 참조할 수 있지만 리소스 조회 시퀀스는 해당 개체가 논리 트리와 연결되는 지점에서 시작됩니다. Objects that are not in the logical tree can reference keyed resources, but the resource lookup sequence begins at the point where that object is connected to the logical tree.However, for existing WPF properties that support property inheritance, property value inheritance is able to perpetuate through an intervening object that is not in the logical tree.
그러나 속성 상속을 지원하는 기존 WPF 속성의 경우 속성 값 상속은 논리 트리에 없는 중간 개체를 통해 지속될 수 있습니다. However, for existing WPF properties that support property inheritance, property value inheritance is able to perpetuate through an intervening object that is not in the logical tree.However, as you can see if you actually use the LogicalTreeHelper API, the logical tree sometimes contains nodes that are not either FrameworkElement or FrameworkContentElement.
그러나 실제로 LogicalTreeHelper API를 사용 하는 것 처럼 논리 트리에는 FrameworkElement 또는 FrameworkContentElement되지 않는 노드가 포함 될 수도 있습니다. However, as you can see if you actually use the LogicalTreeHelper API, the logical tree sometimes contains nodes that are not either FrameworkElement or FrameworkContentElement.As mentioned before, the route of any given routed event travels along a single and predetermined path of a tree that is a hybrid of the visual and logical tree representations.
앞서 언급했듯이 지정된 라우트된 이벤트의 경로는 시각적 트리와 논리 트리 표현이 혼합된 트리의 미리 결정된 단일 경로를 따라 이동합니다. As mentioned before, the route of any given routed event travels along a single and predetermined path of a The terms visual tree and logical tree are also used in the WPF documentation because these same trees are useful for understanding the behavior of certain key WPF features.
또한 WPF 설명서에서는 시각적 트리와 논리 트리라는 용어를 사용하는데 이러한 동일한 트리는 특정 주요 WPF 기능의 동작을 이해하는 데 유용하기 때문입니다. The terms visual tree and logical Therefore, both the parent that holds the original value and the child object that inherits thatvalue must both be FrameworkElement or FrameworkContentElement, and they must both be part of some logical tree.
따라서 원래 값을 포함 하는 부모와 해당 값을 상속 하는 자식 개체 모두 FrameworkElement 하거나 FrameworkContentElement해야 하며 둘 다 논리적 트리의 일부 여야 합니다. Therefore, both the parent that holds the original value and the child object that inherits that value must both be FrameworkElement or FrameworkContentElement,and they must both be part of some logical tree.Basically, the logical tree is an approximation of a run time object graph at the framework level, which excludes visuals, but is adequate for many querying operations against your own run time application's composition.
기본적으로 논리 트리는 시각 효과를 제외한 프레임워크 수준의 런타임 개체 그래프와 유사하지만 고유한 런타임 애플리케이션의 구성에 대한 많은 쿼리 작업에 적합합니다. Basically, the logical tree is an approximation of a run time object graph at the framework level, which excludes visuals, but is adequate for many querying operations against your own run time application's composition.In Windows Presentation Foundation(WPF), there are two ways that the complete objecttree is conceptualized and can be reported to its public API: as the logical tree and as the visual tree. .
WPF(Windows Presentation Foundation)Windows Presentation Foundation (WPF)에서 완벽한 트리 구조는 논리 트리와 시각적 트리라는 두 가지 방법으로 개념화하고 공용 API에 보고할 수 있습니다. In WPF(Windows Presentation Foundation)Windows Presentation Foundation (WPF), there are two ways that the complete object In WPF, only logical tree nodes can have a Resources property that contains a ResourceDictionary, therefore there is no benefit in traversing the visual tree looking for keyed resources from a ResourceDictionary.
WPF에서 논리적 트리 노드만 ResourceDictionary를 포함 하는 Resources 속성을 가질 수 있으므로 ResourceDictionary에서 키가 지정 된 리소스를 찾는 시각적 트리를 트래버스하는 이점을 누릴 수 없습니다. In WPF, only logical tree nodes can have a Resources property that contains a ResourceDictionary, therefore there is no benefit in traversing the visual tree looking for keyed resources from a ResourceDictionary.
