Problems converting 2.2.7 to 3.5.5

Classic Servoy
1

Hi,
I am trying to migrate a major solution from 2.2.7 to 3.5.5.
It has worked mostly OK, however there were a couple of key issues.

  1. it seems that the ‘controller.showRecords()’ behaviour has changed. In 2.2.7, this would display all records if I had not performed an explicit search (& in fact I was normally doing a databaseRefresh before the call). I have done a global replace to ‘controller.show()’ which seems to have fixed things.
  2. There are some strange cosmetic/visual issues. The solution was based on the original Servoy 2 CRM solution, which used the ‘Servoy’ style. Once it has been converted, any fields I have placed on a form that had the bevel style, but set as Transparent, now have an ugly black border.
    [Before]

    [properties]

[After]

[properties]

Also the contents of the fields are almost clipped on the left side of the box. I think I have managed to tweak this by adjusting the style ‘field {margin :’ settings, but don’t know how to cure the black border issue.

[Servoy style]

field
{
	background-color: #ebe9e9;
	border-style: inset;
	text-align: left;
	margin: 2px 2px 2px 2px;
}

portal
{

	background-color: #cccccc;
	border-style: inset;
}

label
{
	border-style: outset;
}

button
{
	border-style: outset;
}

Any help would be greatly appreciated. I really am not an expert in CSS Style sheets, so don’t know what to do to fix it (unless it is a bug…).

Thanks,

Rafi

2

Hi Rafi,

I can reproduce the issue.
When setting the transparency on the field to true the inset turns black.
Setting border colors using CSS doesn’t have any affect.
When not using CSS and using the border property to make an inset then transparency doesn’t have any negative effect. Only downside is that you can’t control the border width.
I suggest you file a bugreport in the support system.

Tested with:
Servoy Developer
Version 3.5.5-build 518
Java version 1.5.0_13-119 (Mac OS X)

3

rafig:

  1. it seems that the ‘controller.showRecords()’ behaviour has changed. In 2.2.7, this would display all records if I had not performed an explicit search (& in fact I was normally doing a databaseRefresh before the call). I have done a global replace to ‘controller.show()’ which seems to have fixed things.
  2. There are some strange cosmetic/visual issues.
  1. you mixup controller.showRecords() and controller.showAllRecords()
  2. we create a support case 130364 on your name
4

ROCLASI:
Hi Rafi,

I can reproduce the issue.
When setting the transparency on the field to true the inset turns black.
Setting border colors using CSS doesn’t have any affect.
When not using CSS and using the border property to make an inset then transparency doesn’t have any negative effect. Only downside is that you can’t control the border width.
I suggest you file a bugreport in the support system.

Thanks Robert.

JAN WROTE:

  1. you mixup controller.showRecords() and controller.showAllRecords()

I did not always want to showAllRecords. Some of the calls to showRecords() were after ‘finds’. In these cases I only wanted to show ‘found’ records, and the old call did not act in the same way as in 2.2.8, it only worked if I changed it to show().

  1. we create a support case 130364 on your name

Thanks, but is that for the bug of the transparent fields, or the controllerShow?

Having done more detailed testing now, there also seems to be a problem with ‘element.requestFocus()’ not seeming to work, but I am still looking into it (it was putting the cursor into a ‘Qty’ field on an order/line item ready for an operator to enter data. This was working great in 2.2.8, but is now not working).

Thanks,

Rafi[/quote]

5
  1. not sure if I understand what you are saying, but after a find in a hidden form the only reasonable thing to call is controller.show() and not showRecords() in the first place, since showRecords without arguments has different meaning all along, see docs or sample code
  2. case is created only for the strange border problem
6

Jan Blok:

  1. not sure if I understand what you are saying, but after a find in a hidden form the only reasonable thing to call is controller.show() and not showRecords() in the first place, since showRecords without arguments has different meaning all along, see docs or sample code
  2. case is created only for the strange border problem

  1. I’d have to look back at the old 2.2 docs to see what that said, but it worked that way before. AS I’ve done a global search/replace now to fix it, I’ll leave that be for the moment (time pressures…)

  2. that’s great as it is a real ‘eye-sore’ currently.

Thanks,
Rafi

7

the border problem is fixed in the next release,

8

Gabi Boros:
the border problem is fixed in the next release,

Great!

I’m glad I found it :)

Thanks

Rafi

9

we needed to look a bit harder to that fix.

The problem is that you use a BevelBorder with no colors. This is a very valid thing to have. Then the BevelBorder uses the components color to determine what border colors it should use…

But it seems that if you set it to transparent the bevel border cant do much.

i made the BevelBorder editor a bit more clear, for black borders around transparent fields you should look to your Border setting and change it to use real colors…

10

jcompagner:
i made the BevelBorder editor a bit more clear, for black borders around transparent fields you should look to your Border setting and change it to use real colors…

Can you give me the CSS/Style code I need to do this, so I can just edit the Style Sheet, as there is NO WAY I can go thru every form in the solution tweaking properties!!!
This was a nice visual effect that worked great in 2.2.x, but now isn’t and my client’s users really don’t like the ugly black borders :(

When will 3.5.6 (or whatever) be out with new ‘BevelBorder editor’?

Thanks,
Rafi

11

currently if you have a css border of inset or outset (border-style) the color property (border-color) isnt used at all currently. So only a default BevelBorder is created without colors.

I changed this so that this works:

label
{
border-style: inset;
border-color: #ffffff #f0f0f0 #808080 #000000;
}

field
{
border-style: outset;
border-color: #ffffff #808080;
}

so if you define 2 or 4 colors for inset/outset then the BevelBorder is created with them.

We are looking if this could break existing solutions somehow, so if we can include this into 3.5.6 that is planned for tomorrow.