Cannot change page setup

[klaa3]

OK,

Let's make this simple.

1. Open a diagram
2. Right click, choose Diagram Properties
3. Click Page Setup button
4. Change the margin settings (to anything different)
5. Click OK
6. Click Page Setup button again
7. Were changes saved? (on mine, EA 3.10 build 504, the answer is no).

Any suggestions?

[kelly_sumrall]

I get the same results.  I think it used to work.

[Erik Przekop]

Add a "me too" to that one.  I've found that the border will show up in the 'print preview' window, but the bottom (or right) edge is often chopped off on the actual output.

[crispan]

I still have this problem, too.

For details look at my post "Diagram printing problem" from 09/12/02 at 11:52:52.

Cheers,

crispan

[jafalt]

Me to
.. and I can set up the page settings in other application e.g. Word ... so to mee  it must be a bug.


My work around:
I use "copy to clipboard" in the diagram menu
and paste it into Microsoft publisher. Here it's still vector graphic so I can scale it, rotate it, put pagenumber on and so on and save it as a zoomable *.pdf.
Only the printer sets the limit from here.

Maybe it's a help

newbe 2
/jafalt

[jlalexander]

Wow, ok, glad to see it's not just me.

But, what an annoying bug. Unfortunately, it's not a good bug (is there such a thing as a "good bug") to find while evaluating a product for purchase.

And, considering that this bug was first reported in September? Scary.

How often are new releases typically done? Does anyone know?


Thanks,
-Jason

[jaimeglz]

Hi Jason (jlalexander),

Do take a look at other issues raised in the forum, and evaluate how fast they have been resolved.

It would be unwise to evaluate EA on the basis of this bug alone (which, by the way, has not bothered me in the least for all the time I've been using the product succesfully).

Cheers,

Jaime Gonzalez

[jlalexander]

Hey there Jaime,


I appreciate the reply.

I did do a search on the admin's post, which consisted of only changelogs of each build, and builds do come fairly frequently. So, I'm not concerned there at all.

I've now spent the last few hours reverse generating my code, and putting together a rough object model, and I'm impressed! It has the feel of Rational, but without the sticker price.

As it is now, I did as the others suggested, copying to clipboard and printing out the image, and it worked like a champ.

So, two thumbs up! Good stuff!


-Jason

[Bob Heck]

Jaime,

I agree that EA is a fine product and that Jason should really take a look at everything it offers (it really is a bundle).  However, as the original poster of this problem, I am still waiting for resolution -- to me it HAS been a problem.  The quick changing and printing of diagrams to copy and take to a board meeting is something that I need.  And the inability to change the printer settings causes inferior output in many cases.  

It is a little disturbing that the Sparx staff has a "we will work when we feel like it" attitude.

Ciao,
Bob Heck  :-/

Hi Jason (jlalexander),

Do take a look at other issues raised in the forum, and evaluate how fast they have been resolved.

It would be unwise to evaluate EA on the basis of this bug alone (which, by the way, has not bothered me in the least for all the time I've been using the product succesfully).

Cheers,

Jaime Gonzalez

[klaa3]

Jaime,

(I posted the last reply without being logged in and claimed to be the original poster of this issue.   I logged in and posted this one just to erase doubts that I may not have been the original poster).

Thanks,
Bob Heck  

[CJ]

G'day Bob,

The Sparx gang aren't the least bit complacent about fixing any bug or adding any good feature.  They've been pretty frigging good about it, I'd say ... where has Sparx ever shown any attitude other than receptive/positive?  

I would find it hard to be critical of the product and its support considering the number of builds provided and the content of those builds.

[jlalexander]

Yeah, they definitely seem real active about getting new builds out and addressing items quickly.

Unfortunately, that particular bug seems like it has lingered around quite a bit, throughout many builds. And, in my mind, the ability to print quickly and easily should be one of the main requirements of the tool, given it's purpose: analysis, design and documentation.

Just my .02. Outside of that, it's a great product from my evaluation. I was easily able to install it, import in my code, layout the object model, and print it out (with the work around).


-Jason

[klaa3]

Jason V,

Point well taken.  However, there has been more than one build since the problem was reported, and it is still unresolved.  As hard as the staff is working, it's still an annoyance being the person with the bug that gets put on the back burner.

Thanks,
Bob

[Steve_Straley]

Bob,

There is a big difference between an "annoyance" and a "bug".   Show stoppers have always been addressed promptly; annoyances, nice-to-have-features, et cetera have always been addressed shortly after.   I understand any frustration an "annoyance" may cause, but when I see posts like "It is a little disturbing that the Sparx staff has a 'we will work when we feel like it' attitude." is not just unfair, it is unjust and un-true.

Consider this:  Rational ReqPro has an "annoyance" where documents created in a package can not be name-changed once created; Rational ReqPro does not allow sub-documents to managed in the repository (only allowed by placing objects in the word document).   They have the attitude that this will NOT be changed and continue to charge outlandish prices.

I could go at-length comparing Sparx approach to bugs, annoyances and nice-to-haves to ANY software company out there and would be safe to bet my retirement funds, my house, and any other money I could scrape together that Sparx and "their staff" come out on top time after time after time.

Steve

[CJ]

G'day,

I hear ya, Bob.  I just haven't reached the point of being annoyed nor hindered by anything in EA.  Still on the honeymoon ...

For all we know, the fix to your printing problem might involve significant work.  I think it's important for the product to not look stagnant (i.e. extend the time to fix/deliver the biggies to keep a continous flow of builds).

Then again, if it's a growing problem for many users, I'm sure it will bubble up Sparx's priority list.