[Done] EditorGadget regression

BarryG · **Joined:** Thu Apr 18, 2019 8:17 am **Posts:** 1192

First post edited to show that it's not due to making a table with the strings.

Shardik · **Posted:** Sun Nov 15, 2020 5:03 pm

In Windows 10 with PB 5.73 Beta 4 you have to enable SES_EX_NOTABLE before displaying text in the Editorgadget. Fred should implement this when creating an EditorGadget. It doesn't do any harm in PB 5.72.

After enabling SES_EX_NOTABLE in the EditorGadget, BarryG's and infratec's examples work like a charm in PB 5.73 Beta 4:

Code:

#EM_SETEDITSTYLEEX = #WM_USER + 275
#SES_EX_NOTABLE = 4

OpenWindow(0,200,200,100,100,"test",#PB_Window_SystemMenu)
EditorGadget(0,10,10,80,80)
SendMessage_(GadgetID(0), #EM_SETEDITSTYLEEX, #SES_EX_NOTABLE, #SES_EX_NOTABLE)
AddGadgetItem(0,-1,"+-+")
AddGadgetItem(0,-1,"WTF")
Repeat : Until WaitWindowEvent()=#PB_Event_CloseWindow

Code:

#EM_SETEDITSTYLEEX = #WM_USER + 275
#SES_EX_NOTABLE = 4

OpenWindow(0,200,200,200,100,"test",#PB_Window_SystemMenu)
EditorGadget(0,10,10,180,80)
SendMessage_(GadgetID(0), #EM_SETEDITSTYLEEX, #SES_EX_NOTABLE, #SES_EX_NOTABLE)

AddGadgetItem(0,-1,"+----------+")
AddGadgetItem(0,-1,"| C64 Maze |")
AddGadgetItem(0,-1,"+----------+")

Repeat : Until WaitWindowEvent()=#PB_Event_CloseWindow

skywalk · **Posted:** Sun Nov 15, 2020 5:09 pm

NOT A BUG.
But this is an updated RichEdit Control and should be mentioned in "What's New" for v573.
I like the new features exposed in the newer control.

kurzer · **Posted:** Sun Nov 15, 2020 5:27 pm

I don't think it's ok if you first have to switch the new editor gadget to the old behaviour by API commands.
Maybe the editor gadget could get some new flags to enable or control the features of the new rich edit control.

Little John · **Posted:** Sun Nov 15, 2020 5:48 pm

kurzer wrote:

I don't think it's ok if you first have to switch the new editor gadget to the old behaviour by API commands.

I agree. That wouldn't be good, and it would break existing code.
Therefore Shardik's solution should be applied by Fred internally in PureBasic.

RASHAD · **Joined:** Sun Apr 12, 2009 6:27 am **Posts:** 3822

Maybe Fred can make it as a user choice between edit ver 3.0 or ver 4.1
Anyhow BarryG is making a lot of troubles these days :mrgreen:

BarryG · **Joined:** Thu Apr 18, 2019 8:17 am **Posts:** 1192

skywalk wrote:

NOT A BUG.

Really? So the user isn't allowed to add "+-+" as plain ASCII to an EditorGadget now? How do I explain that to my users? Using "+-+" to format ASCII tables around text is a decades-old PC tradition.

Anyway, Shardik's solution is the answer (thank you so much!), and I agree that Fred should make this an optional flag, something like:

Code:

EditorGadget(0,10,10,80,80,#PB_Editor_NoTables)

Which would then apply the #SES_EX_NOTABLE to it. Please do this, Fred, so it doesn't break existing EditorGadgets like it has for my app.

RASHAD wrote:

BarryG is making a lot of troubles these days :mrgreen:

I can't help it if my app doesn't work anymore from the previous Final to the new Betas. That's what beta-testing is for.

Saki · **Posted:** Sun Nov 15, 2020 10:07 pm

Well, I would never have noticed that an ImageGadget() with a transparent image
does not work on a ButtonGadget() anymore, because I would never do that.
In this respect some unusual codes are already useful.
And he tries to help everyone.

You did a good job Barry !

skywalk · **Posted:** Mon Nov 16, 2020 3:28 am

BarryG - I said it is a bug in the documentation. Did you read the link to MS rich edit control?

BarryG · **Joined:** Thu Apr 18, 2019 8:17 am **Posts:** 1192

Yes, I read the link. I see what you mean by "bug" now (after re-reading your post with a clearer mind). Still, the user should be able to add any text without fear that the EditorGadget isn't going to reformat it to what it thinks you want.

Fred · **Posted:** Mon Nov 16, 2020 2:28 pm

Fixed, thanks for the investigation Shardik

PureBasic Forum

[Done] EditorGadget regression

Who is online