Problem in designer when having undescore in schema name

Posts   
 
    
Rosacek
User
Posts: 155
Joined: 18-Mar-2012
# Posted on: 17-Feb-2016 09:15:01   

LLBLGenPro v 4.2 Final (December 11th,2015)

I have schema name in MSSQL DB like "CUCP_Sales" When I add entities into LLBL project then group name "CUCP_Sales" is created. That's ok.

Then I want to add into that group TypedList and I see error msg because group name contains undescore. Might be due some settings, but then why such group name was created by designer when adding entities there.

http://screencast.com/t/MnrxSpZiWz

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 17-Feb-2016 12:48:37   

That indeed shouldn't happen (the group name should be cleaned up), we'll look into it!

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 18-Feb-2016 15:08:10   

Reproduced. I now see where the error is located, it's fine for when generating code, but adding something to that group runs the groupname through the name checker, which then removes '_' due to settings and it ends up as a different name.

Looking into it.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 18-Feb-2016 15:34:38   

Fixed in next build.

What's fixed is that it's not going to happen again, the _ is removed prior to the name being added as the group name in the element.

Your project has still _ in groupnames. You have to manually rename the groups to remove the _ from the names. This is a side effect of the naming rules where you have set to remove _ from names, and therefore a groupname has to obey that too (as it can be used in the generated code).

Frans Bouma | Lead developer LLBLGen Pro
Rosacek
User
Posts: 155
Joined: 18-Mar-2012
# Posted on: 18-Feb-2016 23:06:17   

When renaming group names to not contain undescore I found another flaw in designer rage

When I just change letter case in group name, the group name is not changed at all.

For example: original group name is MY_GROUP I change and mistype to MYGroup Then I want to correct to MyGroup, but no way.

The workaround is to rename to MXGroup and then finally to MyGroup, funny game wink

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 19-Feb-2016 07:12:05   

Rosacek wrote:

For example: original group name is MY_GROUP I change and mistype to MYGroup Then I want to correct to MyGroup, but no way.

The workaround is to rename to MXGroup and then finally to MyGroup, funny game wink

Reproduced. Strange indeed. Actually if you change any case and conseve the original name (with casing changed) is the same behavior. We will look into it as well

David Elizondo | LLBLGen Support Team
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 19-Feb-2016 17:51:59   

It's indeed rather silly. We'll see if this has an easy fix.

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 24-Feb-2016 10:11:26   

Fixed in next build. There's another issue: renames of groups aren't enabling undo, even though they're in the undo buffer/command queue. (so when undo is enabled through another action, they are undo-able). Very strange that this has gone so long unnoticed! Looking into that as well.

(edit) was UI only issue, the state of the undo/redo buttons wasn't updated after the batch update for the group name update (group isn't some container, it's a name on all the elements in the group, so renaming / undo/redo can be slow so it's done in a batch).

Fixed in next build. We'll release a new build later today.

Frans Bouma | Lead developer LLBLGen Pro
Rosacek
User
Posts: 155
Joined: 18-Mar-2012
# Posted on: 26-Feb-2016 11:26:28   

I downloaded the last build and seems ok.

Btw there is nothing in changelog http://www.llblgen.com/pages/ChangeLogBrowser.aspx?ApplicationID=14&S=4&ST=&Page=1

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 27-Feb-2016 10:06:46   

I didn't sync the log DB with the online version. It's now fixed simple_smile

Frans Bouma | Lead developer LLBLGen Pro