Please examine the example file attached in my previous post.
You can remove my graphical assets, copy and paste yours onto the stage, do use the Windows Output Inspector panel to configure accordingly.
My example goes fullscreen and transparent straight out of the box, unless you paste in another clear at layer level 1 when you bring your assets into my posted example, something I'd encourage you to do, just so you can see what does and doesn't make QB go full screen.
The picture you posted is like in QB itself, but you will need to set the full scxreen stuff up in QC when editing the .qtz to go to build.
I personally find that nowadays I am creating the comp to be built , then putting the comp into my 'empty' QB template, configuring shadow, opaque, clear, etc, etc as I require saving that as compbuild.qtz [whatever name for compbuild] and away I go.
hm...
i don't have an "Windows Output Inspector panel" in QC, where is this?
Do you use the QB Advanced settings to define the window dimensions?
If I type in 1920x1200 (my monitor resolution) i get about 1920x500 on screen.
If I leave the QB advanced settings empty, i get a small borderless window on my desktop.
-The option to check off whether or not something opens up in fullscreen is controlled via the Quartz Builder template "output window" macro.
-The option to make something borderless happens only once you "drop" the composition into Quartz Builder. At that point, one has to go to the "Advanced Settings" on the actual Quartz Builder app interface, and check off the "Borderless" option.
Hopefully this will clear it up, as any posted comp/app might not make the step of "borderless" 100% clear, as this happens after everything in the template is set up.
thanks. I start to get a hang of it. I wasn't aware a template is needed to add this feature, I just assumed and old composition could be compiled to an application in QB (which works beautiful, just not full screen). Maybe in another version, you could add this to the Advanced settings dialogue in QB.
Do you not have QC setup to show you the templates when it opens? If you do, then you will see the Quartz Builder template as a choice.
I'm not sure what you mean by adding Advanced settings(?) - they are already there, hence the jpg's I posted to show you where they are, and the reason all of us are able to make fullscreen builds.
Granted, there's not an rtf walk through or anything.
Come to think of it, there are a lot of details about "how" to use it buried in some threads around here... I'm not sure if they are linked to the Quartz Builder talk page or not.
here we go, I never checked the templates, always sticked with the default. Much clearer now.
With the advanced settings I meant, doing the main settings of how the application fills a screen in QB not in QC. The advanced settings in QB does already allow some control (resizable, borderless, ...) but not to the same extend as the template does.
What I would like to see is having control over these parameters without the need of a QC template. But this is purely lazyness on my side.
volkerk wrote: What I would like to see is having control over these parameters without the need of a QC template. But this is purely lazyness on my side.
It's separated as it is now because there are basically 2 kinds of properties: immutable ones [things that can't change] (borderless -- a window can't change to/from borderless), and mutable ones [things that can]. The template exposes all the mutable properties, so the composition can control them dynamically. For example, there's a terminate output that will close the app. It makes absolutely no sense for that to be immutable (either the app would terminate on startup, or it would never terminate, and neither is particularly useful).
So basically, the template isn't going to get any simpler, ever (there's no reason to remove functionality). In fact, as gtoledo hinted, we've actually added more to it in 1.1. The immutable properties will also probably be growing as well -- we're adding a fullscreen property because it's been an endless source of problems, for example.
That's exactly what the Fullscreen output is for in the Quartz Builder template.
maybe i'm missing somthing here. my version does not have an option to activate fullscreen (borderless).
Yes, you are missing something indeed :-)
Please examine the example file attached in my previous post.
You can remove my graphical assets, copy and paste yours onto the stage, do use the Windows Output Inspector panel to configure accordingly.
My example goes fullscreen and transparent straight out of the box, unless you paste in another clear at layer level 1 when you bring your assets into my posted example, something I'd encourage you to do, just so you can see what does and doesn't make QB go full screen.
The picture you posted is like in QB itself, but you will need to set the full scxreen stuff up in QC when editing the .qtz to go to build.
I personally find that nowadays I am creating the comp to be built , then putting the comp into my 'empty' QB template, configuring shadow, opaque, clear, etc, etc as I require saving that as compbuild.qtz [whatever name for compbuild] and away I go.
Hope that helps.
hm... i don't have an "Windows Output Inspector panel" in QC, where is this?
Do you use the QB Advanced settings to define the window dimensions? If I type in 1920x1200 (my monitor resolution) i get about 1920x500 on screen. If I leave the QB advanced settings empty, i get a small borderless window on my desktop.
-The option to check off whether or not something opens up in fullscreen is controlled via the Quartz Builder template "output window" macro.
-The option to make something borderless happens only once you "drop" the composition into Quartz Builder. At that point, one has to go to the "Advanced Settings" on the actual Quartz Builder app interface, and check off the "Borderless" option.
Hopefully this will clear it up, as any posted comp/app might not make the step of "borderless" 100% clear, as this happens after everything in the template is set up.
Check the attach-a-mo-ments for where the pertinent locales are if anything is still unclear.
thanks. I start to get a hang of it. I wasn't aware a template is needed to add this feature, I just assumed and old composition could be compiled to an application in QB (which works beautiful, just not full screen). Maybe in another version, you could add this to the Advanced settings dialogue in QB.
Do you not have QC setup to show you the templates when it opens? If you do, then you will see the Quartz Builder template as a choice.
I'm not sure what you mean by adding Advanced settings(?) - they are already there, hence the jpg's I posted to show you where they are, and the reason all of us are able to make fullscreen builds.
Granted, there's not an rtf walk through or anything.
Come to think of it, there are a lot of details about "how" to use it buried in some threads around here... I'm not sure if they are linked to the Quartz Builder talk page or not.
here we go, I never checked the templates, always sticked with the default. Much clearer now. With the advanced settings I meant, doing the main settings of how the application fills a screen in QB not in QC. The advanced settings in QB does already allow some control (resizable, borderless, ...) but not to the same extend as the template does. What I would like to see is having control over these parameters without the need of a QC template. But this is purely lazyness on my side.
...and HIGHLY unlikely. If anything, I would imagine that MORE params will be added to the template.
It's separated as it is now because there are basically 2 kinds of properties: immutable ones [things that can't change] (borderless -- a window can't change to/from borderless), and mutable ones [things that can]. The template exposes all the mutable properties, so the composition can control them dynamically. For example, there's a terminate output that will close the app. It makes absolutely no sense for that to be immutable (either the app would terminate on startup, or it would never terminate, and neither is particularly useful).
So basically, the template isn't going to get any simpler, ever (there's no reason to remove functionality). In fact, as gtoledo hinted, we've actually added more to it in 1.1. The immutable properties will also probably be growing as well -- we're adding a fullscreen property because it's been an endless source of problems, for example.
here's a zip of an example .qtz for quartz builder which was is going onto my website where you can find some other QB examples..