Jump to content











Photo
- - - - -

Bug in "Visible" command in latest "pre-releases (81)


  • Please log in to reply
58 replies to this topic

#1 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1338 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 04 May 2011 - 06:05 PM

Seems there is a bug in the visible command in 81 - attached test script...(works as expected in 80)

Attached Files



#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 04 May 2011 - 09:16 PM

Thanks, Scott!

I was able to reproduce.

Peter

#3 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 04 May 2011 - 09:35 PM

Fixed! :buehehe:

Peter

#4 MichaelZ

MichaelZ

    Frequent Member

  • Team Reboot
  • 333 posts
  • Location:Braunschweig, Germany
  •  
    Germany

Posted 04 May 2011 - 09:38 PM

Fixed! :buehehe:

Fine. :cheers:
But where's the link for the download? :)

Many Greetings
MichaelZ

#5 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 11:10 AM

Currently the actual version exists only in my development PC. :)

I have no idea whether it will be decided to publish as alpha, beta or final. :buehehe:

Peter :cheers:

#6 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 May 2011 - 11:27 AM

It will be published when/if the new version is compatible with the scripts that run at version 080.

This means replacing 080 with a new version and still use the current projects from the download center.

#7 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 11:38 AM

It is difficult to decide about compatibility, when there is nobody who can compare.
To check the compatibility between "Item 80" and "Item 81", "Item 80" AND "Item 81" should be available.

Currently I'm the only one who can test for compatibilty, and my current results are ramarkably above 95 %

Peter

#8 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 May 2011 - 12:18 PM

Currently I'm the only one who can test for compatibilty

It is not black magic. I compared both of them several months ago and we've spoke about this, do you remember?

The version you propose breaks current projects without real need. At the time I suggested you to pick the code from 080 and keep it compatible from start while working on improvements.


Let's keep things simple and painless for everyone.

#9 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 12:44 PM

I compared both of them several months ago and we've spoke about this, do you remember?

And what about actual compare?

The version you propose breaks current projects without real need.

IMO real need is a speed increase of 250%

Let's keep things simple and painless for everyone.

I agree: Painless for everyone is, if nothing changes.

I committed my current WB souce code to the SVN.

Peter

#10 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 May 2011 - 12:56 PM

IMO real need is a speed increase of 250%

My friend, what we need is stability.

#11 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 02:01 PM

"Stability" IMO sometimes implies "No Progress"

Peter

BTW: For me it is appropriate now working again with important issues such as multiPE ...

#12 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 May 2011 - 04:27 PM

Sorry Peter, defect fixing is good and invalidating current projects is not.

As winbuilder developers, it is our responsibility to provide a stable engine.

#13 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 06:01 PM

... invalidating current projects is not.


I think that the "invalidating" referres to the revolution which was started by Galapo.

He mentioned "a lot of scripts" to be changed.

And here how he / Lancelot solved: Only some lines in the API script:
[ConvertVariableToMacro_Post80]

...

FileCreateBlank,%ProjectTemp%\CapiCommand_Temp\CapiCommand.txt

TxtAddline,%ProjectTemp%\CapiCommand_Temp\CapiCommand.txt,[VariableToMacro],Prepend

TxtAddline,%ProjectTemp%\CapiCommand_Temp\CapiCommand.txt,"Echo#$c#$qImproved (sarcasm) exbuilder81x can not do this - Can you believe that :clap:#$q",Append

TxtAddline,%ProjectTemp%\CapiCommand_Temp\CapiCommand.txt,"#2#$c#3#$c#4#$c#5#$c#6#$c#7#$c#8#$c#9",Append

...

Run,%ProjectTemp%\CapiCommand_Temp\CapiCommand.txt,VariableToMacro
BTW: Have a look at the unnecessary "(sarcasm)" line (may give a hint to some background intentions).

This "revolution - Reason", to distinguish macros and variables, has never beean a theme in all other projects besides LiveXP (which is, following a post of Wonko, 'burned out').

I do not feel responsible to provide a stable ( = "all known bugs accepted") engine.
Here the fixes (available only for me, on my development PC) since the 080 release:

fixed - Parameter existing only of 2 quotes now becomes empty
fixed - Do not write surrounding quotes into variables when reading the [variables] section
fixed - resolve escapes to character in If command compares
fixed - (Finally) Do not write surrounding quotes into variables when reading the [variables] section
fixed - resolve escapes to character in If,QUESTION
fixed - several 'surrounding quotes' bugs in If command
fixed - "Coolest Bug ever!" corrupting .scr file
fixed - bug in FileCopy / DirCopy command with SHOW option
fixed - log output for If commands
fixed - Bug in PackParam
fixed - Bug in RegWriteBin
fixed - Bug in StrFormat,Rtrim
fixed - Incompatibility of GetParam, introduced by the bug fix of PackParam
fixed - Bug in RegWrite,HKLM,0x1,WB-Setup\Classes\SHCmdFile\shell\open\ddeexec,,"[ShellFile(""%1""#$c""%1"",%S)]"
fixed - License window sizing issue
fixed - Bug in log.html generation causing 'Index out of bounds' when logging a Loop command
fixed - Bug causing 'Access Violation' in interface
fixed - Bug in logging error of DirCopy command (wrote " + s" rather than error description)
fixed - bug "AddInterface does not work when used with run"
fixed - Bug in interface due to values with quotes
fixed - Bug in running section on CheckBox click
fixed - Bug in Interface Click event handling
fixed - Bug in If command, when comparing numerical values
fixed - Comma issue in If commands
fixed - Bug in OUT: parameters handling
fixed - access violation in Set,%InterfaceVar%
fixed - Bug which did not allow GLOBAL changes of %Constants%
fixed - Bug with duplicating quotes in interface text labels
fixed - Bug in IniDelete
fixed - Bug in logging Loop statements
fixed - #$xs sometimes not resolved
fixed - Codebox in a fresh started WB was without API
fixed - some smaller bugs when treating multiple components in interface editor
fixed - bug in progress window when exec a script at tree end
fixed - made behaviour of interface component 'FileCheckList' logically compatible to WinBuilder 076
fixed - bug when aborting "Add component to interface"
fixed - bug: Set,%InterfaceComponent% PERMANENT sometimes corrupts interface
fixed - Bug in RegMulti, which overwrote %variables%
fixed - Bug in StrFormat when writing result to parameter #n
fixed - bug in positioning of RadioGroup when scrollbars used
fixed - bug "RegWrite,HKLM,0x3,<Section>,<Keyname>,%variable%"
fixed - bug "RegMulti,HKLM,Section,Key,DELETE,SubVal bug"
fixed - bug in Visible command

