Service Pack 3 for Visual Objects 2.8
in [Visual Objects]
|
Prev: Fabzip
Next: to call an URL from insite a VO-App
From: E®!k /!sser on 16 Sep 2009 04:01 Willie, Most people do not use the RPro 3.x COM interface, as this does not allow you to create reports programmaticly. regards, Erik "Willie Moore" <williem(a)wmconsulting.com> schreef in bericht news:h8pik2$g3m$1(a)aioe.org... Jamal, Just to let you know, RP3 for Vulcan has full PDF support. It is accessible from VO as a COM object just as it was when it was the VO version. Regards, Willie __________ Information from ESET NOD32 Antivirus, version of virus signature database 4427 (20090915) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Jamal on 16 Sep 2009 10:22 Willie, Is this released, any more info? Jamal "Willie Moore" <williem(a)wmconsulting.com> wrote in message news:h8pik2$g3m$1(a)aioe.org... Jamal, Just to let you know, RP3 for Vulcan has full PDF support. It is accessible from VO as a COM object just as it was when it was the VO version. Regards, Willie __________ Information from ESET NOD32 Antivirus, version of virus signature database 4427 (20090915) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Willie Moore on 16 Sep 2009 14:18 Jamal, It is on the Grafx site under Vulcan 3rd party tools although I don't see a current description for it. Fillip Fransen did the port to Vulcan and added the pdf support. It uses wPDF for the PDF support. I bought the source code version for 495 so I would be able to rebuild when new releases of Vulcan come up without having to wait for the official RP release. I am very happy with my purchase! I think it is a must have if you have legacy ReportPro reports. Most of my new work is in Reporting Services but I still have a lot of RP3 reports. Regards, Willie "Jamal" <vodotnet(a)yahoo.com> wrote in message news:zw6sm.2781$tl3.1630(a)nwrddc01.gnilink.net... > Willie, > > Is this released, any more info? > > Jamal > > "Willie Moore" <williem(a)wmconsulting.com> wrote in message > news:h8pik2$g3m$1(a)aioe.org... > Jamal, > > Just to let you know, RP3 for Vulcan has full PDF support. It is > accessible > from VO as a COM object just as it was when it was the VO version. > > Regards, > Willie > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4427 (20090915) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4430 (20090916) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4430 (20090916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Geoff Schaller on 5 Oct 2009 02:37 Well folks, annoyingly, many of the SP2 bugs are still present! I have been trying to edit and rebuild a couple of applications and ran into editor problems. These were in source controlled modules so I reverted to one that isn't. NO dice. Here are the problems I am encountering in the first 3 hours of using the new SP: 1. When I import an MEF that already exists, the treeview still duplicates the entry. I had heard that this was "fixed" some months ago but it certainly still happens in 2836. Whilst it is harmless mostly, (except for the visual annoyance) when under SCC it creates instabilities with VSS. If you import multiple MEFs, only the last one duplicates, with or without SCC. 2. Creating new entities causes garbled entries in the IDE browser. I will attach images of this to the GrafX version but new ones (created via the WED) show up as blank entries and sometimes compile, sometimes not. 3. Reindexing new entities gives them symbol names but they compile. This is VERY confusing. And it won't go away! 4. I am having trouble with SCC whilst disconnected - the same issues reported way back in November of last year so I am wondering is these fixes ever made? I will have keep testing this once I get back to the office to be fully certain of this. 5. I have some projects that compile and run fine and I have others that just cause VO to hang. No messages or errors, the CPU just spins away at 50%. Usually the only way out of this is a full project rebuild and again, I will have to wait until I get back to the office to test more conclusively. 6. Importing a SP2 AEF over a SP3 AEF consistently reports a corrupt entity for every module in the AEF. It still compiles and runs but what is this new warning? Does it really require reindexing on every import? 7. Importing an AEF sometimes corrupts the Windows task bar in Vista 64 bit SP2 - I have not yet discovered a consistent trigger. We will experiment on other OS versions later next week. Is anyone else out there testing SP3 with any degree of intensity.... not merely just recompiling? The deeper question I have is why these things weren't picked up by the VOPS folks. Geoff "Brian" <B.ian(a)G.afxsoft.com> wrote in message news:0019520b$0$8031$c3e8da3(a)news.astraweb.com: > Hello All, > > GrafX is pleased to announce the release of Service Pack 3 for Visual > Objects 2.8 on September 30th 2009. > > For a list of features and bug fixes please refer to the following document. > > http://www.grafxsoft.com/28sp3.htm
From: Geoff Schaller on 5 Oct 2009 02:45
I am dead against open sourcing the runtime of VO for a variety of reasons. The lack of skilled C++ and macro engineers chief among them. But in all reality, the VO community behaves like an open source community in almost all practical respects already. Geoff "Gabriel" <gabrielvdk(a)gmail.com> wrote in message news:925ecf9f-b427-4c3e-8b72-35f422db47c9(a)k19g2000yqc.googlegroups.com: > Hi All, > > About 3 years ago I left Marti IT (of which Marc Verkade is the owner) > after ca. 3 years of working for them. For me Marti meant my first > object oriented programming experience, and for me that first > experience was in VO. Marc always directed me to this newsgroup where > you could (and I presume still can) always count on a quick and > correct response. |