Scalos - General

[AMIGASYSTEM]

Scalos Prefs Guru Menu !

[deadwood]

@AMIGASYSTEM

1) Which icon did you try to Leave Out?

2) What are the steps to reproduce the software failure in Preferences (starting from a clean unzip of AROS-20190416-2-mingw32-i386-system-integrated.tar)?

[AMIGASYSTEM]

Dovrebbe farlo con tutte le icone, ho creato un video che mostra i due Guru (Save Menu e Leave Out?)

https://drive.google.com/file/d/16cpCgFz_8dKR54N0eD85Dzy2QZGidcTH/view?usp=sharing

Ho provato a spostare l'icona "Screemode"  da Prefs con "Leave Out" con il menu nativo Scalos e anche in questo caso ho ottenuto un Guru, vedi screenshot

[deadwood]

Ok, Thanks. I reproduced both bugs on linux hosted as well.

[OlafS3]

theoretical put out works (file is put out after reboot). Put back works correctly

[AMIGASYSTEM]

Ok, Thanks. I reproduced both bugs on linux hosted as well.

To be more precise, in the menu to generate the Guru and when you add the "User-defined Button" item, basically these buttons do not exist and therefore cannot save something that does not exist.

I would add instead that the Guru appears "on all items" if you try to delete any, reverse drag and drop

[AMIGASYSTEM]

I add if you hadn't noticed on my previous Screenshot that DualPNG icons are always cut by Scalos ! on Wander they are pefect, while Scalos cuts them.

[deadwood]

To be more precise, in the menu to generate the Guru and when you add the "User-defined Button" item, basically these buttons do not exist and therefore cannot save something that does not exist.

I would add instead that the Guru appears "on all items" if you try to delete any, reverse drag and drop

Actually when you drag&drop User-defined Button, you then need to select command from the drop down list (bottom of window). If you select, it saves, if not, it crashes.

[deadwood]

I add if you hadn't noticed on my previous Screenshot that DualPNG icons are always cut by Scalos ! on Wander they are pefect, while Scalos cuts them.

I know, you reported that previously.

The fixes done for this version were only in Preferences programs as mentioned in first post.

[AMIGASYSTEM]

There also seems to be a graphical problem, buttons sometimes do not appear or show up badly, same thing for backgrounds.

[magorium]

@OlafS3: glad you got it worked out now

There is no need to copy to the Root or copy Scalos to Extras, Scalos can be put wherever one wants, what is of interest is to assign the Scalos path, which "need not be done in user-startup or Startup-sequence."

I am aware that there is no need when it comes to Scalos itself.

The need to do so arises from the fact that deadwood request us to do so.

That way the errors as reported can be consistently reproduced. If you go ahead and use your own custom setup then it could be you are able to produce bugs that are not able to replicated by other users (unless they match the exact same setup as yours).

So, instead of being stubborn and install things my own way (even if it works as your screenshots show) , i follow the instructions as requested by deadwood 

[AMIGASYSTEM]

Sorry to continue with my 68 year old stubbornness , in my opinion, nothing should change if all the assignments are correct, the bugs i reported were almost always confirmed by deadwood.

Then in any case for confirmation I also do the counter test even with Scalos installed on Extras, if you watch the video I attached above where I reported the bugs, Scalos it is installed in SYS:Extras, as recommended by deadwood..

Also consider that the Extras folder on AROS, depending on the choice you make on InstallAROS, could then be in DH1:Extras and thus would not work, unless you make the change I made on AROS One after the report that deadwood made to me.

In my opinion it is right to keep all the Scalos files in the "Scalos" Folder to prevent some homonymous file from overwriting some other file with the same name.

[magorium]

@deadwood:
Not sure if this falls into your selected category of reporting...
i386 linux hosted

Steps to reproduce:

• Start Scalos as instructed
• Menu/Drawers/scalos prefs/scalos_prefs
• from list on left: text windows
• then on the tabpage fonts
• Press Use TT TextWindow Font
• Press dropdown
• Crash

Crashlog:

