Visio 2013: Create scrollbar for hidden overflow
.
I have a list of over 112 items. Which, is extensive for a simple diagram. I would like to have only 4 lines viewable and have a scroll bar to view the overflow.ties.
e.g.
I have a list of sites that are hosted on each server. To have all the sites for all servers displayed will decrease diagram readability. I need to set the max displayed lines to 4. The rest needs to be hidden. You should be able to view these by using a scroll bar.
This is a common practice in HTML. Hoping to find a way to do this with Visio 2013 also.
For example:
domain1.com
domain2.com
domain3.com
domain4.com
--Overflow--
domain5.com
domain6.com
andmanymore.com
Instead of doing the filtering in visio, provide already filtered data. ie: fill the list field already with a string, where the domains are separated by CHR(10).
This operation is easier to realise in excel/access/VBA.
I would send a draft, but I don't see a possibility to add attachments to answers.
HTH, otherwise don't hesitate to ask for details.
I guess that you have the list of domains in a user defined field.
Now add another field with the following formula mid(prop.yourlist,controls.start,prop.numberOfCharactersToDisplay)
where:
controls.start would be a control added to scroll your list and
prop.numberof.. the number of characters to display.
Insert now the new field to be displayed in your shape. Done.
These formulas will of course truncate your domains at any place in the string. If you want it to show always full lines, you should look for the line breaks (find(char(10), yourList)
HTH
Related
I have a stack of DICOM coronal images where I have used the Image Position (Patient)(0020,0032) tag to sort the images in correct order.
However, the stack also contains an "overview" image showing how the coronal slices where generated from an axial stack - see attachment.
Obviously I want to automatically skip this overview image when sorting the stack - does anyone know how to utilize DICOM tags (which?) to distinguish this one from the rest of the stack?
Sorting on Image Position (Patient)(0020,0032) seems correct.
Sorting on other tags like:
(0008,0012) Instance Creation Date and (0008,0013) Instance Creation Time
(0008,0022) Acquisition Date and (0008,0032) Acquisition Time
may not work. Technician may acquire intermediate images afterward if missing in earlier scan sequence.
(0020,0012) Acquisition Number and (0020,0013) Instance Number may not work for same reason.
So, tag you choose for sorting looks correct.
Now, images you are interested in are "AXIAL" and you want to skip "OVERVIEW" images from stacking.
Well, I am not sure if "OVERVIEW" is correct term. Do you mean Topogram/Scout/Scanogram/Localizer/Patient Protocol or something? Anyway, we will continue with your term.
Check the (0008,0008) Image Type attribute. For "AXIAL" images, it should contain value "AXIAL" generally at third position. Something like following:
ORIGINAL\PRIMARY\AXIAL
OR
DERIVED\SECONDARY\AXIAL
For "OVERVIEW" images, this either will not present or it will be different ("LOCALIZER" most probably assuming CT Image).
Please note that only first two values are mandatory. Values beyond that are optional.
Reference:
ftp://dicom.nema.org/MEDICAL/dicom/2016a/output/chtml/part03/sect_C.7.6.html#sect_C.7.6.1.1.2
https://dicom.innolitics.com/ciods/ct-image/ct-image/00080008
ftp://dicom.nema.org/MEDICAL/dicom/2016a/output/chtml/part03/sect_C.8.16.html#table_C.8-129
Another option which might be more reliable than the Image Type attribute is to check the Image Orientation Patient (0020,0037) since the localizers are usually perpendicular to the stack they are referencing.
I have successfully used kibana (4.3.1) to make a dashboard with several visualizations. Great! Now I would like to add some input controls to allow filtering. I know that you can manually enter filters in the query bar, for example 'myCol:[low TO high]' but this is problematic for a couple of reasons. First, the syntax is a little too advanced for casual users (although I could use the metadata visualization to document the syntax). Second, the query bar goes away when exporting the dashboard via iframe.
I have tried using the metric visualization to display a min and max values. Unfortunately, the metric visualization is read only.
I have tried a bar chart to allow range filtering but my users will need to select very specific ranges that result in selection areas of only a few pixels. This is error prone and not precise enough.
Any other ideas on how to create input controls for easy filtering? I was hoping find some sort of dial that is tied to a column to allow users an easy way to apply filters.
Thanks,
Nathan
Check working with filters section in the documentation. Selecting a filter changes dashboard URL and includes snippet like (filters:!((meta:(disabled:!t,index:'myIndex_*',key:MyTermToFilter,negate:!f,value:'MyValueToFilter'). Once you have all the filters you want your users to change in the URL, after they navigate to that URL they will be able to enable/disable them in the UI
For about a week, Google Analytics was erroneously reporting page views for a few request URIs, severely skewing my data. I have read that there is no way to remove data once it is reported. If this is the case, is there a way to simply hide this data from the view?
I have tried a number of things (such as creating global filters, view filters, etc.) to no avail. Using segments also doesn't work, because apparently you can only filter out visits/users (whereas my goal is to filter out page views associated with a specific page). At this point, I feel like I must be going about it the totally wrong way...
Below is a screenshot of the Behavior > Overview section. The page views I want to move are #1, #2, and #5.
Alex, unfortunately, there is nothing you can do about the historical data.
However, you can use simple filter to exclude pages you don't want to see (the filter field above the report table, not filters related to account/profiles) -- see the attached screen below.
Make sure you select exclude and then pick Page dimension. The easiest way would be to use regular expressions, like:
(a|b|c)
This one would remove any pages that contain either "a", or "b" or "c".
The expression would be probably a bit more complicated in your case and I suggest using tools like RegEx Hero (free, online). I am not sure if there is anything common for the pages you would like to remove from the reports, but regular expression can do quite a lot :).
One last thing -- be aware there is a slight difference in segments and (table) filters. If you use segments for page dimension, you would end up with ALL the pages that were seen during a visit, which includes the page you set in the segment. Might be a bit confusing, but see this article for detailed explanation.
I'm doing a permissions screen that could use a slider bar- for each section of the site, I want to be able to give users permissions easily, using a horizontal slider bar that has text values defining the different levels of permissions, meaning what they can do in each section of the site, increasing in permissions to include abilities like reading data, writing, deleting items, adding them etc. Every level includes the previous levels, so a slider bar seems the logical choice to show that's what's going on.
Unfortunately, looking around, the only slider bar with good ASP integration (this is part of an ASP web form) is the AJAX one, SliderExtender, but that only uses numbers as values. Is there a way to use text values as the labels for this control, or is there another (free) one that I can use for this purpose?
Thanks in advance for the help.
Why not just use numeric values and handle convert the numbers to text values in your code?
1 = Admin
2 = Power User
3 = User
4 = Other User
Hope this helps
We have uploaded tons of files via FTP to a Plone intranet we're deploying. This step does not set the titles of the files; so searching for a file called: "invoice_policy.odt" it won't show up in a search by "invoice policy" (two words); cause the index for id's is a field index.
Moreover, the default plone lexicon does not split words by underscores, so setting the title to be just the id won't help either.
So, in order to improve our search recall, we have scripted (taken from several sources including some answers in StackOverflow) a quite simple normalization script: https://gist.github.com/3701401
However, after applying it to near 8000 files I see that the titles have changed, but the files still appear in the navigation with the id "invoice_policy.odt"; I have to edit the file and then save it in order for it to appear with its title in the navigation.
I have uploaded three images to flickr to show the process:
Image 1. The (last) file in its folder.
Image 2. When I click the file you may see it has a title (normalized with our script)
Image 3. I just clicked the title and the click the Save and went back to its containing folder. Now it's been shown properly.
Do I need to do (or undo) something in my script for it to work properly. Furthermore, although I (think I) enclosed each rename in its own transaction, I don't see any transaction in the Undo tab of the ZMI. I guess it's because it's not associate to a real request, is that so? Can I fix it?
Best regards,
Manuel.
You need to reindex the items, either one by one in your script, or in batch at the end. http://collective-docs.readthedocs.org/en/latest/searching_and_indexing/indexing.html will probably help.