44 replies to this topic

[Lancelot]

I see you have not read Galapo's topic or my posts in detail to see the issue.
Repeating again for ..... : We do not have a problem with seperating macros with variables which we already did.
Winbuilder have a syntax problem !!

But if you like to comment more without spending time to understand what is going on, have fun.

[Brito]

If Bootland is reachable tomorrow, i bet he answers.

Boot Land will likely be closed for business during a few hours in the morning. I think this coincides with 11h00~17h00 in Germany's time fuse.

I need to wait a long time until I can log with a ssh connection and ask for a reboot.

Yesterday our site ranked at the 23 000 most popular sites on the planet, don't know if real people or bots are coming here to visit us..

[Galapo]

I see, so your problem is not that you can't make the script work, but that you can't make it work by converting variables and macros forth and back, like you want to.

Can't remember Peter ever saying anything about, if that is even allowed, since variables and macros got seperated.
But i guess not, cause else there would have been little sense in seperating the two in the first place. But better ask Peter that.

Hi MedEvil,

Since Peter's idea was to separate variables and macros, my idea that was rejected was to use a different command for setting of variables to macros, ie 'Set' for variables and 'SetMacro' for macros. http://www.boot-land...?...ost&p=90523

Peter said that 'Set' could handle both, but the problem is that when we come to 080 it isn't working in all cases. So it's not just that 080 is not backbards compatible with some previous script syntax, we can get older scripts yet updated to new WB handling.

Regards,
Galapo.

[MedEvil]

Peter said that 'Set' could handle both,

Well if he said that, then we have a bug.
My latest knowledge is, that nacros are only to be declared in variables section.

[Brito]

So it's not just that 080 is not backbards compatible with some previous script syntax

Was this functionality available on the previous stables 078 and 076?

Backwards compatibility should only focus on stable releases, versions in between are volatile.

[Galapo]

Was this functionality available on the previous stables 078 and 076?

Yes, it was available. Hence the issue and our frustration with getting LiveXP updated for use with new 080.

Regards,
Galapo.

[Wonko the Sane]

Was this functionality available on the previous stables 078 and 076?

Some nice pictures of latest stables of Winbuilder :
076:


078:


080:


As you can see in "stable" 080 the V-cut door was moved from center to the right, and a lot of horses, driven by habits, and BECAUSE noone actually properly trained them in the new environment, are seriously harming their heads by trying to peek outside of the gates in the center of them, where now solid bars are.

What the horses are saying, amounts more or less to:


Medevil, having never peeked outside (being it's main activity that of criticizing what the other horses are doing from the inside of his box) is of course unaffected by the changes.



Wonko

P.S.: Just in case, I also have a picture of the un-stable 077-rc2:

(with Galapo looking in it particularly happy )

[Galapo]

As you can see in "stable" 080 the V-cut door was moved from center to the right, and a lot of horses, driven by habits, and BECAUSE noone actually properly trained them in the new environment, are seriously harming their heads by trying to peek outside of the gates in the center of them, where now solid bars are.

You really made me laugh with your latest image-finding effort! Very good illustration of what has happened.

P.S.: Just in case, I also have a picture of the un-stable 077-rc2:

(with Galapo looking in it particularly happy )

Yep, no serious head-butting there. Limitations are clear. Just need direction in the new stables.

Regards,
Galapo.

[Wonko the Sane]

You really made me laugh with your latest image-finding effort! Very good illustration of what has happened.

I hope you appreciated also how I got 'em from down-under (actually NZ) so that you don't need the usual picture flipping software to avoid seeing them upside down....



Wonnko

[Galapo]

I did actually notice they were more "our" style stables.

The giveaway was as you said that I didn't have to turn my laptop upside down to see the pictures properly.

Regards,
Galapo.

[Brito]

That's some nice stables with no doubt..

[Wonko the Sane]

That's some nice stables with no doubt..

Sure , but living outside of the Asylum, I feel even happier :




Wonko

[Galapo]

In the mentioned post I showd you the correct script command use which lets it work.

Hi Peter,

Actually still not working as intended. Your "correct script command" does not relate to the issue as raised in the topic. I've made a couple of more posts for you to hopefully see the issue a bit more clearly.

Thanks,
Galapo.

[Galapo]

Sure , but living outside of the Asylum, I feel even happier :

But you might need to go to the dentist for a teeth clean!

[Wonko the Sane]

But you might need to go to the dentist for a teeth clean!

..... and I also need to quit smoking



Wonko

[pscEx]

Since Peter's idea was to separate variables and macros, my idea that was rejected was to use a different command for setting of variables to macros, ie 'Set' for variables and 'SetMacro' for macros. http://www.boot-land...?...ost&p=90523

Peter said that 'Set' could handle both, but the problem is that when we come to 080 it isn't working in all cases. So it's not just that 080 is not backbards compatible with some previous script syntax, we can get older scripts yet updated to new WB handling.

That works in All cases.
Set puts items with % into the variables collection and items w/o % into the macros collection.
What can go wrong?

Hi Peter,

Actually still not working as intended. Your "correct script command" does not relate to the issue as raised in the topic. I've made a couple of more posts for you to hopefully see the issue a bit more clearly.

Thanks,
Galapo.

The issue is that in your solutiuon one macro in the script uses another macro in the CAPI.
And that was not intended and therefore not provided.

In rev. 3 it is.

Peter

BTW: Instead of writing so many posts with code, only one post would have been necessary.

Macro nesting does not work

I unerstand that rather late, when you first time spoke about CAPI.

[Galapo]

What can go wrong?

Well, nothing in theory. But in practice just what occurred: script was working under earlier version, but broken under new version until WB fix was forthcoming. See Jaclaz stable images for visual representation.

But now that is fixed, there's no issue.

Thanks,
Galapo.

[Wonko the Sane]

Stable 080 rev.3 :


In this model the V-cut door can be placed in the center or to the left or right side, according to the single horse's preferences and habits.



Wonko

[pscEx]

Now the compiler autoincrements the build # of the file version.

In scripts it can be referenced by %FileVersion% and has the format

<major>.<minor>.<revision>.<build>

Peter

[Galapo]

Thanks, Peter!

Regards,
Galapo.