Author Topic: Issue (or maybe not) with <IP>2</IP>  (Read 1257 times)

kourou

  • Jr. Member
  • **
  • Posts: 81
  • Anything that can go wrong will go wrong
    • FANNY (Discord)
Issue (or maybe not) with <IP>2</IP>
« on: November 23, 2018, 11:51:13 AM »
I don't know if this is an issue or if it's by purpose, but anyway:
the flag <IP> works fine when we try to import commands from a .vap
but it does not work with the option "Copy To" when we import that same .vap and write click the cmd.


EDIT by Pfeil: Checked in v1.7.3.9; Individual commands can still be copied to another profile(either using "Copy To..." or "Copy" from the command list context menu).
« Last Edit: March 18, 2019, 11:04:46 PM by Pfeil »

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2832
Re: Issue (or maybe not) with <IP>2</IP>
« Reply #1 on: November 23, 2018, 12:01:58 PM »
I will take a look at it.

Edit - Yeah, there needs to be a check made at that point.  Good catch.
« Last Edit: November 23, 2018, 12:28:44 PM by Gary »

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2832
Re: Issue (or maybe not) with <IP>2</IP>
« Reply #2 on: June 11, 2019, 11:02:04 PM »
I just noticed that the paste part of this issue was not completed.  I updated the code and this will be out in the next release.

Copy to a profile that has IP set will result in a warning or stop.
Copying from one profile and pasting into a second profile where the second profile has IP set will result in a warning or a stop.
Coping from a profile and pasting into that same profile with IP set will NOT result in a warning or stop.