My Revit file has some topography overrides. There are overrides for the topography type as well.
Now, when I change the material in the topography it does not update in the 3D view.
Is there anything wrong with the override settings? When I completely turn off the overrides for topography it hides the topography completely which I don't want. Please suggest what override should be used.
Is there another possible reason why the topography material is not updating even after selecting and picking material from the materials section as seen in the figure - topography materials.
Would appreciate any response. Thanks!
Related
I am not sure if Revit is part of the Stackoverflow community but it seems that the Tag already existed so I decided to give it a try.
I have created a section of my 3D model. In order to export it as a PDF, I have created a new sheet and I have dragged a 2D of a section onto the sheet.
On top of the 2D section I needed to add some elements as filled areas with different hatches. When I check the areas on Revit, they are shown with a non transparent background (the section's lines of a 2D drawing are not visible behind), nevertheless when exporting it to a PDF the areas are transparent and I can see the section lines through them.
When checking the settings configurations for transparency filled areas the value is set to 0. Therefore, I would have expected not to have any difference between the Revit view and the PDF version (meaning non transparent background)
Am I missing something?
The StackOverflow tag is actually revit-api, standing for the Revit API, the built-in .NET programming interface. The API wraps the UI for automation purposes. Do you know how to achieve what you need manually through the end user interface? If so, that knowledge will be very helpful to determine how to achieve the same programmatically. If not, it can probably not be achieved programmatically either. The best place to raise a question to determine how to achieve the desired result manually in the user interface is the generic Revit Architecture discussion forum.
There are two problems that I have using the EnhancedDateRangePicker in Vaadin 14(source: https://vaadin.com/directory/component/date-range-picker):
The design is broken when I add the component somewhere in a layout but that happens only when I add a label. If I don't the design is as expected to be. Here is a screenshot to see what exactly happens -
The other problem is that the dash is not visible clearly in this color(light gray I think). Is there a way to change the color of the dash?
Could you please tell me is there any way to make the design as I mentioned in the above two points?
Thanks in advance :).
The problem is solved. It's not the problem with the component, it is actually the Theme which we are using in our projects and the component just overrides the theme styles and that brokes the component. When I put it in a blank page there is no problem. Thanks you all very much for the effort :).
I’m configuring the layout for the UIView in the photo (photo in the link because I don’t have the points to upload it) and I’m having trouble configuring the constraints of the marked elements, which are the constraints for the two lines of buttons, the label that is between them and the label that is on the middle of the large image. The other elements are working correctly. I’ve tried different things but still don’t get it right. I’ll appreciate if you could help me with which are the correct constraints I have to add.
https://www.dropbox.com/s/6v1fsik9duvn0d7/Photo%20Apr%2023%2C%208%2042%2021%20AM.jpg?dl=0
Thanks
Added the buttons inside a view and add the constraints to the view and the buttons. It is working correctly now
I tried to use UMLDesigner to draw my project related diagrams. I see there is a Arrange functionality that can automatically layout diagram elements and links to save some manual work. But when i used it in my Activity diagrams it designed it upside down.
Here is an example. I created following simple activity diagram.
And here is how auto layout result for the same model looks like: auto layout.
The initial node is at the bottom and the final nodes are on top. But i want it the other way - to start at the top and end at the bottom. Is there a way to configure this?
I tried pinning starting and final nodes but it just made a mess after arranging the rest automatically. I searched the settings but couldn't find anything. I use UML Designer Version 7.1.0.
Thanks ahead for any help.
I am sorry there is no way from the preferences to change this behaviour.
This is because I never provide a specific layout for this diagram. Please, fill an issue in the bug tracker and it will be fixed for the next version of UML Designer as it is really easy to fix: https://github.com/ObeoNetwork/UML-Designer/issues.
Thanks for your feedback!
I found a library, this library supports vertical scrolling cards, I want to change this library according to my needs (Horizontal scrolling).
Can anyone suggest how to implement Cards just like the mentioned library cards horizontally.
Guys I just found a library, which helped me to solve this issue.
Carousel Library
Best Library I found which I customized for my project:
https://github.com/applm/CarouselWidget
Other helpful libraries:
https://github.com/davidschreiber/FancyCoverFlow
https://android-arsenal.com/details/1/3289
I hope, this answer may help you in finding solution.
As I always suggest to ask an author and this time I'm the author of this library, I'll tell you what to do.
RecentsList is very simple and the only place you have to change is here: https://github.com/ZieIony/MaterialRecents/blob/master/app/src/main/java/tk/zielony/materialrecents/RecentsList.java#L127 . This method layouts cards inside container. You have to write your own layouting logic.
Why I don't implement that change? Because I'm not sure what do you mean by horizontal cards. Lollipop in landscape orientation shows vertical cards (at least the one I have on my desk).
The second reason is that I think I should rewrite this library from scratch. It was just an experiment with custom layouting code. Correct implementation would use view reusing and recycling just like RecyclerView and ListView do.