Belxjander wrote:Well I ran into a weird problem...
The SDK Installer decided to cut off everything past the entry for the SDK in my User-Startup sequence
and as that entry was near the beginning... obliterated ALL of the file following...so I lost the MUI and Application assigns for everything else installed.
Neat fun... not... is the Installer suppossed to have exclusive control or have any trigger for "cutting short" files like that ?
Second Item... is "IExec->CreateMsgPort();" deprecated or not?
It happened to me too (i also already had the lines in from an earlier SDK), but it only "erased" the very last entry of user-startup.
I was able to recover it through the .recycled dir, though...and i remember this "last line erase" from earlier installations (going back to OS4.0, seems to be a long standing installer problem, IF it is a problem).
Never had such a big chunk cut off
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Belxjander wrote:Well I ran into a weird problem...
The SDK Installer decided to cut off everything past the entry for the SDK in my User-Startup sequence
and as that entry was near the beginning... obliterated ALL of the file following...so I lost the MUI and Application assigns for everything else installed.
Neat fun... not... is the Installer suppossed to have exclusive control or have any trigger for "cutting short" files like that ?
Second Item... is "IExec->CreateMsgPort();" deprecated or not?
It happened to me too (i also already had the lines in from an earlier SDK), but it only "erased" the very last entry of user-startup.
I was able to recover it through the .recycled dir, though...and i remember this "last line erase" from earlier installations (going back to OS4.0, seems to be a long standing installer problem, IF it is a problem).
Never had such a big chunk cut off
I had a long User-Startup I had written out... and the SDK entry was near the beginning... basically it almost wiped it back to only its own entry
and I didn't have any .recycled backup versions to "recover" from at all... so I am just re-writing extras into it as I come across the need
Belxjander wrote:
I had a long User-Startup I had written out... and the SDK entry was near the beginning... basically it almost wiped it back to only its own entry
Did you delete or in some way modify the line with ";END AmigaOS 4.1 SDK" in your User-Startup? If you did it could explain what happened since everything between ";START AmigaOS 4.1 SDK" and ";END AmigaOS 4.1 SDK" is to be replaced by the installer and if it can't find the end marker because it was deleted or somehow made unrecognisable it would probably replace the entire rest of the file.
FWIW I had my SDK entry pretty much at the beginning of my User-Startup too and it didn't cause me any problems.
Belxjander wrote:
I had a long User-Startup I had written out... and the SDK entry was near the beginning... basically it almost wiped it back to only its own entry
Did you delete or in some way modify the line with ";END AmigaOS 4.1 SDK" in your User-Startup? If you did it could explain what happened since everything between ";START AmigaOS 4.1 SDK" and ";END AmigaOS 4.1 SDK" is to be replaced by the installer and if it can't find the end marker because it was deleted or somehow made unrecognisable it would probably replace the entire rest of the file.
FWIW I had my SDK entry pretty much at the beginning of my User-Startup too and it didn't cause me any problems.
Another change introduced: at include_h/graphics/text.h the definition of struct TextAttr and TTextattr there is a CONST_STRPTR as the type of name of the font. My program has several cases that the structure is used to open a selectable font, and using ta->ta_Name causes a 'const' warning now. Can be ignored, but why the change?
Another change introduced: at include_h/graphics/text.h the definition of struct TextAttr and TTextattr there is a CONST_STRPTR as the type of name of the font. My program has several cases that the structure is used to open a selectable font, and using ta->ta_Name causes a 'const' warning now. Can be ignored, but why the change?
Because it is the correct type to use there.
Instead of just ignoring those compiler warnings you should always try to understand them and fix them. Compiler warnings are your friends and can help you to find bugs in your programs if you just let them.
The types have been corrected. There are many more corrections and more will be corrected over time. You should adapt your code to use the corrected types.
Another change introduced: at include_h/graphics/text.h the definition of struct TextAttr and TTextattr there is a CONST_STRPTR as the type of name of the font...
Because it is the correct type to use there.
Instead of just ignoring those compiler warnings you should always try to understand them and fix them. Compiler warnings are your friends and can help you to find bugs in your programs if you just let them.
Yes, I appreciate the warnings, they tell usually very much of my flawed code But here I don't understand the CONST_ part, as I understand the const to define something that is constant for the time program runs. But these structs are used for example to open an user selectable font. Could you explain a bit more?