Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
So actually i test the container with columns function. Works pretty well. The only thing i miss (or I don't know where to find) is following: When inserting a CwC, I'll be asked for the Number of Cols (@Niko: Schreibfehler bei "Anzahl") and the minWidth, default by 150. After viewing my result, I dismissed the minWidth part, and want to change it from 150 to maybe 400. Where can I do this? Michael |
||||
|
Yes, there is currently no simple way to change that other than editing the values in the breakpoint editor for each column. It's sometimes easier to just delete the containers and re-create them. |
||||
|
yes, it's not that much more mouseclicks to handle :) got an email from my boss, he bought a RC licence yesterday. not for need, just for support your company. 
|
||||
|
Heh, thanks, that's really nice! |
||||
|
you're welcome. so actually i try to find out how to solve the following three container scenario: desktop: (picture) (text) (text) (picture) (picture) (text) mobile: (picture) (text) (text) (picture) ---> (picture) (text) (picture) (text) the second container should change the columns when width < X. so it should look like (picture) (text) (picture) (text) (picture) (text) any suggestions? |
||||
|
Hm, you could probably do that by adding some other hidden container and hide/show it on demand. |
||||
|
Hi Nico, was my first thought, too. Ended up with a blank page on first try.  But ii'm onto it. Michael |
||||
|
Niko, I tried. But I don't get a real solution. The seperate container with the picture always stays visible. I can't find something like a breakpoint : "if view larger than" -> picture not visible My Idea on the 2 containers is: 1 text | 2 and on breakpoint f.e. 600 px 1 just visible when smaller, hide when larger 2 just visible when larger, hide when smaller The other problem is following: when picture 2 is not visible, the column height rests empty what results in space. do i have to set the container min height to none? Michael |
||||
|
Hi, Michael, "when the view is larger" does not exist. I have done a simple test (cocobello.net), if you mean something like that. Picture 1 normally placed, Breakpoints: if smaller than 875 px , visible (remove marker - = invisible) Picture 2 freely placed, Breakpoints: if less than 3000 px, visible (remove marker = invisible) further breakpoint (+): if smaller than 875 px, visible (marker set) |
||||
|
Bupp, this is exactly what i wanted I never would have thought the other way to set both visible/invisible when smaller than... but this makes so much sense. I was thinking of a solution like: user klicks on a menu: when size > X then open menu_large.html when size < X then open menu_small.html so i got another page for viewing on mobile phones. i now just have to find out how to get the white space away when the picture is disabled in the container. |
||||
|
try to set the container length to 'auto' |
||||
|
got it. not by auto, but instead of making the picture invisible i made the container around itself invisible. so actually i just got irregular spaces between the containers, but i can live with that. |
||||
|
Hi, I am trying similar where I have a background image (covering the whole page) but I want to introduce (make visible) another image in a container (embedded within this larger container) when pixels are say 400. I don't mind the larger image staying displayed at this lower width. I just want the other image in front of it to become visible at px lower than 400. I'm guessing this isn't possible just using the 'visible' or not 'visible' settings given you have to place the smaller image in the container in the first place and by default it is already showing 'visible'. Thanks |
||||
|
".... (embedded within this larger container)" that's the problem. consider: if you make the large container invisible, then everything in the container logically becomes invisible as well. However, if you insert two containers normally and make the top one invisible via breakpoints, the second container automatically moves to the top. Maybe a consideration |
||||
|
|
){kind=link}