This long-time DW user is having some basic usability issues with DW 18. Wondering if anyone might be available for some paid time with me via TeamViewer, to help sort out my issues. I'm not anticipating a long, drawn-out session; the basics are just not falling into place as in the past. DW-CC 18.0 running on Mac OS10.13.3. Tks, jwc ... View more

In my inDesign text table I have successfully hidden the table borders. Now I also would like to hide the cell (i.e., column and row) borders. If one of you could point me to the correct workflow, I would be grateful. Best, jwc ... View more

Please forgive  me if this duplicates (a portion of) an earlier post. I would like to start a dialog with a knowledgeable Adobe (Bridge) rep. regarding the existing search options within Bridge, which at present, do not include all of the fields for which I need to search. I would and I believe that other users would greatly benefit if Adobe could expand the searchspace to include all of the existing ‘IPTC Core’ metadata categories There are also sections called‘Audio’, ’Video’. and 'DICOM'. My particular interest lies in Orchids. There are thousands of orchid lovers, -growers and -photographers worldwide. Orchids are found growing wild on all of the world’s continents except Antarctic. Many are cultivated in greenhouses or outdoors in benign climates. To-date, I have photographed nearly 1,000 orchids in 4 countries on 2 continents, and am in the process of publishing them on the Web and as hardcopy books. I can see that it would become burdensome for Adobe to accommodate orchids (as an example) and all of the other, potential classes of items for which users might would like to create collections and search images. However, I am wondering if this situation might be simplified by allowing users to define their own property sets. For example, at minimum, orchids would require the following hierarchical branches: subfamily, tribe, subtribe, genus, species or hybrid (and, for a hybrid) the clone name and/or the parentage. You can see that this becomes somewhat complicated. Finally, in the case of orchids (and, I am sure, many other object classes), it would be very desirable to allow users to (a [as mentioned above]) define their own , unique or 'custom' sets of metadata entries, in quantity up to, say, 20, and (b) to develop more sophisticated queries like (A=a) and ([B=b] or [{C=c} and {D=d}]), etc., which would be an important step beyond today's limited set of all ‘and (i.e., ’if ALL are true’) or all ‘or' (i.e., if ANY  are true). Perhaps much of this would easily be capable of implementation, since so much of the logical structure of your search engines already is in place. ... View more