NISUS Archives

July 2012

NISUS@LISTSERV.DARTMOUTH.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Is this a bug in the macro language?
From:
Þorvarður Davíðsson <[log in to unmask]>
Reply To:
[log in to unmask]
Date:
Tue, 24 Jul 2012 18:46:19 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines) 
On 24.07.2012, at 16:28, Philip Spaelti wrote:

> 
> 
> I think Martin once explained something about this version number. It is maybe the version as calculated from NW Express.

The current version of NW Express is 3.4.1, I think. If it refers to NW Express they should then mention that in the NWP manual.

> The main purpose of this command is for macros that you want to exchange, and where your macro uses commands that were introduced later.

Therefore it’s important that the command returns correct value. -- Did Martin explain this in the Forum?


Žorvaršur


--------------
> 
> On 24. Jul 2012, at 23:22 , Žorvaršur Davķšsson wrote:
> 
>> On page 406 in the Nisus Writer Pro Manual there are two macro commands given to obtain the version number of the currently running Nisus Writer Pro application (see under "Current Nisus Writer application values", p. 406.)
>> 
>> If I select this:
>> 
>> $version_number = Application Property "version"
>> Prompt $version_number
>> 
>> and run the selection as macro, I get the result "4.0.2". 
>> 
>> Is this a bug?
>> 
>> 
>> P.S.
>> This, on the other hand, returns "2.0.2", as one would expect.
>> 
>> $detailed_version_number = Application Property "long version"
>> Prompt $detailed_version_number
>>

ATOM RSS1 RSS2