They are both extracted there
But when I was investigating this last night then I inspected the sqlite DB there.
And when I only have RawPng in the package then the DB has records in it. But when it has both RawPng and RawBmp in it then the DB only has Table structure and no records at all.
Helpful!
If you stuck on it later on then I can try to send you the setup when I come in. (am outside painting since its literally first day of the summer where i see the sun)
I’ve already found the problem. The package loader loads the first library it finds, not the named one. I wasn’t thinking that we needed more than one library per platform per package when this was designed. Easy fix in the grand scheme of things.
I could do it somehow else, in separate package for each file format or something. I segment them since the whole amount of dylibs is over 100 mb once I pile in all the high tech new age file formats into it. And most users only use one. (Unless their making some sort of Graphic converter app)
It should still be able to handle that and strip down to only what they need. That’s something we’ll need to test.
But yeah, the whole reason so much of Buoy is in packages is that they are things that not everyone will want in their projects and would otherwise bloat our relatively small deliverables.
Try 0.38.0
It worked now ! Thanks
Hey everyone. We’ve entered a phase where I’m mostly doing bug fixes for a while. I have roughly 60 triaged bugs and feature requests in the backlog including the 17 public issues on the Buoy-releases site to get through.
Please keep testing and thank you for being part of this journey!
Did you think about the possibility of just skipping the old Win32 UI API and going WinUI ?
(Since WinUI runs on Win10 and Win11, so which I assume are your targets anyhow)
I looked into that first and what I found is that Microsoft is still making large breaking changes between releases even with WinUI3.
We may have to go the route that Xojo took and offer a Xaml container until MS gets their act together.
There is definitely no clear cut in it or right or wrong answer. Its in some way been almost 20 year wait for Microsoft and always new and new framework and then scrap it. And the mess is probably big reason why non OS frameworks have gained some ground.
Another problem with WinUI especially if we don’t want xaml is WinUI 3 ships in the Windows App SDK, which is not in-box: you either self-contain it (you own the CVE cadence) or require the framework package (a deployment dependency on the end user’s machine). I find that to be a heavy lift for a tool that is otherwise cross platform without outside dependencies.
I’m having trouble wrapping my head around two concepts as they relate to buiding a UI with the View block format and the Layout Editor:
Communication between controls (via classes inheriting from these controls to allow event handling):
I have a View containing a ComboBox subclass and a HTMLViewer subclass. The HTML data displayed in the HTMLViewer depends upon the value selected in the ComboBox. How do I refer to the HTMLViewer instance in the ComboBox SelectionChanged handler to tell it that the selection has changed and that needs to reload its contents?
Accessing information from model classes by Control subclasses within a View:
Here I have a few model classes that need to be read and written to by TextFields, Checkboxes and Labels within a View. If I assign references to these model classes into properties of the View subclass itself during the Window’s Opening() event handler, how do I access them from each TextField? Do I need to have a reference to the model classes inside each Control subclass? Or can the parent View’s properties be accessed somehow by child Controls?
This same problem applies to a second view containing a Canvas to plot a custom graph and Sliders to change the plot scale. The Canvas needs access to the model classes.
Thanks in advance to anybody who can clear this up for me. Perhaps the View block documentation needs to be fleshed out a bit to address issues like this.
You don’t need to inherit from the controls any more to handle events.
Check out the example projects on my Word Component for Buoy. I updated them all last week to use the new style in Buoy, which gives you far far easier way to do the UI, and handle the control events.
Thanks. I didn’t remember that.
Another question:
When using View block format, how do you specify that a TextField’s FieldType should be Number or Password?
I have not actually tried that on text block but…even if the designer has not many properties yet then I have had success in setting properties just by typing them in the block format.
Like here I type in the Text property which the designer does not support yet>
Control Label lblDepth2
Frame = (523, 475, 491, 20)
Text = "Depth:"
End Control
So from that then I imagine the properties you need to set the field type should also work there.
I tried setting the FieldType that way, but it didn’t work because FieldType is read-only and set when the TextField is first created. Since there’s no way to add arguments when using the View block format, there’s no way to create a specialized TextField. I think what’s needed is the ability to write:
Control TextField(FieldType.Number) field1
Frame = (523, 475, 491, 20)
Text = "20.0"
End Control