Is there an easy way to find things at various positions in the doc (line-start, paragraph-end, etc.), a la NW 6.5?
It took me a while, but I was able to find things matching complex criteria in 6.5. In NWE I end up frustrated more often than not when attempting to use PowerFind. It is not nearly as intuitive as it was in 6.5. Why did the positional options disappear? They apparently still exist in PowerFindPro, which is totally user-unfriendly for the non-Unix-savvy user.
TIA,
Nick D.
PowerFind by position?
Powerfind.
Dear Nick,
I think whe have the same experience. I posted some of the problems I had comparing powerfind in NWE and 6.5 on 16th january. However, nobody from Nisus reacted until now. I just received the usual 'great' e mails. So I wish you good luck.
Arnold.
I think whe have the same experience. I posted some of the problems I had comparing powerfind in NWE and 6.5 on 16th january. However, nobody from Nisus reacted until now. I just received the usual 'great' e mails. So I wish you good luck.
Arnold.
Re: Powerfind.
Hi,Arnold wrote:Dear Nick,
I think whe have the same experience. I posted some of the problems I had comparing powerfind in NWE and 6.5 on 16th january. However, nobody from Nisus reacted until now. I just received the usual 'great' e mails. So I wish you good luck.
Arnold.
I have had another experience. Charles Jolley has answered my topic " Is there a chance to get back, what we once had?" and has said, that they are planning to enhance the f/r feature.
Best, Matze
-
rmark
- Official Nisus Person
- Posts: 430
- Joined: 2003-02-11 10:49:05
- Location: Solana Beach, CA
- Contact:
Position in PowerFind
Matze, Arnold and Nick,
You can learn more about the “position” metacharacters in Nisus Writer Express 2.1.1 (called “Constraint Escapes”) in the MOKit Open Source Framework to extend Cocoa.
You can learn more about MOKit.
The documentation is available on the Web published by A Better Finder Select, or, slightly more formatted by skEdit.
At Nisus Software Inc., for Nisus Writer Express we implemented MOKit GREP, rather than "reinventing" what we had in Nisus Writer Classic because it was much faster to integrate that available code (there was already an interface for Objective-C). Even if the classic version could have been pulled out and used, it did not know how to handle Unicode. The Classic code would have had to have been rewritten completely, rather than reused. I apologize for not having these position metacharacters available in the PowerFind menus. I understand that would make learning how to use them much easier.
You’ll note also that Nisus Writer Express does not yet support attribute-sensitive find and replace. We are working on that.
You can learn more about the “position” metacharacters in Nisus Writer Express 2.1.1 (called “Constraint Escapes”) in the MOKit Open Source Framework to extend Cocoa.
You can learn more about MOKit.
The documentation is available on the Web published by A Better Finder Select, or, slightly more formatted by skEdit.
At Nisus Software Inc., for Nisus Writer Express we implemented MOKit GREP, rather than "reinventing" what we had in Nisus Writer Classic because it was much faster to integrate that available code (there was already an interface for Objective-C). Even if the classic version could have been pulled out and used, it did not know how to handle Unicode. The Classic code would have had to have been rewritten completely, rather than reused. I apologize for not having these position metacharacters available in the PowerFind menus. I understand that would make learning how to use them much easier.
You’ll note also that Nisus Writer Express does not yet support attribute-sensitive find and replace. We are working on that.
Write On!
Mark Hurvitz
VP for Communications *RETIRED*
Nisus Software Inc.
Mark Hurvitz
VP for Communications *RETIRED*
Nisus Software Inc.