Clear the MessageBox

[FourthWorld]

PERHAPS it might not be a bad idea for the Forum to acquire 7 more sections:

1. Things peculiar to GNU-Linux.

2. Things peculiar to MacOS.

3. Things peculiar to Windows.

4. Things peculiar to Android.

5. Things peculiar to iOS.

6. Things peculiar to HTML.

7. Things just plain peculiar.

Of course, if one wanted to be polite one could use the following formula:

Issues with GNU-Linux.

1. Click "Board Index" near the top of this page.
2. Scroll down through the list of sections
#ComprehensiveAnticipatoryDesignScience

[richmond62]

-
Blast: I knew I should have started the day with a Double Whisky.

This oversight mainly due to looking at the 'New Messages' section all the time.

[FourthWorld]

SShot 2022-02-22 at 12.00.31.png
-
Blast: I knew I should have started the day with a Double Whisky.

Breakfast of Champions

This oversight mainly due to looking at the 'New Messages' section all the time.

Me too, and I recommend that for others 'cause it's a super efficient way to see just the latest.

[wsamples]

"By unusable I mean I can't execute lines of script from the message box. It seems like the message box window is losing focus before I can hit enter."

This is an issue that has been discussed in another thread, although there is no known foolproof solution. There are different focus/window hiding issues which may (or may not?) be related which vary from distro to distro and depending on which DE/WM/Compositor combo you're using. Xfce has been found to demonstrate exactly the unusable behavior you describe in several distros, for several users, while working fine for others. One thing you might try is closing the tools pallete before opening the message box. I suggest that since in some cases there is clearly some mysterious interaction between them. You might also try displaying the backdrop, which mitigates some window hiding issues sometimes seen under Plasma5 - it's at least worth a try Good luck!

[PaulDaMacMan]

"By unusable I mean I can't execute lines of script from the message box. It seems like the message box window is losing focus before I can hit enter."

This is an issue that has been discussed in another thread, although there is no known foolproof solution. There are different focus/window hiding issues which may (or may not?) be related which vary from distro to distro and depending on which DE/WM/Compositor combo you're using. Xfce has been found to demonstrate exactly the unusable behavior you describe in several distros, for several users, while working fine for others. One thing you might try is closing the tools pallete before opening the message box. I suggest that since in some cases there is clearly some mysterious interaction between them. You might also try displaying the backdrop, which mitigates some window hiding issues sometimes seen under Plasma5 - it's at least worth a try Good luck!

Oh thanks so much, I knew I wasn't (that) crazy, but it's nice to have confirmation. It would be great if we could track down exactly the things that are NOT compatible with the Linux Engine so we can avoid/uninstall whatever is doing those things.

Strange I wasn't able to install the installer on Ubuntu Studio (KDEPlasma) because it kept telling me it couldn't use the GDK that's installed. I copied the IDE to my desktop from a previous backup (the IDE is basically a portable app) and it seems to be running great! No issues on this distro so far (I had it installed previously too).

I'm pretty sure I had Xubuntu working with the IDE in the past, but maybe I had a minimal install of it then?
Anyway KDE Plasma has come a long way, it's quite zippy now (even with the GPU eye-candy) and I've read that they've reduced its resources usage too!

[richmond62]

I have addressed our tangential trip over here:

viewtopic.php?f=20&t=36784

and I feel those matters should be over there rather than mixed up with
the stuff about the MessageBox.

[marksmithhfx]

I'm still trying to figure out why one would want to delete old message box entries. I find it very convenient to begin typing a command I used a long time ago and still have it pop up immediately after only two or three characters. Must be related to work flow I guess.

Hi Jacque,

I recently discovered the msg box has a limit as to how many previous lines it retains (I think) when I could not find an old command I was looking for. But I was not able to find out how many lines that is (or maybe an upgrade along the way just reset my back list?). Do you know if/what the limit is or if it's changeable? I'd probably set it to 1000 if possible!

Mark

[richmond62]

The first question I would ask relates to how:

IDESingleLineMessageHistory

and

IDEMultipleLinesMessageHistory

are stored.

While it is possible to do this:

Code: Select all

set the IDESingleLineMessageHistory of stack "revpreferences" to empty

one can also do this, which would suggest IDESingleLineMessageHistory is either a multi-line variable or an array:

Code: Select all

set the IDESingleLineMessageHistory of stack "revpreferences" to "cheese"

[Klaus]

What is the only stack of the IDE that can and does get saved?
Correct, the "refpreferences".
Check -> the customkeys of stack "revpreferences"

[richmond62]

OK, Klaus: I got 498 customKeys . . .

Cripes: probably time to crack out that bottle of whisky someone gave me for my birthday.

Bunging this script in a button:

Code: Select all

on mouseUp
 put customkeys of stack "revpreferences" into fld "fHISTORY"
end mouseUp

followed by this one:

Code: Select all

on mouseUp
put 1 into KOUNT
repeat until line KOUNT of fld "fHISTORY" is empty
if line KOUNT of fld "fHISTORY" contains "MSG" then
set the textColor of line KOUNT of fld "fHISTORY" to red
end if
add 1 to KOUNT
end repeat
end mouseUp

Is PBU (Pretty Bloody Uninformative) as these lines end up coloured red:

cREVMsgTabRectMultipleLines
cREVMsgTabRectpendingMessages
cREVMsgShowUIVariables
cREVMsgTabRectGlobalProperties
cREVMsgTabRectGlobal Properties
cREVMsgTabRectfrontScripts
cREVMsgIntelligenceObject
cREVMsgTabRectcard id 1002

and so on . . .

Doing this:

Code: Select all

on mouseUp
put 1 into KOUNT
repeat until line KOUNT of fld "fHISTORY" is empty
if line KOUNT of fld "fHISTORY" contains "Line" then
set the textColor of line KOUNT of fld "fHISTORY" to blue
end if
add 1 to KOUNT
end repeat
end mouseUp

gives me, among other things:

cREVMultipleLineHistory
IDEMultipleLinesMessageHistory

and I really wonder which . . .

[Klaus]

Code: Select all

get the customkeys of stack "revpreferences";filter it with "IDE*";put it

Reduces the amount to 5 lines, mon ami.

[richmond62]

Not entirely friendly right now . . .

as, while there are things that mention 'IDE', there are also things that mention 'MSG'
(and, where the MonoSodium Glutamate is escapes me),
and 'MessageBox'.

[richmond62]

OK, OK: getting 'somewhere':

Code: Select all

on mouseUp
put empty into fld "fSINGLE"
put the IDESingleLineMessageHistory of stack "revpreferences" into fld "fSINGLE"
end mouseUp

HOWEVER, what is NOT clear to me is whether customKeys can have properties . . .

This:

Code: Select all

on mouseUp
   put the properties of IDESingleLineMessageHistory of stack "revpreferences" into fld "fPROPS"
end mouseUp

threw a blue meanie!

[Klaus]

HOWEVER, what is NOT clear to me is whether customKeys can have properties . . .

Oh my...

[richmond62]

AND, just to throw a big, fat spanner in the works I found this:
-

-
which refers to something I was doing about 3 years ago!

But this:

Code: Select all

on mouseUp
   put the cREVSingleLineHistory of stack "revpreferences" into fld "fOLDcrap"
end mouseUp

does NOT work.