The GroupLayout control needs a RowsLayout or a ColumnsLayout as its child control. That child control can then contain anything you want, including groups of groups. I hope that helps, & I'm sorry that the documentation doesn't explain that better.
Hi Mark, thanks for asking the question! I want to know that myself, lol. I've just sent an email to the publisher, & I'll let you know what comes back as soon as I hear. Have you seen the recently updated "Luminous LightSwitch Types"? I've added a "Password" type, & a "Link" type. You may find them helpful.
The answer I got was "Yes, absolutely, as well as on the Nook, in the Apple Store for iPhone and iPad, and in ePub, MOBI, and just about every other e-format you can think of".
Just simply brilliant and useful! This shows another glimpse of what the future holds and the immense potential most of us believe LightSwitch holds. Again, without any coding :) (my favorite part) you can give your app a very personal, but professional, appealing and unique look and feel.
Helping to fulfill the LS tag line of "coding optional."
Yann, thanks again for sharing this with the community. And another thanks to the LS team for making all this possible.
I have been noticing one When using the standard lightswitch controls as groups nested one in to another, the screen becomes very slow in performance, the main part where its gets slow is when closing the screen, sometimes it might take up to a minute to close.
The interesting part here is, when placing this extension control Group box on top of the screen and then placing all lightswitch standard controls underneath, then the problem goes away immediately, nothing even in comparison. Which comes to show that this is something fixable and something lightswitch team can fix in the code.
My problem is, i do not want to use these extensions simple because when upgrading to a new version of visual studio these controls are not available.
I would really appreciate if you can help me out. I was noticing you on all lightswich blogs and I'm a big fan of lightswich same as you. Thanks in advance. I need some advice.
Many thanks for the controls! Could you explain how it may be possible to change the TextBlock 'Text' property at runtime? The control does not seem to implement the controlAvailable event and therefore I am unable to cast the proxy from 'findControl'.
Many Thanks in advance.
First of all thanks for your nice controls. I can give my screens a more personal look now with less effort!
I only have a problem when I try to change some properties of a GroupLayoutControl.
Private AGroup As Luminous.Controls.Presentation.Controls.GroupLayoutControl
AddHandler Me.FindControl("MyGroup").ControlAvailable, AddressOf MyGroup_Available
Private Sub MyGroup_Available(sender As Object, args As ControlAvailableEventArgs)
AGroup = CType(args.Control, Luminous.Controls.Presentation.Controls.GroupLayoutControl)
In some other routine:
If Not IsNothing(AGroup) Then
If Me.Application.User.HasPermission(AllAllowed) = True Then
AGroup.HorizontalAlignment = Windows.HorizontalAlignment.Left
AGroup.HorizontalAlignment = Windows.HorizontalAlignment.Stretch
Problem is that the "MyGroup_Available" is never triggered.
(I doublechecked that "MyGroup" is an existing control)
Do you have any idea what causes this problem?
Thanks in advance,
I have created a modal wizard dialog. Each wizard page contains a page RowLayout container control and under that one a pile of GroupLayout controls. The navigation buttons hide/show the different page Rowlayout controls. It works nicely the first time with proper spacing between grouplayout panels, however when showing a previously hidden page suddenly much more space is added between the GroupLayout controls and I cant seem to figure out what is causing the problem, do you have any idea of what could cause this effect?
I have now found out that the problem is the TextBlock(Title)object which is included in the GroupLayout control. In my case I dont use the title so I left it empty and initialy when the modal dialog is created the title height is 0 and everything is fine. However after the parent RowLayout container has been toogled between visible/not-visible/visible suddenly all TextBlock(Title)objects gets a height of 14.631 showing nothing. How can I avoid this? I have tried to get access to the GroupLayout control from code for manipulation but the ControlAvailable is not fired on such objects for some reason. My approach was to set the Visibility property to Collapsed for the Title object or something.
All ideas are appreciated?
Have you found a solution to the log off issue? I've checked all of the forums/blogs where I've found Luminous Controls listed but haven't seen anything.
Server Error in '/' Application.
The resource cannot be found.
Requested URL: /Luminous.Commands.Server;component/LogOff.aspx
I came across your controls, and they looked like just what I needed.
I installed them, but after adding the group control to my screen I can see no possibility to add an item to it. I cannot drag and drop an item there (like an existing rows layout, or a data item), and there is no + Add link like for other layout controls.
What am I missing here?
The current version only allows a single control. So it requires a "container" control to be added to it (like a RowsLayout, or a ColumnsLayout) if you want to add multiple controls instead of just one.
I actually would have thought that you'd be able to drag an extisting RowsLayout, but I have to admit that I haven't tried that.
I'm working on a newer version that hopefully should remove that requirement, but it's not ready to be released yet.
I know that the documentation for the exisiting controls isn't that great (I was busy working on a LightSwitch book), so I'll try to give better instructions with the next version. Please do let me know if you still can't figure out how to use the controls from this explanation.
Thanks for your reply!
How do I add a rowslayout then?
After having added the group layout control I have not any possibility to add anything:
no drag and drop, no add link, and when I right click the control I have the
following menu items: add button, cut, paste and delete.
If I click the Add layout item link while having the group control selected I have the items button, group control (disabled) , custom control (disabled)
If I change the data for the new custom control to something other than "Screen" (I know this does not really make sense,but i tried this anyway) I have the group control item in the right-click menu, but disabled.
I can add a button, but thats not what the control is for....
Is there another way to add controls??
I could use the textbox control right away, only I have not yet found out how to change the width (I've got a longer text to display). But this might have something to do with the position of the field in the general layout. Or is there an inherent limitation on the width?
I have found out somehting else: I tried to use the pixata custom controls, and I cannot use them really either, because the additional properties which should be in the Appearance section e.g. for the StylableStaticLabel are not there. So it looks as if something basic is missing in my Lightswitch installation which probably is the cause of my problem with your controls, too.
What I have installed: no full visual studio, only lightswitch itself, version is:
Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel
Installed Version: LS Standard
And I am using a VB Project. Is there something else I need to have installed or activated?
I figured it out: when adding the group layout control I did use Add layout Item, then custom control and then chose your control from the custom controls tree... This does not work (and does not for the pixata controls, either). But when I did choose Add layout item, then Group, and then changed the type to "Group Layout" ( = your control) , then it does work. So I took just the wrong way to add your control.
Now I can do some nice groupings on my screen, thanks!
Sorry I didn't get to answer before you had to go through all that, but in all honesty I don't think I would have been able to come up with your solution, I would never have imagined that somebody would have tried to add my control as a "custom control", lol, so I wouldn't have known why the "add" options weren't there. But that's my fault for not having better documentation. I'm so glad you found the answer yourself! I'll make sure that I point out in the documentation for the next version not to add it as a custom control.
I hope you like what you can do with the two controls. Please don't hesitate to ask any questions, or suggest any improvements.
I have not yet that much experience with Lightswitch, so I thought, well they're custom controls, so I have to add them like that. I only realized that that was wrong when the pixata controls showed up with their name (pixata xxx) in the drop downlist together with the standard Lightswitch controls and then I realized that yours where there, too.
But your controls and the pixata ones make layout so much easier.....
Yes, I originally named those controls, so that they would "fit in" seamlessly with the existing controls, but new releases will all have a "Luminous" prefix, for exactly that reason, so that people know that they're NOT built-in controls. Oh well, you can't get it right all the time, lol.
Good luck with your LightSwitch apps, & I hope you enjoy your experience. LightSwitch is an amazing product!
These controls are really awesome. I just started using them, but they're very mature and blend in well with the default controls. Well done!
I'm wondering if you'd consider sharing the source code of your extensions or sources of information to learn more about creating more advanced controls. I'm trying to understand LSML in order to create highly configurable controls and I guess your controls would show me in the right direction.
I'm defintely looking into ordering your book :)
Hi Sander, Thanks for the compliment, I really appreciate hearing this like this! Sorry it's taken me a while to get back to you (I normally answer these questions straight away, but somehow this one slipped through the cracks). The book will hopefully explain what you need to know to be able to create extensions like mine, but I don't have any plans to release the actual source code. I would have thought that making the controls available for free would have been enough, lol.
I stombled over your Extension for LS and thought - thats, what I need for displaying an static text field. So, I installed the extension an mark it as active in the Project Properties. After confirmation of the upcoming Dialog "Microsoft VS/LS should restart to use the new extension" (or so similar), I got the following error message box (I try to translate it from german to english):
"Adding the Reference for these extension is not possible because:
The Extension <<Luminous.Controls>> could'nt load. The model fragment for the extension <<Luminous.Controls>> could'nt load. The fragment has an error in row 0, column 0. The unknown member <<Microsoft.Lightswitch.Model.Storage.Control.IsViewer>> can not be determined.
The reference fo this extension was removed. ... Restart MS VS to apply the changes."
I'm still using the Beta 2 of Lightswitch.
Any suggestions about the reason for this error?
Thanks in progress.
Hi Thommi, I believe that this is a problem with all extensions working with Beta 2, not just mine. There's not really anything I can do about that though I'm sorry. B2 is due to expire on October 11th, so it's probably a good idea to download & install the RTM version as soon as possible anyway. You can get a 90-day trial (30 days initially, plus a 60-day extension for registering).
At the moment, the background is themed to be the same as a non-active screen tab (which is a 2-color gradient). While this doesn't *have* to be the choice, I felt that it was best to use something that was likely to be harmonious with the page it was being displayed on.
OK, that's a good logic. The only problem with this is that the group can be quite a bit bigger than the tab, and the gradient looks a bit out of place at that size.
Not a huge issue, but would definitely be an improvement if we could (at least) remove the gradient, or (even better) set it to something of our own choice.