I'm not saying that it's a showstopper because the app will not run but I am saying that I can not release a Windows app compiled with 2006r4 created on a Mac to my clients as it looks ultra unprofessional to release an app with these details displaying this text. This may be a matter of opinion and some people may be prepared to release it all the same - but I can't do it. I have my new release ready and I'd love to compile with 2006r4 but I don't want to with this issue. It affects the splash screen, version checking, app properties window, security alerts etc.

Sure I could hard code the text in the splash screen but the strange text is still present in the app prefs as well as Windows Security Alert etc.

Eg. Windows Security Alert pops up saying

Do you want to keep blocking this program:

Name: eso .ea1id2

All I am saying is that as long as that is present I will revert to a previous version to compile and thus it is a showstopper for me to compile with r4. It's just that I know that it has to be quite a serious issue for RS to release a new incremental build and I don't want to have to wait 3 months for a fix for this. I want to be able to develop my Mac and Windows app within the same version of the IDE and if I have to develop with R4 and then compile with a previous version who knows what issues may arise. If I can't code and compile with the same version of the IDE then I consider it a showstopper. I currently can't compile with R4 without releasing an app which has an unprofessional factor which I know my customers will raise. It frustrates me when people criticize apps because they're built with RB and I believe releasing an app called eso .b Build 0 will not look good.

Can anyone else confirm that this is an issue or does the problem lie somewhere within my environment?

Thanks


Jeff


On 15/10/2006, at 9:40 AM, Trausti Thor Johannsson wrote:

How is this a show stopper ? I mean really ? What about having a dynamic string inside a module which contains the version information ? Or as a work around just make the static text contain the version number.

Really ?  A showstopper ?


Trausti
On Oct 15, 2006, at 1:11 AM, Jeff Ayling wrote:

Hi all,

The following issues have appeared with RB2006r4 OSX. These were not issue with RB5.5 or 2006r1

In the IDE project tab - when I click on app, I enter text in the LongVersion field and the NonReleaseVersion field (which is on autoincrement) yet these details are not being passed through to a compiled Windows app correctly. However they appear correctly on OSX.

On my splash screen I use the following to insert the version details on the window like this:

me.text=app.longversion+" Build "+str(app.NonReleaseVersion)

On OSX it appears as - Version 3.0b1 Build 21

On Windows it appears as - eso .b Build 0

...update - ok I thought it may have just been my app so I created a new project containing nothing but a statictext field with "me.text=app.longversion+" Build "+str(app.NonReleaseVersion)" in it's open event - and exactly the same issues result. I can not get the LongVersion or NonReleaseVersion to appear correctly.

Has anyone else experienced this?

I simply can not distribute a compiled Windows app with these details incorrect.

I sincerely hope that this is something I am either doing wrong or can fix otherwise Version r4 OSX can not be used to create Windows apps and this is a Showstopper until we get a fix.

Any thoughts would be urgently appreciated.


Cheers


Jeff
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to