[timunie]

No description provided.

[AppVeyorBot]

❌ Build IconPacks.Avalonia 1.4.0-Update-Avalonia.17.build.100 failed (commit a5bab0dd50 by @timunie)

[AppVeyorBot]

✅ Build IconPacks.Avalonia 1.4.0-Update-Avalonia.18.build.101 completed (commit 07484ed227 by @timunie)

[AppVeyorBot]

✅ Build IconPacks.Avalonia 1.4.0-Update-Avalonia.19.build.102 completed (commit c277021ca3 by @punker76)

[AppVeyorBot]

✅ Build IconPacks.Avalonia 2.1.0-Update-Avalonia.9.build.109 completed (commit 6b04444c36 by @punker76)

[insomniachi]

is there a way to just get the upgrade to version done? I've been blocked for almost 2 months

[leixao]

is there a way to just get the upgrade to version done? I've been blocked for almost 2 months

I also look forward to its early release.🙏

[insomniachi]

is there a way to just get the upgrade to version done? I've been blocked for almost 2 months

I also look forward to its early release.🙏

As a work around i'm using that path data from the icon browser and using it directly as path icons

[tsgsOFFICIAL]

is there a way to just get the upgrade to version done? I've been blocked for almost 2 months

I also look forward to its early release.🙏

As a work around i'm using that path data from the icon browser and using it directly as path icons

You don't have to wait on an official release to unblock yourself. You can reference the package straight from source in the meantime, this means once a release is (hopefulle soon) out, you just have to swap sources.
It's a few extra lines but it works today:

1. Pull the repo in as a submodule:

git submodule add -b Update-Avalonia https://github.com/timunie/IconPacks.Avalonia.git externals/IconPacks.Avalonia

2. Reference the specific pack(s) you use directly by .csproj, instead of the NuGet package:

<ItemGroup>
    <ProjectReference Include="externals\IconPacks.Avalonia\src\IconPacks.Avalonia.PhosphorIcons\IconPacks.Avalonia.PhosphorIcons.csproj" />
    <ProjectReference Include="externals\IconPacks.Avalonia\src\IconPacks.Avalonia.SimpleIcons\IconPacks.Avalonia.SimpleIcons.csproj" />
</ItemGroup>

3. Load each pack's style in App.axaml:

<Application.Styles>
    <FluentTheme />
    <StyleInclude Source="avares://IconPacks.Avalonia.PhosphorIcons/PhosphorIcons.axaml" />
    <StyleInclude Source="avares://IconPacks.Avalonia.SimpleIcons/SimpleIcons.axaml" />
</Application.Styles>

4. Use it in AXAML: same iconPacks namespace regardless of which packs you add:

<!-- Root element -->
xmlns:iconPacks="https://github.com/MahApps/IconPacks.Avalonia"
<!-- Body -->
<iconPacks:PackIconPhosphorIcons Kind="House" Width="18" Height="18" />

Hopefully this explains it good enough, otherwise you're more than welcome to ping me on Discord

[ZzZombo]

To those who look forward to trying this ^ out, it still doesn't seem to work. Although I didn't fully follow the instructions given in that because I used to use the full package, I also didn't bother with referencing just the actually used packages and referenced the full one as well.

EDIT: I just realized all of them still reference the v11.x of Avalonia. So either I screwed this up somehow or?..

[punker76]

I will be update the lib after my vacation. So end of August is my deadline 🤪

[tsgsOFFICIAL]

To those who look forward to trying this ^ out, it still doesn't seem to work. Although I didn't fully follow the instructions given in that because I used to use the full package, I also didn't bother with referencing just the actually used packages and referenced the full one as well.

EDIT: I just realized all of them still reference the v11.x of Avalonia. So either I screwed this up somehow or?..

Hey ZzZombo, if you're reffering to my previous comment you most likely forgot to target the correct branch.

If you need help, do feel free to ping me, or wait for the soon to come official repo.to.be updated (Yay!🥳)

Ps. I am in no way affiliated with this repo, I'm just an eager supporter :⁠-⁠P

[ZzZombo]

@tsgsOFFICIAL: thanks for the heads-up, this did it! It works! FWIW, the branch is Update-Avalonia.

Edited the wrong person mentioned.