<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>John Finkell's Activities</title><link>https://communities.bentley.com/members/63b54a93_2d00_6114_2d00_4d5c_2d00_ad10_2d00_5697fc4153ba</link><description>John Finkell's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Capture and use current filename being processed via Batch Utility</title><link>https://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/129294/capture-and-use-current-filename-being-processed-via-batch-utility</link><pubDate>Tue, 06 Dec 2016 19:54:58 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:124d0eeb-4249-4de1-859f-ddd5e75e275b</guid><dc:creator>John Finkell</dc:creator><description>&lt;p&gt;I am trying to batch publish iModels from within PW. I have the script working fine, it is is just that the command &amp;quot;publishdgn package&amp;quot; requires I provide a filename with &amp;quot;.i.dgn&amp;quot; to generate the Packaged iModel. Is there some way to capture the name of the current file being processed by the batch utility and somehow use this within the command script, ideally, using the filename only without the extension. I tried using $(_DGNFILE).i.dgn, however, it just complained it could not create the file, &amp;quot;Error creating file: [c:\pw_workdir\...\dms01040\$(_DGNFILE).i.dgn]&amp;quot; most likely due to the &amp;quot;$&amp;quot; and paraenthesis. Obviously, it is literally using $(_DGNFILE) rather than expanding out the variable value. I get this same behavior whether I am within PW or not. Any suggestions/samples would be greatly appreciated. Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Apply a Clip Volume by Element Key-in</title><link>https://communities.bentley.com/products/microstation/f/microstation-forum/119683/apply-a-clip-volume-by-element-key-in</link><pubDate>Thu, 26 May 2016 15:02:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c0c16c6a-e041-4255-9283-eec59958fe98</guid><dc:creator>John Finkell</dc:creator><description>&lt;p&gt;Is there a key-in for Apply a Clip Volume by Element? I am writing a simple MicroStation script to place a Solid and I then want to apply a clip volume based on that solid. Is this possible do do with key-ins?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>[CONNECT] Installer doesn&amp;#39;t work via Remote Desktop</title><link>https://communities.bentley.com/products/microstation/f/microstation-forum/110574/connect-installer-doesn-t-work-via-remote-desktop</link><pubDate>Thu, 03 Sep 2015 20:34:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d8457de2-d05e-4d21-a545-198cdea22441</guid><dc:creator>John Finkell</dc:creator><description>&lt;p&gt;Although I like the dynamic nature of the new installer, I have noticed I am unable to install via Remote Desktop to a computer. Was this taken into consideration when going with this new interface? Are there any settings anyone could recommend, that could help with this. Not a super huge deal, however, it would be convenient to be able to use Remote Desktop for installs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>