Code: [Select]

[KRN] Protecting host process stack (0xffee4430 - 0xffeee430)
[X11] BitMap class @ 0xe88ca6e4
*** Could not create object of Urltext.mcc
*** Couldn't find Urltext.mcc
UpdateWorkbench("NewPopupMenu.prefs", LOCK e89c0b90, 0x00000001)
Scalos_Prefs: MUI Notification loop detected! (#0)
  Source object: 0xe9cd5afc  Dest object: 0xe9d1f04c
  Attribute: 0x8042654b   Value: 0x1
Scalos_Prefs: MUI Notification loop detected! (#1)
  Source object: 0xe9cd5afc  Dest object: 0xe9d1f04c
  Attribute: 0x8042654b   Value: 0x0
Scalos_Prefs: MUI Notification loop detected! (#2)
  Source object: 0xe9cd5afc  Dest object: 0xe9d1f04c
  Attribute: 0x8042654b   Value: 0x1
[KRN] Trap signal 11, SysBase e88881e0, KernelBase e8888f44
    SP=e96bae20  FP=e96bb0c8  PC=e96da71a
    R0=ffffffbc  R1=e8e1518a  R2=e96bb260  R3=e96da6f9
    R4=00000000  R5=e89a2fc0
*** Logged alert:
Program failed
Task : 0xE9600600 - Scalos_Prefs
Error: 0x80000002 - Hardware bus fault/address error
PC   : 0xE96DA71A
Module Scalos_Prefs Segment 1 .text (0xE96D790D) Offset 0x00002E0D
Function TextWindowTtfPopOpenHookFunc (0xE96DA6F9) Offset 0x00000021
CPU context:
EAX=0xFFFFFFBC  EBX=0xE8E1518A  ECX=0xE96BB260  EDX=0xE96DA6F9
ESI=0xE89A2FC0  EDI=0x00000000  ESP=0xE96BAE20  EBP=0xE96BB0C8
EIP=0xE96DA71A  ESP=0xE96BAE20  EFLAGS=0x00010293
Stack trace:
0xE971AA71 Scalos_Prefs Function HookEntry + 0x00000024
0xE8E421B5 muimaster.library Segment 1 .text + 0x000475B5
0xE8E42D0D muimaster.library Function Notify__MUIM_CallHook + 0x0000003C
0xE8E434C1 muimaster.library Function Notify_Dispatcher + 0x000001F6
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E22883 muimaster.library Function Area_Dispatcher + 0x000006DA
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E34E92 muimaster.library Function Group_Dispatcher + 0x0000074E
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E463E5 muimaster.library Function Popstring_Dispatcher + 0x0000018F

@AMIGASYSTEM: you do you, and i do as instructed. No need to argue about it   

[AMIGASYSTEM]

@deadwood

The buttons on native AROS x86 are perfect, see screenshot, so the problem was only on AROS Hosted Windows

I suspect that the problem on AROS Hosted Windows is due to the Graphics Card

[OlafS3]

@OlafS3: glad you got it worked out now

There is no need to copy to the Root or copy Scalos to Extras, Scalos can be put wherever one wants, what is of interest is to assign the Scalos path, which "need not be done in user-startup or Startup-sequence."

I am aware that there is no need when it comes to Scalos itself.

The need to do so arises from the fact that deadwood request us to do so.

That way the errors as reported can be consistently reproduced. If you go ahead and use your own custom setup then it could be you are able to produce bugs that are not able to replicated by other users (unless they match the exact same setup as yours).

So, instead of being stubborn and install things my own way (even if it works as your screenshots show) , i follow the instructions as requested by deadwood 

+1

for testing and reporting we should have standardized platforms to make it reproduceable. I for example used Scalos as full replacement, installed it elsewhere and mixed it with original files. After that a lot of worked and I had a lot of discussions with Amigasystem who did it different.  . To have a step by step standardized way to create the test environment or use the same archive is more efficient in my view. It will be interesting to see what happens if it is installed elsewhere or used as full replacement and started directly but first the current bugs should be fixed.