32 replies to this topic

[pscEx]

Before I publish WinBuilder 077 beta 3, I would like that developers test the new Interface Functionality.

Short said:

• Important interface component values can be changed by the Set command, just like variables.
• The change is shown immediatelly; System,RefreshInterface is not longer necessary.
• System,RefreshInterface just reloads the interface from script and builds it again.

To test, you can download a 'complete' project from http://nativeex.boot...e/Interface.zip

You have to understand one fact:

Whenever a button is clicked, when starting the according action, first the current interface is saved to the script.
Without that it would not be possible to use actual user changes.

Have fun with testing, and give me respond and maybe suggestions.

BTW:

The crash on WB exit depends on the restricted abilities of this test version.

Please do not try to use this WB version to test your projects. For that it would be better to use some trash!

Peter

[Lancelot]

Hi Peter,

My first todo today, testing new feature
First of all, System,RefreshInterface is still necessary (no further comment for now )

verry sorry for finding bugy

2bugies

to demonstrate finding i change [On] section

[On]

Set,%pTextLabel1%,"Hi Peter",Permanent

Set,%pTextBox1%,"How are you",Permanent

Set,%pCheckBox1%,True

and press On button
first look everything seems oki, i click on "Interface Test" (script.project) and click back to Bla
1)
than surprise seeing these on interface:
Hi#$sPeter
How#$sare#$syou
I believe since we are changing interface we would not like to see new users get these!
2)
and surprise seeing Local Change (%pCheckBox1%) still selected
well in fact not surprise, i believe it is not a bugy. Selecting CheckBox permanent or not dont effect gui result but will be a good during build process (A note to history...txt will be good to point that )


After the changes/fixes you make for current interface, also some small idea(s) connected to

first the current interface is saved to the script.

[pscEx]

#1: I already saw this. There is a new fixed test project with all available functionality.

#2: When you leave a script, the current state is saved.

Peter

[Lancelot]

#1: I already saw this. There is a new fixed test project with all available functionality.

i havent saw new fixed version

checking the current link with new 6408614C3042FD02C94D5F907A0EA99B same failure
ps:old F71189B6D463E6BBE654CBF99897FD04

well i am sure you will fix or already fixed.... just reporting

#2: When you leave a script, the current state is saved.

A nice warning for histroy


further:

first the current interface is saved to the script.

! well, besides the current improvement on handling existing interface settings, we need a button to change all Interface section.
With currrent versions of wb 2 things required
System,RefreshInterface --> will be available on next version, till than we use ReScanScripts
And an external file or script **

Currently LiveXP script.project and olegpov's new msst script uses similar ways which requires an external file. It will be much better to have this option available without external file. Maybe new side feature of saving current interface the script maybe used or not !.
Maybe a new command for switching sections in ini file,

IniSwitchsection,%scriptfile%,Interface,Interface-Advanced

System,RefreshInterface

would make life much easier for script writers.

-->if you dont like the idea than no more commments about this

[pscEx]

The test package now contains a new WinBuilder command:

Visible,%pComponent%,True / False
Also optional parameter PERMANENT provided

It changes dynamically the visibility of components.

Peter

[pscEx]

#2: When you leave a script, the current state is saved.
A nice warning for histroy

That has been in this manner since OpenBuilder.

Currently LiveXP script.project and olegpov's new msst script uses similar ways which requires an external file. It will be much better to have this option available without external file. Maybe new side feature of saving current interface the script maybe used or not !.
Maybe a new command for switching sections in ini file,

IniSwitchsection,%scriptfile%,Interface,Interface-Advanced

System,RefreshInterface

would make life much easier for script writers.

I think that this can be performed by the new Visible command.

Peter

[amalux]

Dramatic improvement!

I used olegpov's new interface as a test and the switch back and forth was quite smooth. If it were possible to avoid the jump to progress bar, it would provide an even more seamless transition but I don't know if this is possible.

