Quick Drop Keyboard Shortcut – Arrange VI Window

[Kosta]

---

@felipefoz wrote:

Is there a way to know if something has really changed (programatically) and maybe discard the * ? 

---

I have some ideas, but no convenient answers. I haven't tested any of those.

1. Consider saving the VI before running this QD, and comparing the VI before and after QD, using this post as a starting point. If VIs are different, delete the original. If VIs are the same, delete modified VI.
2. Rearchitect the QD VI by splitting analysis and coordinate computation from scripting that moves objects around and resizes windows. Only move objects and resize windows if there are any differences between original and computed coordinates or window sizes.

I would expect the first approach to be much easier to implement, if you can fit the change with your tooling; the second approach would be cool.

[felipefoz]

---

@Kosta  escreveu:

---

1. Consider saving the VI before running this QD, and comparing the VI before and after QD, using this post as a starting point. If VIs are different, delete the original. If VIs are the same, delete modified VI.

---

Great idea, that would also probably work, I might try this approach first. It should be pretty quick and I might reuse that for other comparisons too.

2. Rearchitect the QD VI by splitting analysis and coordinate computation from scripting that moves objects around and resizes windows. Only move objects and resize windows if there are any differences between original and computed coordinates or window sizes.

---

That would be a perfect solution, but that is going to take much more effort, right now I am thinking of not modifying the shipped plugin.

We should consider an update of this QD in the long run. 

Thanks.

[felipefoz]

I just create a VI to collect some VI Properties used in this QD plugin. There must be a better way or I am missing some property. At least I learned a bit about the QD plugin. 😃

  And the function which calls this VI is this one.

 

Apparently is solving my problem, but it might have some gotchas there that I am not aware of.

Thanks for the help so far.

[FireFist-Redhawk]

---

@Kosta wrote:

---

@felipefoz wrote:

Is there a way to know if something has really changed (programatically) and maybe discard the * ? 

---

I have some ideas, but no convenient answers. I haven't tested any of those.

1. Consider saving the VI before running this QD, and comparing the VI before and after QD, using this post as a starting point. If VIs are different, delete the original. If VIs are the same, delete modified VI.
2. Rearchitect the QD VI by splitting analysis and coordinate computation from scripting that moves objects around and resizes windows. Only move objects and resize windows if there are any differences between original and computed coordinates or window sizes.

I would expect the first approach to be much easier to implement, if you can fit the change with your tooling; the second approach would be cool.

---

I feel like something much easier than (2) but along the same lines would be to make a VI that gets an ordered list of all pertinent object coords/window sizes, wire it so it runs right before any scripting happens and right after, and compare. Fail the transaction if equal, end undo if not equal.

Thanks for the plugin by the way, it's awesome 😊

[FireFist-Redhawk]

Hey all,

Using felipe's "Get VI Properties_LV2015.vi", I made an update to the QD plugin to fail the transaction if the QD is used on a VI and nothing changes. Tested on some basic VIs and saved in 2017. Cheers once again, this plugin has helped me so much with big cleanup jobs.