Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20
  1. #11
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    > I do expect us to add some sort of ad-hoc unimportance parsing

    Good to hear, thanks.

    > it won't be "Replace 'xxx' with ''".

    I think this Replace anomaly needs addressing. There's nothing to justify it.

    > he current behavior is powerful

    Agreed, and I have no doubt it is extremely appreciated by those who need it. I wish you luck in reconciling the needs of both ends of the spectrum!

  2. #12
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,787

    Default

    Hello Chirs,

    How does it interfere with your other sessions? If you define the grammar definition, its importance is controlled per session. By default you can consider it Important, but for that specific session consider it Unimportant. Or vice versa.

    Specific examples would help as test cases as we investigate changing this feature.
    Aaron P Scooter Software

  3. #13
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    > How does it interfere with your other sessions?

    It changes comparison results in saved sessions using the saem file format.

    > If you define the grammar definition, its importance is controlled per session. By default you can consider it Important

    By default BC /does/ consider it important. Hence the interference.

    Or so I beleived, from the confusing results I experienced and the explanations of the cause given on this forum.

    But do please tell me if I am wrong.

  4. #14
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    > Specific examples would help as test cases as we investigate changing this feature.

    Here is one: http://img189.imageshack.us/img189/3113/picwi.png

    Right == left except right's 30s\Loud\ is changed to null on left.

    I would like the session Replacement Item to replace 30s\Loud\ with null. This case is lucky - I can workaround using \30s\Loud\ -> \.

    BTW, nowhere AFAICT on the UI does Replacement Item indicate that it makes the target text unimportant (very nice that it does, BTW) rather than truly replaced. I think it should indicate.
    Last edited by chrisjj; 14-Jun-2010 at 11:21 AM.

  5. #15
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,787

    Default

    Hello Chris,

    For that example, first define a grammar element that matches "\30s\Loud\" and give it a unique name, like "30Loud directory" or "directory section".

    Then, in the Home screen, go to Edit session defaults, select Text Compare, and uncheck "30Loud directory" in the Importance tab. This will mark it as unimportant for all future Text Compare sessions. If you have an already saved Text Compare session, or a Folder Compare that has specific child comparison settings set, then you may need to change it there as well. If you run into a problem with a specific session, please email us your Support package (Help menu -> Support; Export) and a pair of example files. Please include a link to this forum post as well.
    Aaron P Scooter Software

  6. #16
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    Quote Originally Posted by Aaron View Post
    If you have an already saved Text Compare session, or a Folder Compare that has specific child comparison settings set, then you may need to change it there as well.
    Thanks Aaron, but I have far too many saved sessions to manually search, and far too many projects using them that cannot tolerate interference by such an abuse of the File Format grammar to handle what is just a comparison setting requirement for the current session.

    Obviously Replacement Item is the appropriate solution for this requirement. Please pass on my wish that the null text case be fixed. Thanks.

  7. #17
    Join Date
    Oct 2007
    Location
    Madison, WI
    Posts
    11,787

    Default

    But Text Replacements are saved and stored the same way. You would still need to either save an existing session or set it as a default for future sessions.

    Update: I've added a wishlist entry to handle propagation of settings to already saved sessions.
    Last edited by Aaron; 17-Jun-2010 at 12:04 PM. Reason: updated
    Aaron P Scooter Software

  8. #18
    Join Date
    Oct 2007
    Location
    Pennsylvania
    Posts
    1,772

    Default

    Quote Originally Posted by chrisjj View Post
    Please pass on my wish that the null text case be fixed.
    Chris, there is nothing to fix because replacements are working as designed. You certainly can suggest a new enhancement... but, if I am not mistaken, supporting null replacements would not be a trivial change and would require a redesign of the replacements algorithm as a whole. Whether you want to use a grammar rule or not...it is possible to do what you want with a grammar rule. Enhancement requests for functionality that can already be done using another work-around method are not likely to get very high on the priority list.
    BC v4.0.7 build 19761
    ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

  9. #19
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    > Chris, there is nothing to fix because replacements are working as designed.

    Design can be fixed too, y'now.

  10. #20
    Join Date
    Apr 2008
    Posts
    2,158

    Default

    > But Text Replacements are saved and stored the same way.

    I really hope that text replacements are not stored the same way since they too would then cause intereference to other sessions. And the ywould not be Session Sessings as the BC UI claims them to be.

    Certainly text replacements, unlike grammar elements, are not seen by me on the File Format dialogs.

    > Update: I've added a wishlist entry to handle propagation of settings to already saved sessions.

    What I need at least innthe case of using a grammar element for workaround is NON-propagation to existing sessions.

    I would also feel unconfortable with a scope that was specifically "already saved sessions" e.g. those changes would get lost upon the subsequent save of an an open modified session.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •