We have created a couple reports in VS2008 and since we've converted to 2012 we've run into an issue where the fields look perfect in the designer and in the viewer, but when we print it the fields are all moved. Now it isn't all the same movement either, some items moved down about an inch, others moved up a half inch, some left/right/etc. So to resolve the issue immediately I've opened designer and manually moved the fields so that they look wrong on designer but they print properly. The issue I'm running into now is when I put a field at the very top of the page, it still pushes it down despite all margins being set to zero.
Now I don't like breaking my designer to make it work, so if there is a more permanent solution people are aware of, that would be ideal. But if there is anyway to force this field to be pushed to top of page, that would be an acceptable temp fix.
The nature of our need here is that this prints on a specific insurance form and the fields have to fit in the proper boxes or they are declined.
Thanks in advance,
Dylan
With the use of guidelines in crystal report you can resolve this issue.
you can enable guidelines from File--> option --> in which layout tab
in Design view panel you can select Guidelines.
now you can design your crystal report and set all the fields in touch of guidelines.
remove unnecessary guidelines. you can set your report easily.
We had to recreate the form in VS2012. Something about the conversion process for an 08 file to 12 just would not hold margins at all.
Related
Using PhpStorm, I usually have 2 or 3 source files opened in splitted editors. Now that I have a secondary screen, I've put all the toolbars in the second screen, and I'd like to have a fixed 3-splits layout for my editors. But as soon as I close the last tab in one of the splits, that split is gone.
I've search through PhpStorm options and surfed for an answer, but didn't seem to find how to do it.
Is there any way to fix the split layout in PhpStorm?
It is not possible to get such behaviour in current version.
https://youtrack.jetbrains.com/issue/IDEA-66407 -- watch this ticket (star/vote/comment) to get notified on progress.
I'm prepared to duck when the tomatoes are throw because this seems so simple. Nevertheless... In Visual Studio 2013 when looking at pending changes is there way to vertically expand the included changes and excluded changes segments ?
For example this morning I have a large changes set (around 1200 of the files pictured below are auto generated T4s, but it it's still tough to look over that much data in 300 pixels.
I encountered the same behavior in VS2015.
You can avoid the tiny box by collapsing parts of the tree, it only appears when the currently shown list is "too long".
I had to select the View Options > Show Solution Changes then the entire list was visible without scrolling.
UPDATE
On VS 2015/Update 2, the behavior is that the two scrollable sections appear when the expanded height exceeds a certain limit. I.e., to make those sections disappear/merge into one, it seems to be enough to just collapse some of the tree nodes, so that the height falls below that magical limit.
[Original post follows]
Had the exact same issue (I'm running VS 2013 Pro, Update 4)
Found no UI options that would fix it. So I decided to just "learn to live with it", and started making actual changes (i.e. include/exclude items, Undo, Compare, etc.) -- and suddenly noticed that it reverted back to that "tall view" on its own! And, it's still in the "Tree View" mode:
I'm guessing it was the move of some of the items into 'Excluded Changes' section (which became empty for some reason -- it wasn't before). I didn't catch what actually did the trick, but that seems like the most likely cause.
You can change to List View which will give you all the vertical space you could want, but obviously you lose the folder heirarchy, so it's not ideal :(
Alternatively, you can use the TFS Power Tools to enable Windows Explorer integration which uses the old style dialog which is completely resizable.
EDIT: Added image of list view.
I just tested this under Visual Studio Update 4 and 5 and it seems that the current behavior is that if there are more than 99 items in either the "Included Changes" or in the "Excluded Changes" list, both lists are limited to 300 pixels.
This makes sense to me, as it would become too hard to switch between "Included Changes" and "Excluded Changes" otherwise, having to scroll back and forth (though making creative use of collapse would make it easier).
It would have been nice that when one docks the Pending Changes panel as a document, the included and excluded changes would show as 2 columns with infinite scrolling, but alas, this is not the case.
In some cases, switching to list view removes some of the "tree" nodes if you have folders in your set of changes. This may cause the panel to collapse with fewer changes.
I have a form that correctly displays component borders most of the time.
However when I tab out of the form’s first input field, the borders of all the form’s TDBEdit/TEdit components disappear. The component’s border’s reappear when moused over.
I can reset these at runtime by looping through the form’s components and setting TDBEdit/TEdit borders (BevelInner: bvLowered, BevelOuter: bvRaised).
Also, this issue appears to have something to do with the Enable runtime themes option in the Project Options. The issue only exists when this option is enabled and regardless of the Windows Theme that is being used.
CodeGear™ Delphi® 2007 for Win32® R2 Version 11.0.2902.10471
After some additional research it appears that this is a known issue and occurs predominantly when a user is using the ALT button.
Additional information pertaining to workarounds can be found at:
http://qc.embarcadero.com/wc/qcmain.aspx?d=37403
I'm making a report with a Rave Reports component in Delphi. I've come to some issues that I cannot figure out myself.
If I have a very long number or text without spaces inside, how can I fit it into the tab? My tabs have concrete widths and I don't want that very long text is truncated that doesn't fit into the tab. Is there any way to check if text is longer than tab width and then continue this text on new line? Also, is there a way for tab padding?
Regards,
evilone
I would seriously consider changing your reporting engine to, for example, Fast Reports. Last i heard was Rave Reports is no longer - i may be wrong, but just doing a quick check i couldnt even get to their website.
Fast Reports has the functionality you describe.
Windows in my application are popping up off the edge of the screen, and this of course is a problem because some of the windows are modal and can't be dismissed (you don't even know they are there).
I'm using the TurboPower Orpheus component which remembers the location and size of each form, then restores it when the form is shown again. It saves the size and placement in an INI file.
What can I do to prevent windows from ever showing off the side of the screen?
It's common for this sort of thing to happen if you use multiple monitors and then disconnect one, such as when undocking a laptop. Or if you dock a laptop to a screen with a higher resolution. Or use remote desktop, etc..
The remedy is to override the "remember my position" behavior with a sanity check, to see if the left+width exceeds the width of the screen (Screen.Monitors array, actually - thanks guys), and vice-versa for the top+height.
Ideally, you "bump" by subtracting the difference, so you're butting up against the edge that the window wanted to straddle.
Also, see if there are updates to Orpheus that fix this. If not, you can get the source, make the correction (optional), and contribute it back to the project. It's OSS, as I recall.
You may want to give a look at their DefaultMonitor property and read the code from TCustomForm.SetWindowToMonitor to see how to deal with positioning relatively to Screen.Monitors.
Use DefaultMonitor to associate a form with a particular monitor in a multi-monitor application. The following table lists the possible values:
Value Meaning
dmDesktop No attempt is made to position the form on a specific monitor.
dmPrimary The form is positioned on the first monitor listed in the global screen object's Monitors property.
dmMainForm The form appears on the same monitor as the application's main form.
dmActiveForm The form appears on the same monitor as the currently active form.
Note: DefaultMonitor has no effect if the application does not have a main form.
To recall the previous position of a form, without having it suddenly in an area which is no longer available (due to a plugged off screen or changed resolution), you just call
TForm.MakeFullyVisible;
That's it. See the documentation.