As usual, some of them, e.g. the last "Visible" one are introduced by current fixes. But most of them fix real 080 bugs.

Does "Stable" mean "Bugs are well known"

For me, this topic is "out of interest now"

Peter

#14 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 06:15 PM

It will be published when/if the new version is compatible with the scripts that run at version 080.

This means replacing 080 with a new version and still use the current projects from the download center.

download http://nativeex.exec...s/WinBuilder.7z, and unpack with PWD iceland.

Then please tell me, which project does not run with the "nightly"!
Hint: You MUST also download the actual version of all these projects!
If you find any, I'll fix that!

Peter

#15 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1338 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 05 May 2011 - 08:44 PM

download http://nativeex.exec...s/WinBuilder.7z, and unpack with PWD iceland.

Then please tell me, which project does not run with the "nightly"!
Hint: You MUST also download the actual version of all these projects!
If you find any, I'll fix that!

Peter

Thanks and I will continue to do some testing on things like win7PE_SE and others as I have time/capability to do so...

While there are others (not named here) that think this isn't worthwhile, I do...BUT, I have to also agree with Nuno that stability in the syntax is also VERY important, even if that means that the engine stands a bit still...since (to me) the important things are the projects...the WB exe is just a tool to make them realizable...Speed is important, but only for thigns that take WAY too long...a 250% increase on a 1 minute task isn't that critical (i.e. even going from 2-3 minutes down to less than one minute - especially when things like using the current dism to mount an image can take 4-5 minutes, and another 4-5 minutes to dismount...

BUT, bug fixes like this (and all the others) are important to me! As is full docs on all the functionality!

Again, thanks.
Scott

#16 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 May 2011 - 08:46 PM

Then please tell me, which project does not run with the "nightly"!
Hint: You MUST also download the actual version of all these projects!
If you find any, I'll fix that!

That's the spirit! :(

Let's gather the community to help improving the next winbuilder version.

I will open a new topic within the next days to invite people downloading version 081 and trying it out with the current projects. It won't just be me trying the projects, I am sure that more people will have interest in participating.

If you are up to the challenge, we shall have a version 082 before the month ends. :ph34r:

Can the fun begin?

:cheers:

#17 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 May 2011 - 10:04 PM

That's the spirit! :thumbup:

Let's gather the community to help improving the next winbuilder version.

I will open a new topic within the next days to invite people downloading version 081 and trying it out with the current projects. It won't just be me trying the projects, I am sure that more people will have interest in participating.

If you are up to the challenge, we shall have a version 082 before the month ends. :ph34r:

Can the fun begin?

:cheers:

I'm so glaaaaaaad about your decision.

If necessary, I'm going to have a 28 hours day :cheers: / :(

Peter

#18 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15041 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 05 May 2011 - 10:32 PM

...and I had this queer idea that people could learn from past errors.... :ph34r:


:(
Wonko

#19 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 05 May 2011 - 11:17 PM

Seems to be a problem with the latest winbuilder showing the image number scrollbox in the win7pe images.script if 'Choose your image index' is selected. See attached images.

Attached Thumbnails

  • index1.PNG
  • index2.PNG


#20 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 06 May 2011 - 12:07 AM

For me there is a huge difference in speed between winbuilder 80 and the latest winbuilder with the supercharge option enabled.

Building on win7 sp1 x64 using a quad core I7 I get the following ( both using imagex version 6.1.7600.16385 ) and building the win7pe se project:

version 80 - 9:56

latest - 3:45

#21 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 May 2011 - 07:02 AM

Seems to be a problem with the latest winbuilder showing the image number scrollbox in the win7pe images.script if 'Choose your image index' is selected. See attached images.

Where do I get this script?

I did a new download of win7pe_se, but the script is not contained.

Peter

#22 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 06 May 2011 - 11:38 AM

It was written by ChrisR. Not quite sure where I downloaded it from. Anyway its available here:

http://wb.paraglider...E/Images.script

#23 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 06 May 2011 - 11:45 AM

It was part of "Package_2011_04_29.7z" downloaded from the other g??? w???? forum where discussion of win7pe se seems to have moved. I don't tend to spend too much time there as there are far too many negative posts

#24 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 May 2011 - 01:26 PM

Seems to be a problem with the latest winbuilder showing the image number scrollbox in the win7pe images.script if 'Choose your image index' is selected. See attached images.

Fixed (currently in my develop system only)

fixed - made z-order of components compatible to version 80


Peter

#25 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10547 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 06 May 2011 - 02:38 PM

Shall the testing begin?

Peter, would you please update a binary as "winbuilder081_YYMMDD.exe" where YYMMDD represent the current year, month and day?

This way it can be updated and we can put several exe's on the same folder to verify the results.

Next monday I'll announce the 081 testing phase over the newsletter so that we can get more feedback from the masses.

:cheers:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users