Ram.Type-0
Ram.Type-0
@GrabYourPitchforks How about just adding link to `OpCodes.Cpblk` at "See also"?
> You mention that "MudNavMenu layout is still broken," but you don't specify in what way. NavMenu is designed to appear just under the AppBar, but when I add padding...
I also have simple solution that define CSS class which adds additional padding or margin seems to be good. But I think this solution could not handle NavMenu&AppBar issue
> This seems like something that should be handled entirely on the MAUI end. PWA on iOS have safe area (even if we do not set `viewport-fit=cover`) and it is...
> Thanks. Do you have a GitHub repository I can try running on my Galaxy S23 to replicate it? Here is repro. https://github.com/RamType0/MudBlazorSafeAreaIssue But I am not sure if this...
> この問題は`context.Observe(ndmfMeshSimplifier)`を用いず、以下のようにextract/compareを実装するとほぼ再現しなくなると思います。 > > ``` > context.Observe(ndmfMeshSimplifier, c => c.target, (a, b) => a.Kind == b.Kind && a.Value.Equals(b.Value)); > context.Observe(ndmfMeshSimplifier, c => c.options, (a, b) => a.Equals(b)); > ``` >...
https://github.com/RamType0/Markdig.Renderers.MudBlazor/blob/master/Markdig.Renderers.RazorComponent/Components/ColorCodeBlock.razor `ColorCode` would be good library for this.
Why you don't count js dependencies as external dependencies?
> #1334 でtrace and optimizeでは実装されてますがこれが動いてない、または単体のコンポーネントとして必要ということでしょうか Trace and Optimizeも有効化してましたが、サブメッシュのマージがされず、複数の同じマテリアルが一つのメッシュに割り当てられたままになっていました
TTTを使わずに手動で同じマテリアルを複数割り当てて、Trace and optimizeでマテリアルの並び替えを許可しても変わりませんでした