A few bugs I found

[MikeM]

I only had a little time to play on a new installation of TSB, and here are a few small bugs I found:

When creating a software object and adding an editor, after you have created an editor and click 'save and new' to add another editor, the Description and Property Editor boxes shrink to half their size. They still take data, you just can't see most of it.

If you click the Static Text -> New, you get an error as below, and then you have to close TSB and re-open it or you get errors on all the other library objects:

Exception occurs while assigning the 'DetailView, ID:StaticText_DetailView' view to WinWindow:
The following control could not be licensed: TXTextControl.TextControl

Also when creating software projects and adding your objects, I see none of the column names in the grid view are populated. I need to right click and select the column chooser to add the names to the columns.

On the great side is I can move my data file where ever I want and re-connect the software project to it. Now I can move them out of those really long folder names and organize them much better. And the updates seem to work great, which is a fantastic thing to have.

Be back later to send you those files Thomas.

[TigerSoftware]

The licensing error is strange.

I just added a static text item on a clean xp machine and a clean vista machine with no licensing. I tried to recreate the Property Editor with no luck.

I see Alton has been playing with the mail merge which uses the same component. He should have got that licensing error as well which makes me think it might be local to your machine.

You may want to remove the program all together. Save all your TSB files for your software projects. Once you remove the program, make sure all the files in the old program folder are deleted. Keep your tsb files since these are your project files.

Reinstall the program.


Let me know what happens.

[TigerSoftware]

Ok, I got the licensing error thanks to a video Robbie showed me.

I was looking inside the model portion and not the main portion of the software program.


Thomas

[MikeM]

Clicking Static Text and then New in the Library brings the following error in 2.0.0.4:

Exception occurs while assigning the 'DetailView, ID:StaticText_DetailView' view to WinWindow:
The TX Text Control kernel DLL file could not be found.

Haven't tested too much else. I'll have to wait until I get my files back from you :D

[MikeM]

OK, this is weird. Installed 2.0.0.4 on my vista laptop and I don't get any error on the static text, but when trying to open a test program I made in 2.0.0.2 I get an error about the key.

Item has already been added. Key in dictionary: 'FK_Event_RecurrencePattern' Key being added: 'FK_Event_RecurrencePattern'
Error 120 (Provider v. 3.2.1.43): Cannot rename or alter table: Event

maybe because my deskto is 64 bit? I'll try to reinstall again later and see what happens.

[Alton]

I had the same error for the same "offense" this afternoon. I do know that I had created a conflict in that I had several objects that had the same names. Apparently, the result of combining objects created from the TSB with objects created from within the model that use the same names. I called it a day at that point. I may have to recreate the software and just add the already created objects in the morning. After I download the latest TSB.

I would like to know whether I should create objects from within the TSB or the model? I think I should do it within the TSB in order to use them on future projects.

I am using a computer with XP Proffessional.

[MikeM]

Maybe I'm nuts, but is the photo editor missing from the software objects?

I also noticed there is a new way to add objects from the object library in the software projects :D

That took a while to figure out, had to open and close the program a few times before I found that ;)

[MikeM]

It seems I get the key error as above even on newly created software. I had some objects in the library, but deleted them and created some new. Putting them in a new software project results in the error when trying to run it from within the model.

Time to quit for the night :)