-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Breadcrumb - Cannot Add items to Root via the designer. #665
Comments
@Wagnerp |
Hi @giduac Can you provide a video of the bug/exception? |
@Wagnerp there you go, No exception there. Design time |
Hi @giduac Thanks for posting, looks as if something is missing |
All works in NET48 |
Could this difference be it (taken from KryptonContextMenuCollections.cs) . According to the docs for Type.AssemblyQualifiedName [Editor( @"Krypton.Toolkit.KryptonContextMenuCollectionEditor, Krypton.Toolkit", typeof( UITypeEditor ) )] [Editor( @"Krypton.Toolkit.KryptonBreadCrumbItemsEditor", , typeof( UITypeEditor ) )] |
Might be, lets check |
Hi @giduac Yes, that works. It'll be in tomorrows nightly build. |
Did a search for these editor attribute strings and there are several that are missing the assembly name.
|
Hi @giduac Could you possibly retest using |
@Wagnerp I've added the Editor line also to the items property and that seems to work. You might give this a try yourself... and add it to the next Nightly?? |
Will be in tomorrows nightly build |
Hi @Wagnerp, I build the Palette Designer locally without packages and added a BreadCrumb to it. And it actually doesn't work. The order of the TargetFrameworks in the .csproj file dictates which toolkit.dll is active in the designer. In this case it works in the designer. <TargetFrameworks>net48;net5.0-windows;net6.0-windows</TargetFrameworks> And in this order not. So the first TargetFrameworks is the one that is loaded <TargetFrameworks>net5.0-windows;net6.0-windows;net48</TargetFrameworks> And as soon as you create an app with NuGet packages and target anything except net48 it doesn't work. Just like building the app in the source tree So that editor line on the items property has no effect. |
Hi @giduac I think for V7 (aka 70.22.11.xx), separate packages for pre .NET Core could be on the cards, i.e. Legacy packages? |
@Wagnerp |
Been looking around a bit, and found some info. As it looks it could be connected to the WinForms Designer's for .Net3/5/6. ongoing development. dotnet/winforms#4304 |
To test the info above I also tried it with KTreeView. Just like the BreadCrumb, KTreeView node editor also doesn’t work with Net3/5/6 At runtime the Nodes editor is accessible from a property-grid. Just like the BreadCrumb. |
KContextMenu KryptonContextMenuCollectionEditor derives from CollectionEditor Net48 works normal At runtime all .NET versions can start the editor and edit items. |
A possible workaround would be to include net48 as the first framework in the In that way the project can be edited from the designer and when compiling this goes into to the higher .Net version. Edit: |
That would need to be done on the developers part, since the packages already contain binaries from 4.6.2 - .NET 6/7 (nightly releases) |
Yes a workaround on the dev's side. But it's not ideal. The odd one out is the KNavigator pages editor. That one does work. And is derived from the same class as the others. |
More investigation needs to be done, I don't think this can be done in the April 2022 build. But a workaround will be noted in the readme. |
Also needs keeping an eye on the status of the ongoing development of the WinForms designer for the higher .NET versions. |
Announced discussion has been opened here: |
Trying to use net48 causes the majority of my program to break (it complains I can't use the C#8 and later features). Not sure if this is considered a great workaround. |
@Smurf-IV Hasn't this been recently fixed or am I imagining it? |
I have noticed that the Framework tends not to work as expected in Preview builds of Visual Studio, and one it is released, it then takes a patch update to get the .net48 designer working again. (Like it currently is for 17.8.p1) |
Describe the bug
The RootItem/Items collection is not accessible via the designer.
Works in NET480
Does not work in Net31/50/60
Tried several TK version including stable, canary and nightlies.
To Reproduce
Add a KBreadcrumb to the form
Try to add items
Expected behavior
N/A
Screenshots
N/A
Desktop (please complete the following information):
Additional context
Items can be added programmatically.
The text was updated successfully, but these errors were encountered: