OS/2, eCS & ArcaOS - Technical > Applications

XWP v1.0.16

<< < (5/19) > >>

Andy Willis:

--- Quote from: Rich Walsh on November 06, 2023, 06:36:20 am ---XWP v1.0.16 introduces some of the most significant Desktop usability improvements in years.

XStartup
Large parts of the XStartup code have been rewritten for improved reliability. It should no longer be necessary to impose a long delay to ensure the first object starts properly. XStartup's notebook page has also been updated with XWP-Full's Boot Logo option getting its own page.

--- End quote ---
How hard would it be to add the initial delay back? I had imposed I think just a one second (maybe 3, I don't recall now) delay to prevent a 30-45 second hang that is now back (I had timed it back then but haven't now that it is back).  If the code is still there but just either commented or ifdef'd out, I should be able to build it (assuming my build environment is still good).

Andy Willis:

--- Quote from: Andy Willis on December 09, 2023, 06:44:04 pm ---
--- Quote from: Rich Walsh on November 06, 2023, 06:36:20 am ---XWP v1.0.16 introduces some of the most significant Desktop usability improvements in years.

XStartup
Large parts of the XStartup code have been rewritten for improved reliability. It should no longer be necessary to impose a long delay to ensure the first object starts properly. XStartup's notebook page has also been updated with XWP-Full's Boot Logo option getting its own page.

--- End quote ---
How hard would it be to add the initial delay back? I had imposed I think just a one second (maybe 3, I don't recall now) delay to prevent a 30-45 second hang that is now back (I had timed it back then but haven't now that it is back).  If the code is still there but just either commented or ifdef'd out, I should be able to build it (assuming my build environment is still good).

--- End quote ---
Never mind, I was able to work around it by moving TCPIP startup to launch second instead of first.  Previously, I was unsuccessful in affecting the hang by changing the order.

Rich Walsh:

--- Quote from: Andy Willis on December 09, 2023, 06:44:04 pm ---
--- Quote from: Rich Walsh on November 06, 2023, 06:36:20 am ---Large parts of the XStartup code have been rewritten for improved reliability. It should no longer be necessary to impose a long delay to ensure the first object starts properly.

--- End quote ---
How hard would it be to add the initial delay back? I had imposed I think just a one second (maybe 3, I don't recall now) delay to prevent a 30-45 second hang that is now back (I had timed it back then but haven't now that it is back). 
--- End quote ---

I didn't get rid of the delay. It was a global rather than per-object setting, so I moved it to the Desktop 'Startup' tab where you create your first Startup folder. It starts out set to 1 second because there's always a 1-sec delay before XWP does _anything_. Values greater than 1 include that initial delay.


--- Quote ---If the code is still there but just either commented or ifdef'd out, I should be able to build it (assuming my build environment is still good).

--- End quote ---

I seldom leave detritus lying around - that's what version-control systems are for. If there's a problem with any change I've made, please advise so that I can fix it for all users (assuming it needs fixing).

Andy Willis:

--- Quote from: Rich Walsh on December 09, 2023, 10:28:59 pm ---
--- Quote from: Andy Willis on December 09, 2023, 06:44:04 pm ---
--- Quote from: Rich Walsh on November 06, 2023, 06:36:20 am ---Large parts of the XStartup code have been rewritten for improved reliability. It should no longer be necessary to impose a long delay to ensure the first object starts properly.

--- End quote ---
How hard would it be to add the initial delay back? I had imposed I think just a one second (maybe 3, I don't recall now) delay to prevent a 30-45 second hang that is now back (I had timed it back then but haven't now that it is back). 
--- End quote ---

I didn't get rid of the delay. It was a global rather than per-object setting, so I moved it to the Desktop 'Startup' tab where you create your first Startup folder. It starts out set to 1 second because there's always a 1-sec delay before XWP does _anything_. Values greater than 1 include that initial delay.


--- Quote ---If the code is still there but just either commented or ifdef'd out, I should be able to build it (assuming my build environment is still good).

--- End quote ---

I seldom leave detritus lying around - that's what version-control systems are for. If there's a problem with any change I've made, please advise so that I can fix it for all users (assuming it needs fixing).

--- End quote ---
OK, tested making the changes on the startup tab.  After moving tcpip startup back to the first program to launch and booted set to 3 seconds, 2 seconds and unhelpfully back at 1 second (unhelpfully in that I now have no idea why it was hanging as it no longer does in the original configuration).

Andy Willis:
OK, one thing that should be checked to see if it is just an oddity on my system. Whenever I open the desktop properties and go to the Startup tab the delay always initially shows 1.  If I had previously changed it, I can hit Default and it will then show the number I had changed it to.  I can change tabs and go back and it will show the number I had set it to (IOW, going back to 1 is only on initial open).  If I open the Desktop properties and do not open the startup tab, make some changes on other tabs and close it and then open the Desktop properties and the startup tab, I can click default and have the number I had previously set.  If I open the Desktop properties and open the startup tab and close the properties, when I reopen the properties it will have saved the 1 second delay (IOW now clicking default does not change it to what I had set it to previously because it saved the 1 that was showing when I closed the properties.). 

Steps to reproduce:
Open Desktop properties
Open startup tab
change Delay to a number other than 1
Close Desktop properties
Open Desktop properties
Open startup tab
observe Delay

If, as on my system, Delay is back to 1 Click Default at the bottom and observe the number.
Now close Desktop properties
Open Desktop properties, open any or all tabs other than Startup
Close Desktop properties
Open Desktop properties
Open Startup Tab
Observe Delay
If shows 1, click Default button and observe Delay time (if as on mine, it will be the number set)
Close Desktop properties
Open Desktop properties
Observe delay time
Close Desktop properties
Open Desktop properties
Open Startup tab
Observe Delay
Click Default (if as on mine, it will now be 1).

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version