Page 30 of 41

Re: Scripting Bugs

Posted: 21 Mar 2015 06:53
by bdeshi
admin wrote:OK, it depended on Configuration | Find Files & Branch View | Visual Filters | Show filter information in tab headers.

Next version will always work.
Great! thanks.

[split]

Re: Scripting Bugs

Posted: 07 Apr 2015 15:23
by TheQwerty
Ternary seems to be doing its own illogical thing.

Code: Select all

"Empty A - Expect trues" Global $a = ''; Sub '_test';
"False A - Expect falses" Global $a = false; Sub '_test';
"True A - Expect trues" Global $a = true; Sub '_test';

"_test"
  Global $a;
  $b = ($a == '' || $a == true);
  $c = ($a == '' || $a == true) ? true : false;echo "A: '$a'<crlf>B: $b<crlf>C: $c<crlf>B==C: " . ($b == $c);
:veryconfused:

Re: Scripting Bugs

Posted: 07 Apr 2015 16:25
by admin
Bugs (yep, 2 independent bugs here) confirmed and fixed.

Re: Scripting Bugs

Posted: 07 Apr 2015 19:38
by TheQwerty
Ternary fix confirmed in v15.00.0301.
Thanks!

Re: Scripting Bugs

Posted: 09 Apr 2015 12:50
by bdeshi
Report() templates for CustomColumns can only retrieve values of the first 5 CCs.

Code: Select all

 text report("{custom 1}|{custom 2}|{custom 3}|{custom 4}|{custom 5}|{custom 6}", <curitem>);

Re: Scripting Bugs

Posted: 11 Apr 2015 16:36
by admin
SammaySarkar wrote:Report() templates for CustomColumns can only retrieve values of the first 5 CCs.

Code: Select all

 text report("{custom 1}|{custom 2}|{custom 3}|{custom 4}|{custom 5}|{custom 6}", <curitem>);
Confirmed, only the 5 hard custom columns are supported.

Re: Scripting Bugs

Posted: 11 Apr 2015 16:36
by bdeshi
allow all.
This apparently supported all columns in the past, what's the reason for this change?

Re: Scripting Bugs

Posted: 11 Apr 2015 16:41
by admin
No, they have never been supported. Their nature is too different from the rest internally. Would need lots of heavy rewriting.

Re: Scripting Bugs

Posted: 11 Apr 2015 17:04
by bdeshi
How? forgive me, but as I see it, the first five CCs are completely interchangeable with all the others -- we can swap them at any time by editing, and report doesn't fail then ; seems there's nothing special about those first ones, other than they come predefined by default.

Re: Scripting Bugs

Posted: 11 Apr 2015 17:05
by admin
I made it appear like that. :)

PS: Try this to see a bit of the inner difference:

Code: Select all

text columnlayout(, "get");

Re: Scripting Bugs

Posted: 13 Apr 2015 12:13
by admin
Next version you can report those columns via their captions. :cup:

Re: Scripting Bugs

Posted: 14 Apr 2015 11:25
by zer0
By the way of unwanted behaviour, I have to say that I do not like the fact that you cannot minimise XY when a script is running. What is the reason for this? I often run a script that takes 1-2 minutes to execute, so not allowing me to minimise XY seems a bit harsh.

Another kick in the teeth is that the message that pops up to say that you cannot minimise XY while a script is running actually pauses the running script. I mean, come on, if you are going to tell me that I cannot do something, do not delay something that is stopping me from doing what I want to do.

Re: Scripting Bugs

Posted: 14 Apr 2015 14:36
by admin
There is a reason for this:

Code: Select all

v8.90.0001 - 2010-03-11 21:38
    * Scripting: Experimentally it is now disallowed to minimize the 
      application while a script is running. Reason: Any modal forms 
      popped by a script while the application is minimized would block 
      the application.
Not sure though if this is still valid in Win8.1 and later, and no time to test now.

Re: Scripting Bugs

Posted: 14 Apr 2015 14:47
by zer0
admin wrote:There is a reason for this:

Code: Select all

v8.90.0001 - 2010-03-11 21:38
    * Scripting: Experimentally it is now disallowed to minimize the 
      application while a script is running. Reason: Any modal forms 
      popped by a script while the application is minimized would block 
      the application.
That is all well and good if a script has any modal forms to pop-up. My script, for example, is a collection of folderreport() commands that dump to individual files. No pop-up forms, modal or otherwise. Clearly, my scenario does not fit the use case of the restriction that has been introduced, so I would appreciate if you could please either remove it or add logic that determines if a script meets the restriction criteria. Such broad, sweeping restriction seems unjustified.

Re: Scripting Bugs

Posted: 14 Apr 2015 15:08
by admin
Too difficult. I'll add a tweak: ScriptAllowMinimizeApp=1