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.
I have tried to add the &z=15 and %zoom=15 to try to edit the default zoom in the embed code but it seems to not change anything. Also, I have changed up the width and height of the embed code but that didn't change the zoom just the overall dimensions. I am trying to embed a flowchart into my company's intranet SharePoint but the zoom is always set to 19% or 24% by default which makes it impossible to see anything in the diagram by default. I want it to start zoomed in at like 100% so the website/diagram is easier to use.
I have also tried to print it in a pdf, converting it to pdf, and converting it to other formats for the file viewer to give different views but it came to no avail. The closest thing was when I changed it to pdf and it gave me a better view, but I lost the interactive embed that a normal Visio embed would give.
Thank you for your help!
Puzzled with a similar problem, I've built a special Web Part for that (it provides additional options for embedding that are not part of the stock web part, such as zoom).
The source code:
https://github.com/nbelyh/VisioOnlineSpfxWebPart
Here web part in MS Store: https://appsource.microsoft.com/en-us/product/office/wa200002491
Does anyone know if you can change the color of the text for specific items in a dropdown list in Adobe's extendscript ScriptUI? I know about the color section of the Script UI guide, however that says nothing about list items and I tried a few things by chance but wasn't able to find a solution.
The ScriptUI is converted to HTML5/CSS behind the scenes. Because the CSS is not exposed to the user, it is not possible to change any of the colour schemes.
You can use images for buttons to add colour to them, but that wouldn't apply to dropdowns.
I'm not certain about the other Adobe programs, but I know that creating an extension (as opposed to a script) for After Effects is a way of circumventing this restriction.
In the rich text field I choose Full alignment, but when previewed the text has left alignment. When I close and reopen the document, the text is brought back to left alignment.
How can this be resolved?
If I understand you correctly, you have a Notes Form with a Rich Text field, in which you align the text "justified", as in the screenshot below:
But if you view that in a Xpage, the text is no longer justified, neither in the read-only rendering, nor in the edit-rendering with the CKEditor:
Alas, if you align the text justified via the CKEditor, it renders properly in the browser
with an "interesting" rendering in the Notes Client:
This is a "known" problem and in my demo case, the Xpages runtime engine even warns me about that:
"Saving this document will change its format from native Notes rich text to HTML. This may cause a change or loss of formatting if opened again in the regular Notes client."
The conversion of rich text to HTML and vice versa is not the whole problem, even though the message says that. There are also issues with repeated conversions back and forth changeing font sizes, loss of certain colors and styles, etc.
This is a long standing issue with Ben Langhinrichs, who documents that rather thoroughly and even sells an extension to handle that conversions better.
Hope this helps a little bit.
I am using v8.5.3 and in the All Properties of the CKeditor they have a property called 'htmlConversion Warning' that you can set to 'noWarning' which seems to prevent the Saving this document message mentioned above. Seems someone from IBM has taken a note from Microsoft on providing a solution. Now if only they would take a note from them on how to market the product.
I need to design a web form which landlords can use to add rental listings. There are 8 mandatory text boxes and 2 optional text boxes, 11 drop-down lists, 12 checkboxes and one large text area. Any suggestions about how to arrange them in a way that is clean, and uncluttered? My concern is, if the form looks lengthy, they may not want to fill it. So far I have divided the elements on the page into sections, however the page still looks cluttered.
I would suggest that you use 2 pages instead of 1. On the first page, show the 8 mandatory text boxes and follow them with an additional checkbox which makes the 2 optional text boxes appear on being clicked. This means that the user will opt-in for the optional checkboxes making it more acceptable and natural to her. Next, place a submit button which would take the user to the second page.
Put all the 12 checkoxes and the text area on the second page. On page 2, tell the users very clearly that this is the last page they need to fill. They will be less disinclined now since all they need to do is to place a few more clicks.
You may want to split the process of getting all of this data from the user into multiple parts. Conventionally, that would be multiple pages of forms. The problem with that is that it's annoying for the user to have to watch their browser reload the whole page as they move through the form.
A more popular methodology now is to use AJAX to present the larger form in multiple pieces without having to reload the entire page.
In both cases you will need to keep state between each page load or AJAX request so that the back button behaves sanely and the user's previous input reappears as they move backwards (and forwards) through the form.
Unless you have some kind of nifty state-keeping mechanism already written that is generic enough to work for any given form set you may decide to use, welcome to the pain in the ass that is web development.
How about a wizard-style layout?
Break the sections out into separate pages, so components are submitted separately. Make it clear how many sections there are, and how far through the form the user is. Be careful to track the user's progress either in the session, or by keeping state in the form.
This approach makes giving error messages a bit less threatening to users (you never show them the error message "Please correct the following 34 errors").
Edit: Having seen the current form layout, I actually think what you've got at present is very clear, and nicely done.
Do submitters have account profiles that you can use to populate the contact details? If so, I would drop the contact details from the form for creating a listing, and add a review screen that shows all of the information, and gives links for specifying alternative contact details or amending other information. Users then see one screen, plus a review screen with a big "Publish This Listing" button. Amazon's order process uses a good review screen.
Breaking the input into multiple sections is a good idea.
I also like to make most of the input fields invisible, and make them visible as more information is entered. I start with the most important info to be entered first (e.g., name), and as each item is entered, I make further input fields visible. I also give focus to the next logical field that the user is expected to enter as he goes along.
You can use other tricks like highlighting the next field to enter (i.e., changing the background color or surrounding borders of the input field label) to make it even more obvious to the user.
Grouping related fields into separate boxes (with visible borders) may make the info seem less cluttered, too.
This approach makes it look less overwhelming to the user, and makes it more obvious to him what he needs to enter, from start to finish.
Frankly, 33 fields on a single page does not sound all that long for describing a rental listing, especially when 23 of the fields (checkboxes and dropdowns) can default to the most common values. With your current layout, the form almost all fits above the fold. That ain’t bad.
I’d be very cautious about splitting it into separate pages (e.g., as a wizard). First of all, that will take the user longer, because now you’re adding navigation and re-orientation time. Second of all, it will seem to take longer; the user will be like, “Geez, I have fill out a multi-page form?” Thirdly, users can’t tell how much work is expected of them when some of it is hidden on other pages (or by AJAX tricks). Some will not fill out the form at all assuming the worse. Others will abandon it part-way through because they either didn’t plan enough time for it, or just got tired of hitting Next indefinitely. You can mitigate this last problem by saying up front how many pages there are, and showing the user’s progress through them, but that just accentuates the fact that it’s multi-page, and therefore “long.”
IMO, all it needs is some lighter graphic design. I’d drop the “reverse video” section titles and the green background on alternating sections and make it all white. Use color and/or bold text for the section titles. You can combine the Property Description section label with the field label to reduce clutter and redundancy. Consider putting the Pets and Parking fields on the same line as Laundry then spreading the Unit Details fields out vertically so the mis-alignment of the fields is not so noticeable. Alternatively, size the Unit Detail fields so that they are better aligned. Maybe you can drop the “How do you want to be contacted?” field. I’d expect that if users don’t want to be contacted by one of the means, they simply don’t fill out that field.
Other than that, be sure your users understand the importance of these fields –why filling them out helps them find the right renters. Users don’t mind filling out a lot of fields if it’s clear that each benefits them. It’s when users feel like they're disclosing a lot of data to benefit you that they get resentful and reluctant. The importance of the fields you have seems self-evident to me, but maybe you should include a link that explains the purpose and value of the fields.
Finally, make sure there’s not too much clutter and competition from the “standard” page elements (e.g., sidebar menus, legal information).