I get an error after the transition which is probably unrelated or a simple fix in the script (I didn't look) but it doesn't occur with previous WB so I'll report here just fyi:

[homes32]

Dramatic improvement!

I used olegpov's new interface as a test and the switch back and forth was quite smooth. If it were possible to avoid the jump to progress bar, it would provide an even more seamless transition but I don't know if this is possible.

skipping the progress bar would be great! this especially annoys me with the help/info buttons that people use there is an extra couple of seconds delay while a Messagebox pops up....


I would rather see tooltips implemented for controls. much neater, and would reduce interface clutter and load time.

[olegpov]

I get an error after the transition which is probably unrelated or a simple fix in the script (I didn't look) but it doesn't occur with previous WB so I'll report here just fyi:

It is generated by DPs-MassStorageDrivers_MSST script when it is impossible to define version OS

look code from script

If,NOT,%OS%,EQUAL,"XP",If,NOT,%OS%,EQUAL,"W2003",Run,%ScriptFile%,Process-ErrorMessage,"Unknown Source OS Version Check for Retrieve Project Info script"

[amalux]

It is generated by DPs-MassStorageDrivers_MSST script when it is impossible to define version OS

look code from script

If,NOT,%OS%,EQUAL,"XP",If,NOT,%OS%,EQUAL,"W2003",Run,%ScriptFile%,Process-ErrorMessage,"Unknown Source OS Version Check for Retrieve Project Info script"

Well, I knew that -- Why is it popping up now? My OS (XP) hasn't changed

[olegpov]

Probably because

BTW:

The crash on WB exit depends on the restricted abilities of this test version.

Please do not try to use this WB version to test your projects. For that it would be better to use some trash!

Peter

[Lancelot]

*

That has been in this manner since OpenBuilder.

yep i know, I recommended a warning (reminding/memo..) for users that use this feature without permanent. Nevermind they will understand with some trials.

*

I think that this can be performed by the new Visible command.

yep/nope --> ........ never mind, promise is promise no more comments about this.

* text label & textbox

[pscEx]

I used olegpov's new interface as a test and the switch back and forth was quite smooth. If it were possible to avoid the jump to progress bar, it would provide an even more seamless transition but I don't know if this is possible.

A new option under Tools has been implemented:

It suppresses appearence of progress window, if the run type is 'Non-Arrow'. That means usually caused by button click.

Peter

[pscEx]

I would rather see tooltips implemented for controls. much neater, and would reduce interface clutter and load time.

That is in the current interface implementation rather difficult, not to say impossible.

In order to be compatible with current interfaces, the tooltip has to be added as last parameter to the component string.

And several components have an 'unlimited' number of arguments ...

So: How decide whether last argument or tooltip?

Peter

[amalux]

A new option under Tools has been implemented:

It suppresses appearence of progress window, if the run type is 'Non-Arrow'. That means usually caused by button click.

Peter

Don't get the joke but thanks, I'll test when available in livexp

[pscEx]

I removed this option.

Reason:

If a button starts a lenghty operation, WB w/o progress window 'hangs' for maybe some minutes.

I changed to this functionality:

The three Interface components which can run a section (Button, CheckBox, RadioButton) got an additional option:

The 'No Progress' checkmark defines individiually whether progress window is shown or not, when the section is run.

Compatibility with existing scripts is no issue: The option defaults to 'show Progress' if not defined.

Peter

BTW: Available (hopefully) in some minutes. I have troubles with upload.

[pscEx]

Dramatic improvement!

I used olegpov's new interface as a test and the switch back and forth was quite smooth. If it were possible to avoid the jump to progress bar, it would provide an even more seamless transition but I don't know if this is possible.

I think that I have to beg the pardon from many members, but I'm currently for 110% engaged in WB development.

Therfore I'm sure that I sometimes may miss important topics.

What is olegpov's new interface ?

Peter

[olegpov]

What is olegpov's new interface ?

I think it a beta version of my script
Post #28

[pscEx]

I think it a beta version of my script
Post #28

OOPS!

That is a real work to understand or try all, resp. !

I'll try tomorrow!

Peter

[Lancelot]

That is a real work to understand or try all, resp. !

already written before with:

...Currently LiveXP script.project and olegpov's new msst script uses similar ways which requires an external file.......

and you have a good reason

I think that I have to beg the pardon from many members, but I'm currently for 110% engaged in WB development.

Therefore I'm sure that I sometimes may miss important topics.

Now helping for memory (memo's are guut , reminding my old memo suggestion at post12 )

Maybe new side feature of saving current interface the script maybe used or not !.
Maybe a new command for switching sections in ini file,

IniSwitchsection,%scriptfile%,Interface,Interface-Advanced

System,RefreshInterface

would make life much easier for script writers.

reply 1:

Visible,%pComponent%,True / False
Also optional parameter PERMANENT provided

It changes dynamically the visibility of components.

reply 2:

I think that this can be performed by the new Visible command.

My final reply:

* yep/nope --> ........ never mind, promise is promise no more comments about this.

But as the current topic came back to this subject again, The day come to explain a bit more .
to clear yep/nope:
yep: olegpov's script interface (and many others that follow) will be much better/faster.. with new visibility options. It is nice to hide advanced features .
nope: new visibility options cant be used with script.project 1) because of forgotten visibility ,0 in older winbuilders 2) too hard to prepare with this visibility option for LiveXP script.project.
Also other script writers who require 2 absolutely different oriented interface will go on with current alive solution with System,RefreshInterface .
For nope case The requirement for external file is annoying and after you wrote and i notice at post 1

Whenever a button is clicked, when starting the according action, first the current interface is saved to the script.

I asked IniSwitchsection , maybe better to ask Interfaceswitch .

Maybe to understand my nope reason, and especially "IniSwitchsection" suggestion i updated exeandchangelog.script, and again maybe you can take a look only with downloading script.project and exeandchangelog.script (Small A button which was announced a long while ago)
I am happy with System,RefreshInterface without IniSwitchsection . I am sure in time you will see some others adding an external file to his script to swtich all interface. And with some others complaining, the day will come .

Above of this post is only a reminder for Peter to support his memory +explanations. No suggestion, no asking a new feature, totally nothing new.


Biiiggggg special thanks to olegpov for helping System,RefreshInterface back alive. .

@peter
with WinBuilder077_Beta2.zip we have file version number 77.0.0.0 and version says 077.02 -> maybe it is better if they match orrr not with later releases, as you wish, no more comments about this till the day .......

@olegpov
check [switcher] section of new exeandchangelog.script so amalux can get less error tests

@amalux
I believe having System,RefreshInterface is quite fast and satisfactory. Check switching livexp script.project from basic to advanced (vice versa) after updating . Use psc's GUI Interface version only for Interface tests.
ps: My old memo notes:
// System,RefreshInterface - An old bugy feature which is not available now (076 no effect-077b2 giving error but also working)

[pscEx]

New test version online.

Now the key [Main]Interface= of a script defines the used interface.
Of course the '-Language' feature is still working.

The script itself can change it's own interface by

[First]

 IniDelete,%ScriptFile%,Main,Interface

 System,REFRESHINTERFACE

 

 [Second]

 IniWrite,%ScriptFile%,Main,Interface,Interface_A

 System,REFRESHINTERFACE

Peter

BTW: This change I applied to olegpov's script:

[Process-Switch-Mode]

// psc new version

IniRead,%ScriptFile%,Main,Interface,%current%

If,%current%,EQUAL,Interface-Advanced,IniDelete,%ScriptFile%,Main,Interface

Else,IniWrite,%ScriptFile%,Main,Interface,Interface-Advanced

// psc commented old version

//Run,%ScriptFile%,Process-Init,Vars

//If,NOT,EXISTFILE,%MSSTRoot%\interfacemode.script,ExtractFile,%ScriptFile%,"Folder","interfacemode.txt",%MSSTRoot%

//If,EXISTFILE,%MSSTRoot%\interfacemode.txt,FileRename,%MSSTRoot%\interfacemode.txt,%MSSTRoot%\interfacemode.script

//Run,%MSSTRoot%\interfacemode.script,Process-Switch-Mode,%ScriptFile%

// psc end

//

//_______________________________________________________________________________

//

//System,REFRESHINTERFACE - not properly work on WB Smaller 077

If,%Version%,Smaller,077,System,RESCANSCRIPTS

Else,System,REFRESHINTERFACE

//_______________________________________________________________________________

//System,REFRESHINTERFACE

Additionally added a 'no progress show' to the buttons

pButton1="Switch To Advanced Mode",1,8,336,216,141,25,Process-Switch-Mode,-1

pButton1="Switch To Basic Mode",1,8,335,288,141,25,Process-Switch-Mode,-1

[Lancelot]

Hallo psc!
Alle sollten zufrieden mit diesem

[homes32]

That is in the current interface implementation rather difficult, not to say impossible.

In order to be compatible with current interfaces, the tooltip has to be added as last parameter to the component string.

And several components have an 'unlimited' number of arguments ...

So: How decide whether last argument or tooltip?

Peter

that is a good point! some possibilities

adding a separate section for tool tips

[tooltips]
pcheckbox1=This turns something on
pcombobox1=this is a list of things to turn on.

adding some sort of identifier to the tool tip argument
pCheckBox2="Permanent change",1,3,331,211,125,20,False,tip="This also turns something on"

[pscEx]

I have to "sleep some days" about your suggestions. They sound well but I'm not yet convinced. Anywhere in the back of my brain there is still a 'Warning'

Let me confirm to you, that I want to develop a solution. But currently not yet an idea, how.

Peter

[Lancelot]

Hi psc

maybe this helps, a request hidden (never written) in my mind for usual reasons.

Currently auto language of interface (ex: [Interface] [Interface-German] ...) can not be used or preferred (I guess you remember i tried using this feature a lot).
Reason is:
example:
when writing a script, if script writer change location of a button, (s)he have to change at all interfaces.
Lots of works to do if script writer likes to keep up to date of the script. ---> Not prefered

Idea Is:
having multilanguage part of interface simpler

[Interface]

pTextBox1="Hello Peter psc",1,0,43,165,168,21,



[Interface-German]

pTextBox1="Hallo Peter psc"

Summing this idea with homes32 idea

[Interface]

pTextBox1="Hello Peter psc",1,0,43,165,168,21,



[Interface-German]

pTextBox1="Hallo Peter psc"



[Interface-ToolTips]

pTextBox1="There is only one Peter psc"



[Interface-ToolTips-German]

pTextBox1="Es gibt nur eine Peter psc"

Maybe you dont like at all , well it is 1 time request which has no severity (-999999999~~) for me, i wont post anymore about that if you dont like (or respond positive) about the idea.

CU